Re: Storing config data - RDBMS vs File?

If you store your config in a RDBMS, how do you want to get the configuration info for the DBI connection? I stick to human-readability, myself. I've used the basic INI-style stuff, and abused Data::Dumper once before, but my favorite is YAML. I can often make a human-readable config file, that is parsed into the exact data structures I want to work with.

Update: Also, if you're using a DB for key-value pairs, a table with tons of fields is horrible to edit. Use a two-field table, and make a class that uses AUTOLOAD to grab individual keys. If nothing else, you will strike fear in the hearts of your co-workers!

mhoward - at - hattmoward.org

Comment on Re: Storing config data - RDBMS vs File?

Replies are listed 'Best First'.
Re^2: Storing config data - RDBMS vs File? by kanwisch (Sexton) on Sep 27, 2004 at 16:32 UTC
I'm with hattmoward. You'll have to have configuration information for the database then, and will you have really gained anything? The only reason I can think to store information in a database is if you want to make it more difficult for cracker (and any future maintainers of your code) to piece together the information, or if you're going to have lots of different configurations available to a single application (think multi-threading oriented at users; aka portals).	[reply]

Replies are listed 'Best First'.

Re^2: Storing config data - RDBMS vs File?
by kanwisch (Sexton) on Sep 27, 2004 at 16:32 UTC

I'm with hattmoward. You'll have to have configuration information for the database then, and will you have really gained anything? The only reason I can think to store information in a database is if you want to make it more difficult for cracker (and any future maintainers of your code) to piece together the information, or if you're going to have lots of different configurations available to a single application (think multi-threading oriented at users; aka portals).

[reply]