Re: OT: Configuration management for stateful data

On Wed, 2003-06-25 at 14:33, Bruce Atherton wrote:
> The upside to this is that it migrates schema changes to each environment
> synchronized with the release that depends on them. The downsides are that
> it is not easily reversible, and it provides no mechanism to return to the
> state at a particular release. I'm still looking for a good answer to that one.

I'm slowly coming to the conclusion that without "versioning" support
behind where the schema and data are being stored, it's always going
to be a process that is prone to human error (we're finding that people
are forgetting to run patches or running patches twice and deliberately
bypassing the safety checks (i.e. a "patch table" that lists applied
patches that the patches themselves check and update)).

All the versioning operations, such as diff, log and merge all have
use-cases in the data world as well.

Perhaps Subversion itself may find a nice market as a versioned database
:)

Subwiki may be the first example of a step towards this
(subwiki.tigris.org), it'd be interesting to attempt to map a relational
schema into a file tree....

daniel

-- 
Signature at:  http://www.mel.au.adaptiveinternational.com/~danpat/signature.txt
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org