Re: [agileDatabases] Re: Oracle development and Subversion
- dbdeploy does the exact thing, if you don't have Ruby on Rails on your
project you can use DBdeploy.
On 2/26/07, jeffz_2002 <jeffz_2002@...> wrote:
> of course the database needs a way of "remembering" its current schema
> > version. but this can be solved quite easily by persisting the version
> > number in some object, be it a table, udf, or other mechanism after a
> > migration has succeeded.
> FYI, this is what Ruby on Rails does. The db table is called
> schema_info and contains a single field, version. The files are named
> ###_products, where ### is the number of the script (in Rails,
> called "migrations"). Then you can use Rake (a builder, like Ant) and
> say > rake db:migrate, and Rake determines which file(s) to run. Rails
> also has the concept of migrating "up" and "down" (to later/earlier
> versions), so the migration scripts have 2 parts.
> Just in case people don't already know ...
[Non-text portions of this message have been removed]