[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Version control of Databases

From: Frank Gruman <fgatwork_at_verizon.net>
Date: 2005-06-09 20:38:36 CEST

We are also using Oracle.

No biggie. We use TOAD, and there is (with the pricier license, of
course) a DB Compare tool that will automagically create your scripts
for you. If necessary, run this tool just before you do a branch (or
after) and save that in. The other option - when they make a change
through their GUI tools is to then take a snapshot of the DDL and save
that out, saving it as the actual object name (with the object type as
the extension).

Of course - your developers may choose option 1 because it's work they
don't have to do. But then how do you track which developer is making
which change to your DB?


Gabor Szabo wrote:

>Thanks for the suggestions so far.
>I am sure they fit small teams of 1-5 ppl (I do similar things) but I
>wonder if they fit
>larger teams.
>What I forgot to mention that we are dealing here with Oracle and a
>slow company.
>When I mentioned them that the developers will have to write scripts to update
>the database they wanted to run away.
>They want to have some wizzard or GUI tool to maintain the database
>(e.g. SQL Navigator)
>and then they somehow want to have the upgrade script magically.
>To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
>For additional commands, e-mail: users-help@subversion.tigris.org

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Jun 9 20:40:37 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.