What is best practice for storing editable site-specific information?

Posted 3 years ago by puzbie

Over the years I have used numerous ways for storing information like company telephone number, address and the like. The default solution is just to store them in a database, but it always bugs me that its a bit of a waste of a query, given how infrequently the data changes.

I am tempted to include a compile option, so that every time the information is changed, a config file gets generated. But that brings with it permissions issues, in that web users need to have write permissions etc. Nothing wrong with that in itself, but just another thing to configure.

My question is this: am I being a bit anal about this, and should I just rely on caching to ease the query load, or is there a neat solution which has hitherto escaped me?

Please sign in or create an account to participate in this conversation.