Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2011
    Posts
    5

    Storing runtime propertimes in a table

    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.

  2. #2
    Join Date
    Feb 2004
    Location
    In front of the computer
    Posts
    15,579
    It is standard amongst many applications, including all of mine!

    -PatP
    In theory, theory and practice are identical. In practice, theory and practice are unrelated.

  3. #3
    Join Date
    Jan 2011
    Posts
    5
    Okay thanks for the reply!

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •