| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | Brett McCormick <brett(at)work(dot)chicken(dot)org> |
| Cc: | pgsql-hackers(at)hub(dot)org |
| Subject: | Re: [HACKERS] sequences |
| Date: | 1998-02-26 03:40:23 |
| Message-ID: | 34F4E427.75B79BD3@sable.krasnoyarsk.su |
| 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 ?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Bruce Momjian | 1998-02-26 03:43:48 | Re: [PORTS] alpha/64bit & mkoidname problem |
| Previous Message | Brett McCormick | 1998-02-26 03:34:12 | alpha/64bit & mkoidname problem |