Re: [HACKERS] sequences - Mailing list pgsql-hackers

From Michael J. Rogan
Subject Re: [HACKERS] sequences
Date
Msg-id 199802262344.SAA14308@amperes.fpelectronics.com
Whole thread Raw
In response to Re: [HACKERS] sequences  ("Vadim B. Mikheev" <vadim@sable.krasnoyarsk.su>)
List pgsql-hackers
> Brett McCormick wrote:
> >
> > Are there any plans to implement oid-style functionality for
> > sequences, such as returning the nextval in the result tuple somehow?
> >
> > Is it at all possible to implement?  That is one very nice thing about
> > using oid instead, is that it comes back in PQoidStatus.  I probably
> > won't stop using oids until this is possible (i've got my own restore
> > which "preserves" (i.e. renumbers) oid references)
>
> Not possible - sequences are just "a gear", user can use more than
> one sequences in inserts, etc...
>
> But we could return PRIMARY KEY of affected tuple if it exists!
> I kept this feature in mind when thought about removing OID...
>
> Comments ?

This would be very useful.  I never did like the idea of using OID as
reference so a way to get the PIMARY KEY would be  A GOOD THING(tm).

Michael

BTW: I could have sworn the first thing I tried was to grant select on the
sequence I was using when it complianed about access.

>
> Vadim
>
>

* Michael J. Rogan,  Network Administrator,   905-624-3020 *
* Mark IV Industries, F-P Electronics & I.V.H.S. Divisions *
* mrogan@fpelectronics.com                 mrogan@ivhs.com *

pgsql-hackers by date:

Previous
From: Tom I Helbekkmo
Date:
Subject: Re: [HACKERS] Solution to the pg_user passwd problem !?? (c)
Next
From: "Vadim B. Mikheev"
Date:
Subject: Re: [HACKERS] MergeJoin and Mark/Restr scan positions (Re: [PORTS] Port Bug Report)