StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>I don't think there's any overlap between Apache Commons Configuration and your requirement for a change tracking configuration database, unfortunately.</p> <p>If you need to store the configs in a database I suspect you'll either need another framework or roll your own solution. Re. the database, 2 thoughts:</p> <ol> <li>you can store configs with a valid-from/valid-to date. The current configuration would be the one with the null valid-to date, and you'd set the valid-to date as you update the config</li> <li>some databases support the notion of versioned data. E.g. Oracle has a <a href="http://docs.oracle.com/cd/B28359_01/appdev.111/b28424/adfns_flashback.htm" rel="nofollow">flashback</a> capability in which you simply re-write the database entity, and Oracle records a version of that table <em>at that time</em> (the specifics are probably much more complex). That may be a useful solution if you simply want a history of config changes for audit purposes.</li> </ol> <p>Another solution is to manage your configurations using an SCM, and to package/deploy such configurations with releases. e.g. create dev/test/prod configs in your source code repository and manage the changes there. Wrap these configs in your deployable and release to the appropriate environments. You have the change tracking capability of the SCM, but you can't easily track a change that occurs on the deployed environment. Your change management processes may/may not allow this. </p> <p>An amended version of the above would allow you to use your SCM solution on your deployed environments e.g. to check out configs into your prod environment. I've not seen this used a lot, I confess. It means a bridge/dependency between your development and production environments and that may be a bridge too far.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload