Chris Browne <cbbro...@acm.org> writes:
> I'm not sure I'd *want* to have a more-sophisticated scoping mechanism
> for this.
We already have an appropriate language-level solution for this: it's
called INSERT RETURNING.
The fact is that lastval was invented to aid in porting brain-dead
mysql applications that weren't going to do anything as complicated
as execute commands that might involve more than one nextval call.
If there is any remote possibility that your app might have to deal
with such a thing, you shouldn't be using lastval.
Before considering complicating the definition of lastval, I'd vote
for removing it entirely. It's a foot-gun and will never be anything
but.
regards, tom lane
--
Sent via pgsql-bugs mailing list (pgsql-bugs@postgresql.org)
To make changes to your subscription:
http://www.postgresql.org/mailpref/pgsql-bugs
