Data Modeling and Enums
How should enums be modeled in your database? Static Lookup Table? Or should they be left out of the data model and contained only in the object model? Specifically, I'm thinking about an enum that is represented in the UI layer by something like a combo or list box.
Rather than just coming to a decision on my own - I thought I would open it up to my readers (both of you..heh) to give me your opinions on how enums should be modeled in the database. I'm guessing that there are a couple of different ways of thinking on this that both have convincing arguments.