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-06-06 10:15:37 |
Message-ID: | 5066E5A966339E42AA04BA10BA706AE50A9335@rodrick.geeknet.com.au |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-patches |
Yes please...
... That's exactly what I've been asking for....
> -----Original Message-----
> From: pgsql-patches-owner(at)postgresql(dot)org
> [mailto:pgsql-patches-owner(at)postgresql(dot)org] On Behalf Of Neil Conway
> Sent: Monday, June 06, 2005 12:18 PM
> To: Dennis Bjorklund
> Cc: pgsql-patches(at)postgresql(dot)org
> Subject: Re: [PATCHES] lastval()
>
> If you're busy, I can clean this up and apply it.
>
> I wonder if it would be better to have lastval() return the
> last value returned by nextval() or setval() for the current
> session, regardless of any intervening DROP SEQUENCE
> commands. This would simplify the implementation (we can just
> store the int8 value produced by the last
> nextval() / setval() rather than a pointer to the sequence
> object itself), although it is debatable whether this
> behavior is more logical or not. Comments?
>
> -Neil
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>
>
From | Date | Subject | |
---|---|---|---|
Next Message | Christopher Kings-Lynne | 2005-06-06 13:33:22 | Re: lastval() |
Previous Message | Pavel Stehule | 2005-06-06 08:36:57 | Re: SQLSTATE again |