From: | Zeugswetter Andreas SB <ZeugswetterA(at)wien(dot)spardat(dot)at> |
---|---|
To: | "'Bruce Momjian'" <pgman(at)candle(dot)pha(dot)pa(dot)us>, Alessio Bragadini <alessio(at)albourne(dot)com> |
Cc: | Peter Eisentraut <peter_e(at)gmx(dot)net>, XosÉ Vázquez <xose(at)wanadoo(dot)es>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
Subject: | AW: Re: postgres TODO |
Date: | 2000-07-10 13:38:56 |
Message-ID: | 11C1E6749A55D411A9670001FA687963367FEB@sdexcsrv1.f000.d0188.sd.spardat.at |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> > Peter Eisentraut wrote:
> >
> > > Bruce Momjian writes:
> > >
> > > > * Add function to return primary key value on INSERT
> > >
> > > I don't get the point of this. Don't you know what you
> inserted? For
> > > sequences there's curval()
> >
> > Mmmhhh... it means that we can assume no update to the
> sequence value
> > between the insert and the curval selection?
>
> No curval() is per-backend value that is not affected by other users.
> My book has a mention of that issue, and so does the FAQ.
Not all default values need to be a sequence, thus imho
this function is a useful extension. ODBC has it too.
Andreas
From | Date | Subject | |
---|---|---|---|
Next Message | Karel Zak | 2000-07-10 13:43:41 | memory: bug or feature |
Previous Message | Zeugswetter Andreas SB | 2000-07-10 13:32:45 | AW: Re: [GENERAL] PostgreSQL vs. MySQL |