Matt Mossholder on 2 Sep 2008 15:25:59 -0700 |
You could also version the settings "in table"... have another column where you keep the version of the setting (or maybe a timestamp), and rather than changing the setting, you insert a new version of it. Then you in your select statements, make sure you always query for the max version. If you set the table to not permit updates or deletes, it should be pretty tight. You might also have the same effect by using triggers on an existing table that archive out the old setting before replacing it with the new one (and record who made the change, when, etc.). --Matt Mossholder ----- "Christopher M. Jones" <cjones@partialflow.com> wrote: > Shameel Arafin wrote: > > We use 'migration scripts' at work, to track database schema > changes. So, > > let's say I add a table to the db. That table was created with some > sort of > > "CREATE..." statement. That statement goes into a file, and that > file is > > tracked in SVN. Then, when a push is made to the production > server/database, > > the migration script gets run on the production db. > > > > We also periodically do a dump of the entire db, but most changes > are > > tracked on an incremental, migration-basis. > > > My problem is that versioning the schema isn't enough, since what the > > database holds is some important configuration data that directly > relates to how the application function, and not just what it > displays. > What I want to sandbox are those configuration changes. So I want to > version some of the data, as well as the schema. > > I was looking at various ways of doing incremental dumps into an svn > repo. I was also looking at ways of recording queries, as you > describe, > to run on the production db. > > All great suggestions. I think I'm just going to have to do some > experimentaton to find what works best for our deployment. > ___________________________________________________________________________ > Philadelphia Linux Users Group -- > http://www.phillylinux.org > Announcements - > http://lists.phillylinux.org/mailman/listinfo/plug-announce > General Discussion -- > http://lists.phillylinux.org/mailman/listinfo/plug ___________________________________________________________________________ Philadelphia Linux Users Group -- http://www.phillylinux.org Announcements - http://lists.phillylinux.org/mailman/listinfo/plug-announce General Discussion -- http://lists.phillylinux.org/mailman/listinfo/plug
|
|