| From: | Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us> |
|---|---|
| To: | John Hansen <john(at)geeknet(dot)com(dot)au> |
| Cc: | Neil Conway <neilc(at)samurai(dot)com>, Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, pgsql-patches(at)postgresql(dot)org |
| Subject: | Re: lastval() |
| Date: | 2005-05-11 03:26:36 |
| Message-ID: | 200505110326.j4B3QaL00310@candle.pha.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-patches |
John Hansen wrote:
> Neil Conway wrote:
> > Sent: Wednesday, May 11, 2005 10:56 AM
> > To: Dennis Bjorklund
> > Cc: pgsql-patches(at)postgresql(dot)org
> > Subject: Re: [PATCHES] lastval()
> >
> > Dennis Bjorklund wrote:
> > > Here is a small patch that implements a function lastval()
> > that works
> > > just like currval() except that it give the current value
> > of the last
> > > sequence used by nextval().
> >
> > What do people think of this idea? (Tom seems opposed, I'm
> > just wondering if there are other opinions out there.)
>
> I'm all for it. Even more so if the 'currval(void) called before
> nextval(seq_name)' error message could be supressed by a GUC variable
> and return 0 instead.
Why zero and no error?
--
Bruce Momjian | http://candle.pha.pa.us
pgman(at)candle(dot)pha(dot)pa(dot)us | (610) 359-1001
+ If your life is a hard drive, | 13 Roberts Road
+ Christ can be your backup. | Newtown Square, Pennsylvania 19073
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 2005-05-11 03:30:05 | Re: lastval() |
| Previous Message | John Hansen | 2005-05-11 03:20:04 | Re: lastval() |