Hey Derek,
I'm using CVS to version-control my Database structure.
What I did is, that I put the original structure in CVS,
and with every new release that needs changes to the database,
I alter the tables *and* as well update the plain create scripts.
In that sense, bringing out a new version, will only alter the Database
instead of creating it anew. When I now deploy a whole new installation,
I use the create scripts that belong to the version. This works pretty well
for me.
Cheers,
Guus
> -----Original Message-----
> From: Derek Scherger [mailto:[EMAIL PROTECTED]]
>
> Views also work pretty well organized the same way but things start to
> get more tricky when you want to put your table definitions into CVS.
> Once tables are populated (and large) it's tough to drop and re-create
> them! So far we have our heads in the sand on this one and
> simply leave
> it up to the DBA's to keep the tables straight. We'd never be able to
> revert to an old release of our database however.
[ rest omitted for brevity ]
