Re: SERIAL Field - Mailing list pgsql-admin

From Dan Langille
Subject Re: SERIAL Field
Date
Msg-id 20010507142738.DE7B63F43@bast.unixathome.org
Whole thread Raw
In response to Re: SERIAL Field  ("Joel Burton" <joel@joelburton.com>)
Responses Re: SERIAL Field  (Joel Stevenson <jstevenson@bearriver.com>)
List pgsql-admin
On 6 May 2002 at 12:43, Joel Burton wrote:

> > -----Original Message-----
> > From: Dan Langille [mailto:dan@langille.org]
> > Sent: Monday, May 06, 2002 12:41 PM
> > To: Joel Burton
> > Cc: pgsql-admin@postgresql.org
> > Subject: Re: [ADMIN] SERIAL Field
> >
> > > In any event, inserting then using currval() is the standard practice
> > > around here, and it works great. Nothing fishy at all here,
> > nothing to see,
> > > move on.
> >
> > Why is that "less risk"?
>
> It's not; nextval() is just fine. I was half asleep and thinking, I think,
> of another database when I wrote that.
>
> "You say nextval() + write, I say write + currval()..."

So long as a given application does not mix the two approaches, everything
should be fine.
--
Dan Langille
The FreeBSD Diary - http://freebsddiary.org/ - practical examples


pgsql-admin by date:

Previous
From: "Joel Burton"
Date:
Subject: Re: SERIAL Field
Next
From: Brian McCane
Date:
Subject: Re: SERIAL Field