Re: lastval()

From: Bruce Momjian <pgman(at)candle(dot)pha(dot)pa(dot)us>
To: Neil Conway <neilc(at)samurai(dot)com>
Cc: Dennis Bjorklund <db(at)zigo(dot)dhs(dot)org>, pgsql-patches(at)postgresql(dot)org
Subject: Re: lastval()
Date: 2005-05-11 01:50:24
Message-ID: 200505110150.j4B1oOM15896@candle.pha.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-hackers pgsql-patches

Neil Conway wrote:
> 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 like the idea of lastval, though I would rather see us just use
currval() with no argument for it, rather than invent a new function
name. It does the same as currval('last sequence called') right?

--
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

In response to

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 2005-05-11 01:53:11 Re: --enable-thread-safety?
Previous Message Bruce Momjian 2005-05-11 01:49:13 Re: Oracle Style packages on postgres

Browse pgsql-patches by date

  From Date Subject
Next Message Christopher Kings-Lynne 2005-05-11 01:58:34 Re: lastval()
Previous Message Neil Conway 2005-05-11 01:42:02 Re: pgstat: reduce message header