Re: SERIAL Field
От | Dan Langille |
---|---|
Тема | Re: SERIAL Field |
Дата | |
Msg-id | 20010507142738.DE7B63F43@bast.unixathome.org обсуждение исходный текст |
Ответ на | Re: SERIAL Field ("Joel Burton" <joel@joelburton.com>) |
Ответы |
Re: SERIAL Field
|
Список | 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 по дате отправления: