On Mon, Sep 22, 2008 at 03:25:35AM +1000, Naz wrote: > Hi all, > I brought this up a few years ago in the 7.4 days, and since there > is still no satisfactory solution to this I thought I'd raise it > again. When dumping a schema, it is often necessary to dump the > tables separately to the constraints and other non-structural > metadata. The most obvious use case for this is when updating a > schema for a database. > > Assume I have a database named "production" and one named "testing".
Good so far. > Lets now say that I have decided that "testing" is correct and the > app is ready to work with it, and I now want to put the data from > "production" into the schema from "testing". That's where you should have been storing all the SQL transformations (DDL, DCL and DML) in your source code management system and testing said transformations to make sure they all fit inside one transaction :) > I hope someone agrees with me :) The above is what I've seen work. Other schemes...not so well. > السلام عليكم And upon you, peace. David. -- David Fetter <[EMAIL PROTECTED]> http://fetter.org/ Phone: +1 415 235 3778 AIM: dfetter666 Yahoo!: dfetter Skype: davidfetter XMPP: [EMAIL PROTECTED] Remember to vote! Consider donating to Postgres: http://www.postgresql.org/about/donate -- Sent via pgsql-hackers mailing list (pgsql-hackers@postgresql.org) To make changes to your subscription: http://www.postgresql.org/mailpref/pgsql-hackers
