From: | "John Hansen" <john(at)geeknet(dot)com(dot)au> |
---|---|
To: | "Neil Conway" <neilc(at)samurai(dot)com>, "Dennis Bjorklund" <db(at)zigo(dot)dhs(dot)org> |
Cc: | <pgsql-patches(at)postgresql(dot)org> |
Subject: | Re: lastval() |
Date: | 2005-05-11 03:20:04 |
Message-ID: | 5066E5A966339E42AA04BA10BA706AE50A931B@rodrick.geeknet.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
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.
> I like the concept, but I haven't looked at the code -- I'd
> be happy to review the implementation, although I won't waste
> my time if most people are opposed to the idea itself.
>
> -Neil
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 7: don't forget to increase your free space map settings
>
>
.. John
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 2005-05-11 03:26:36 | Re: lastval() |
Previous Message | Abhijit Menon-Sen | 2005-05-11 02:52:46 | Re: lastval() |