Re^2: Storing config data - RDBMS vs File?

The only reason I've used the database for my configuration data all this time is that it seemed better to make one query to a databse that I was already connected to each time a user accessed a page than to load up the extra code of a config file parser, access the file, parse the file and then move on every time.

This wouldn't be an issue with mod_perl, obviously, but I'm not using mod_perl for my project, yet. I don't have the experience or confidance to do so, though I'm working on it.

Comment on Re^2: Storing config data - RDBMS vs File? Select or Download Code

Replies are listed 'Best First'.

Re^3: Storing config data - RDBMS vs File?
by dragonchild (Archbishop) on Sep 27, 2004 at 17:35 UTC

my $config = Config::ApacheFormat->new;
$config->read( '/path/to/config.ini' );

my $block = $config->block( Database => $database_name );

my $dbh = DBI->connect(
    (map { $block->get( $_ ) || '' } qw( sid user password )),
);
[download]

What's so hard about that? And, before you worry about loading the code of a config fileparser ... compare that with the cost of performing an extra database query. I think you'll be (un)pleasantly surprised.

Or, think about it this way - when so many people are telling you something, isn't it worth a day to test it out?

Being right, does not endow the right to be rude; politeness costs nothing.
Being unknowing, is not the same as being stupid.
Expressing a contrary opinion, whether to the individual or the group, is more often a sign of deeper thought than of cantankerous belligerence.
Do not mistake your goals as the only goals; your opinion as the only opinion; your confidence as correctness. Saying you know better is not the same as explaining you know better.

I shouldn't have to say this, but any code, unless otherwise stated, is untested

[reply]
[d/l]


No such thing as a small change
	PerlMonks