From: | "Michael J(dot) Rogan" <mrogan(at)fpelectronics(dot)com> |
---|---|
To: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su>, pgsql-hackers(at)hub(dot)org |
Subject: | Re: [HACKERS] sequences |
Date: | 1998-02-26 17:37:50 |
Message-ID: | 199802262344.SAA14308@amperes.fpelectronics.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | 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(at)fpelectronics(dot)com mrogan(at)ivhs(dot)com *
From | Date | Subject | |
---|---|---|---|
Next Message | Bruce Momjian | 1998-02-26 18:30:09 | subselects |
Previous Message | Andrew Martin | 1998-02-26 17:15:28 | Re: [HACKERS] Snapshot 26Feb98 - another minor showstopper |