Date: Mon, 4 Aug 2003 15:29:48 -0400
From: "Chad N. Tindel" <chad@tindel.net>
To: "scott.marlowe" <scott.marlowe@ihs.com>
Cc: "Chad N. Tindel" <chad@tindel.net>,
	Josh Berkus <josh@agliodbs.com>, pgsql-docs@postgresql.org
Subject: Re: Mysql -> Postgresql pitfalls
Message-ID: <20030804192948.GA48747@calma.pair.com>
References: <20030804172617.GB36172@calma.pair.com>
	<Pine.LNX.4.33.0308041256030.10758-100000@css120.ihs.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <Pine.LNX.4.33.0308041256030.10758-100000@css120.ihs.com>
User-Agent: Mutt/1.4i

> > > FWIW, in 7.5 we're likely to implement SQL3 IDENTITY columns ... basically 
> > > just a SERIAL column where you don't have the option of inserting your own 
> > > value, you have to take what it gives you.
> > 
> > Interesting... how do you import data from a dump with such columsn?
> 
> Easy, after you import the last row, you
> 
> select setval('seqname',lastvalue);
> 
> on the sequence.  Like I said above, it's mostly just a different way of 
> doing things in Postgresql, and often those different ways are less 
> obvious, and quite often, being less obvious is actually safer even if 
> it is a littler harder to learn up front.

But you just said that I can't actually include the id column in an insert 
query.  So how would I import data from a dump and ensure that the id columns
are what I expect them to be?

Chad