I'm developing my first web application in rails and I'm pondering whether this is a good or a bad way to implement a functionality.
This web application has a User and Guild classes. The objective is that the user answers a set of questions through radio buttons in order to match to a certain guild.
Because the Guilds have a continent location and each continent has countries, I have about 60 options each with a name and an id, there are also other shorter radio button questions with as few as 3 options. In total there are about 7 sets of questions, all of which are 'hardcoded' in the Views file.
My main concern is: is it a better practice to model the form's answers in the database since the Guild class has a field for each set of the questions?
I was thinking about registering the option and quering it to the database and return the matching guilds. But then I thought about the registry process of the guilds and how I would have to repeat the same options for them to match the model.
Also because the form would be the most accessed element of the webapp, wouldn't it hurt the performance if the application retrieved each of the options instead of beign hardcoded?