Subject | design question |
---|---|
Author | Chris Meelhuysen |
Post date | 2004-08-20T06:04:24Z |
Where/how do most people store global application settings in a
database? I'm referring to things like Feature X enabled, Use 24 clock,
Language = English, database version, etc. I have inherited an
application that has a table that stores this information with about a
hundred columns and there is only ever one row in this table. This does
not sound normalized to me.
I have seen reference to people who have made a table with two columns
and do a key / value approach always storing as text and casting back to
what they need.
I would prefer to save these settings in the database as opposed to a
config file somwhere else; so that everything that makes this instance
of my application unique is in one place.
What do most people do?
--
Thanks,
Chris Meelhuysen
VP Information Technology
Event Software
480-517-9990
chris@...
database? I'm referring to things like Feature X enabled, Use 24 clock,
Language = English, database version, etc. I have inherited an
application that has a table that stores this information with about a
hundred columns and there is only ever one row in this table. This does
not sound normalized to me.
I have seen reference to people who have made a table with two columns
and do a key / value approach always storing as text and casting back to
what they need.
I would prefer to save these settings in the database as opposed to a
config file somwhere else; so that everything that makes this instance
of my application unique is in one place.
What do most people do?
--
Thanks,
Chris Meelhuysen
VP Information Technology
Event Software
480-517-9990
chris@...