Is it bad practice to use an enum that maps to some seed data in a Database?
Posted
by skb
on Stack Overflow
See other posts from Stack Overflow
or by skb
Published on 2010-04-29T16:31:12Z
Indexed on
2010/04/29
16:37 UTC
Read the original article
Hit count: 250
I have a table in my database called "OrderItemType" which has about 5 records for the different OrderItemTypes in my system. Each OrderItem contains an OrderItemType, and this gives me referential integrity. In my middletier code, I also have an enum which matches the values in this table so that I can have business logic for the different types.
My dev manager says he hates it when people do this, and I am not exactly sure why. Is there a better practice I should be following?
© Stack Overflow or respective owner