From: Esben Mose Hansen <kde@mosehansen.dk>
To: 'pgsql-admin@postgresql.org' <pgsql-admin@postgresql.org>
Subject: Version database structure and content
Date: Fri, 16 Nov 2007 21:41:53 +0100
Message-ID: <200711162141.53831.kde@mosehansen.dk> (raw)
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.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-admin@postgresql.org
Cc: kde@mosehansen.dk
Subject: Re: Version database structure and content
In-Reply-To: <200711162141.53831.kde@mosehansen.dk>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox