Received: from localhost (unknown [200.46.204.184]) by postgresql.org (Postfix) with ESMTP id 757962E2D71 for ; Fri, 16 Nov 2007 16:42:21 -0400 (AST) Received: from postgresql.org ([200.46.204.71]) by localhost (mx1.hub.org [200.46.204.184]) (amavisd-maia, port 10024) with ESMTP id 07360-05 for ; Fri, 16 Nov 2007 16:42:06 -0400 (AST) Received: from mosehansen.dk (unknown [89.150.121.59]) by postgresql.org (Postfix) with ESMTP id AA7EF2E2D68 for ; Fri, 16 Nov 2007 16:42:18 -0400 (AST) Received: from spurv (unknown [192.168.0.5]) by mosehansen.dk (Postfix) with ESMTP id 101834500F9 for ; Fri, 16 Nov 2007 21:41:54 +0100 (CET) From: Esben Mose Hansen To: "'pgsql-admin@postgresql.org'" Subject: Version database structure and content Date: Fri, 16 Nov 2007 21:41:53 +0100 User-Agent: KMail/1.9.6 (enterprise 0.20070907.709405) MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711162141.53831.kde@mosehansen.dk> X-mosehansen.dk-MailScanner: Found to be clean X-mosehansen.dk-MailScanner-SpamCheck: not spam, SpamAssassin (not cached, score=-4.399, required 6, autolearn=not spam, ALL_TRUSTED -1.80, BAYES_00 -2.60) X-mosehansen.dk-MailScanner-From: kde@mosehansen.dk X-Virus-Scanned: Maia Mailguard 1.0.1 X-Spam-Status: No, hits=0.101 tagged_above=0 required=5 tests=BAYES_50=0.001, RDNS_NONE=0.1 X-Spam-Level: X-Archive-Number: 200711/167 X-Sequence-Number: 27410 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.