Yes please... ... That's exactly what I've been asking for....
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] On Behalf Of Neil Conway > Sent: Monday, June 06, 2005 12:18 PM > To: Dennis Bjorklund > Cc: pgsql-patches@postgresql.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 > > ---------------------------(end of broadcast)--------------------------- TIP 1: subscribe and unsubscribe commands go to [EMAIL PROTECTED]
