Re: Roadmap for FE/BE protocol redesign - Mailing list pgsql-hackers

From Tom Lane
Subject Re: Roadmap for FE/BE protocol redesign
Date
Msg-id 13358.1048263075@sss.pgh.pa.us
Whole thread Raw
In response to Re: Roadmap for FE/BE protocol redesign  (Bruce Momjian <pgman@candle.pha.pa.us>)
Responses Re: Roadmap for FE/BE protocol redesign  (Bruce Momjian <pgman@candle.pha.pa.us>)
List pgsql-hackers
Bruce Momjian <pgman@candle.pha.pa.us> writes:
> What I was wondering is if we could create a currval() call that takes
> no arguments, and returns the most recent sequence id assigned.

Why?  That's still an extra query that the client has to issue, and
currval in that form would be an amazingly fragile programming tool.
(What if some trigger causes an autoincrement on some other sequence
than the one you are thinking about?)

I liked the INSERT ... RETURNING and UPDATE ... RETURNING syntax
extensions that Philip Warner (IIRC) proposed awhile back.  Those would
get the job done much more flexibly than anything else that's been
suggested.  That's why I think it's a language problem and not a
protocol problem.
        regards, tom lane


pgsql-hackers by date:

Previous
From: Dave Cramer
Date:
Subject: Re: Roadmap for FE/BE protocol redesign
Next
From: Bruce Momjian
Date:
Subject: Re: Roadmap for FE/BE protocol redesign