Steve Jorgensen wrote:
Well, besides being able to back out the changes, it has a standard way
of determining the current database schema version, and applying all the
migrations necessary, regardless of how far behind (or not) the
production environment has become.
I don't understand how this is always guaranteed to be possible...
...for example if you add a column that is "not null", but doesn't have
a default value, no script magic can know what new values are appropriate...
-Dale
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
