Version database structure and content

Hi,

I'm looking for a way to handle database structure and data maintenance in way
that would make changing the structure versioned and controlled. What I
imagine is something akin to Rails::Migrations, where each version had a
piece of code to upgrade the database from the previous version to the this
version, and another to downgrade this version to the previous version. Some
rake (ruby make) scripts meant that I could write

rake db/migrate

or something in that order to get the database into current version, and

rake db/migrate VERSION=007

to get it to version 7.

However, Rails::Migrations is tightly tied to rails (big surprise). Does
anyone know of an alternative to Rails::Migrations, which might be reasonable
to use in a non-rails project?

Thanks!
--
regards, Esben

--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.