Config info in DB or in include file? advice please

[aqw]

Hi!
I'm in the process of building an enormous php script that will be widely known after the summer 😉

But right now i need some precious advice.

Shall I put all the site config information (there is a whole lot of stuff) in a database table (config_tbl) or shall i put it in an include file like :
includes/config.php.

I think i'll go for the 'include' solution as it's faster (or am I wrong??). the db solutions = much more queries = slower

suppose i stored the application configuration options in the db (it's over 100 things...)
wouldn't that slow down my script?

My idea'd be to put everything in the conf file (include) and then when you need a certain option you just interpole :

$config1

insted of making :
$rid = mysql_query("select * from config_tbl ......." );
$result = $mysql_fetch_assoc($rid);
echo $result["demo"];
.....

Am I stupid if i proceed that way??

moreover an include file is very easy to update with some ereg_replace functions...

Thanks 4 answering

[batman]

Include file would be the best way to go. 🙂

[Weedpacket]

I agree with batman; if it's not something that changes in the normal course of things, then a static file would be a more effective means of storage. Besides, you're going to need a config file to store your database connection info anyway 🙂

The downside of course is that if you do want to alter it at some stage it will mean editing the source itself; either by hand, or by writing some sort of script that can include() the config file and display all the various settings and whatnot in a form which can have the new values entered (the script would then rewrite the config file with the new values). Actually, that's probably not really more difficult than maintaining a database version....