[eluser]jleequeen[/eluser]
I have quite a few lookup tables in a database for a current project and really have two questions.
First, is it good practice to create a model for each lookup table even if the table would only be used to make a dropdown? Maybe that is overkill, but I'm not sure.
Second, I've read articles that talk about "keeping your data in the database" as opposed to a bunch of static lists for creating dropdown menus, but obviously for some lists (especially with only 5 or 6 options) it's hard to justify creating a table just for them. In my project I have lookup tables for states, counties, river basins, river sub-basins, etc. Is there a best practice when it comes deciding on when it is time to create a lookup table, vs a static list? Or should basically all data be in the database without any static lists or arrays hardcoded? I know this also may be personal preference.
