Enumeration practicality

[Mark]

Assume you have an enumeration like PhoneType { Home, Business, Cell }.
This enumeration corresponds with a lookup/dictionary table in your database
like:

phone_cd | phone_descr
1 Home
2 Business
3 Cell

Now, I could associated each enumeration value with the phone_cd used in the
database. However, that strikes me as problematic ... it's like having two
copies of the same information in different places. However, otherwise I
need to be able translate between my enumeration values, and the database
values.

Is there a best practice(s) for dealing with this situation? Obviously it
depends on the circumstances, but general comments would be appreciated.
Thanks in advance.

Mark

[Nicholas Paldino [.NET/C# MVP]]

Mark,

I can't see why you would need it in more than one place. If you had a
number of details that you wanted to store for each id, then I would
recommend storing it in the database (with a column for each property you
want to store).

Either that, or I would use an enumeration in code, and attach
attributes to the enumeration which have the values that you want to store.
You can get the values from these attributes through reflection.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Mark" <Ma**@nowhere.c om> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..

Assume you have an enumeration like PhoneType { Home, Business, Cell }.
This enumeration corresponds with a lookup/dictionary table in your
database
like:

phone_cd | phone_descr
1 Home
2 Business
3 Cell

Now, I could associated each enumeration value with the phone_cd used in
the
database. However, that strikes me as problematic ... it's like having
two
copies of the same information in different places. However, otherwise
I
need to be able translate between my enumeration values, and the database
values.

Is there a best practice(s) for dealing with this situation? Obviously it
depends on the circumstances, but general comments would be appreciated.
Thanks in advance.

Mark

[Mark]

Thanks Nicholas,

Are you suggesting that if I have a critical/obvious need to store the
code/description in the database, that I should likely only use the codes
(1, 2, 3) in the application rather than creating a corresponding
enumeration in my .NET code?

Thanks again.

Mark
"Nicholas Paldino [.NET/C# MVP]" <mv*@spam.guard .caspershouse.c om> wrote in
message news:OL******** ******@TK2MSFTN GP15.phx.gbl...

Mark,

I can't see why you would need it in more than one place. If you had a number of details that you wanted to store for each id, then I would
recommend storing it in the database (with a column for each property you
want to store).

Either that, or I would use an enumeration in code, and attach
attributes to the enumeration which have the values that you want to store. You can get the values from these attributes through reflection.

Hope this helps.
--
- Nicholas Paldino [.NET/C# MVP]
- mv*@spam.guard. caspershouse.co m

"Mark" <Ma**@nowhere.c om> wrote in message
news:%2******** ********@TK2MSF TNGP14.phx.gbl. ..

Assume you have an enumeration like PhoneType { Home, Business, Cell }.
This enumeration corresponds with a lookup/dictionary table in your
database
like:

phone_cd | phone_descr
1 Home
2 Business
3 Cell

Now, I could associated each enumeration value with the phone_cd used in
the
database. However, that strikes me as problematic ... it's like having
two
copies of the same information in different places. However, otherwise I
need to be able translate between my enumeration values, and the database values.

Is there a best practice(s) for dealing with this situation? Obviously it depends on the circumstances, but general comments would be appreciated.
Thanks in advance.

Mark