Re: SERIAL Field - Mailing list pgsql-admin

From Joel Burton
Subject Re: SERIAL Field
Date
Msg-id JGEPJNMCKODMDHGOBKDNOEPLCMAA.joel@joelburton.com
Whole thread Raw
In response to Re: SERIAL Field  ("Dan Langille" <dan@langille.org>)
Responses Re: SERIAL Field  ("Dan Langille" <dan@langille.org>)
List pgsql-admin
> -----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()..."

J.

Joel BURTON | joel@joelburton.com | joelburton.com | aim: wjoelburton
Knowledge Management & Technology Consultant


pgsql-admin by date:

Previous
From: "Dan Langille"
Date:
Subject: Re: SERIAL Field
Next
From: "Dan Langille"
Date:
Subject: Re: SERIAL Field