Skip site navigation (1) Skip section navigation (2)

Re: Mysql -> Postgresql pitfalls

From: "Chad N(dot) Tindel" <chad(at)tindel(dot)net>
To: Josh Berkus <josh(at)agliodbs(dot)com>
Cc: "scott(dot)marlowe" <scott(dot)marlowe(at)ihs(dot)com>,pgsql-docs(at)postgresql(dot)org
Subject: Re: Mysql -> Postgresql pitfalls
Date: 2003-08-04 17:26:17
Message-ID: 20030804172617.GB36172@calma.pair.com (view raw or flat)
Thread:
Lists: pgsql-docs
> > > Yes.  The documentation very clearly states using sequences instead of
> > > auto-increment, but it doesn't make it clear that inserting the id's into
> > > data by hand doesn't cause the sequence to be auto-matically incremented.
> > >  It'd be nice of postgres had a way to trigger an update of the sequence
> > > value after every insert containing an id clumn.
> 
> Um, how would this be a bennefit?   If you're inserting rows 101-259, how does 
In mysql, when you insert into an auto_increment field and you specify an id, 
all future requests to insert a row without specifying the ID will still work
properly.  In postgres, if you specify the id, your next insert without and
id will fail because the sequence won't have been updated.

> 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?

Chad

In response to

Responses

pgsql-docs by date

Next:From: Lamar OwenDate: 2003-08-04 17:27:59
Subject: Re: Mysql -> Postgresql pitfalls
Previous:From: Chad N. TindelDate: 2003-08-04 17:23:02
Subject: Re: Mysql -> Postgresql pitfalls

Privacy Policy | About PostgreSQL
Copyright © 1996-2014 The PostgreSQL Global Development Group