Hi,

I'm pretty new to database design, and recently I've come across a scenario where an enterprise(Java EE) application placed it's runtime properties into a table in the database, properties such as debug on/off, log file path, JMS topics, etc. The intention being the application doesn't have to be redeployed in a production environment to change it's runtime behaviour, only changes need to be made to the database.

This seems pretty odd to me, and I was wondering if this is standard practice? If not, how would the runtime properties of the application be changed?

Thanks.

It is standard amongst many applications, including all of mine!

-PatP

Okay thanks for the reply!