pg.ddx.io  pgsql-docs@postgresql.org mailing list archive  
help / color / mirror / Atom feed
From: Josh Berkus <josh@agliodbs.com>
To: scott.marlowe <scott.marlowe@ihs.com>
To: Chad N. Tindel <chad@tindel.net>
Cc: pgsql-docs@postgresql.org
Subject: Re: Mysql -> Postgresql pitfalls
Date: Mon, 4 Aug 2003 09:49:01 -0700
Message-ID: <200308040949.01128.josh@agliodbs.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0308040910090.10259-100000@css120.ihs.com>
References: <Pine.LNX.4.33.0308040910090.10259-100000@css120.ihs.com>

Chad, Scott:

> > 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 
it benefit you to have the system automatically increment the sequence from 
601-759?

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.

-- 
Josh Berkus
Aglio Database Solutions
San Francisco



view thread (26+ messages)  latest in thread

Message-ID: <200308040949.01128.josh@agliodbs.com>
Permalink:  ../200308040949.01128.josh@agliodbs.com/
Also on:    postgresql.org/message-id/200308040949.01128.josh@agliodbs.com

 · 

reply

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-docs@postgresql.org
  Cc: josh@agliodbs.com, scott.marlowe@ihs.com, chad@tindel.net
  Subject: Re: Mysql -> Postgresql pitfalls
  In-Reply-To: <200308040949.01128.josh@agliodbs.com>

* 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