| From: | "Billy G(dot) Allie" <Bill(dot)Allie(at)mug(dot)org> |
|---|---|
| To: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
| Cc: | pgsql-patches(at)postgreSQL(dot)org, pgsql-hackers(at)postgreSQL(dot)org |
| Subject: | Re: [HACKERS] Re: [PATCHES] Changes to sequence.c |
| Date: | 1998-03-06 03:44:31 |
| Message-ID: | m0yAo3j-0009kAC@bgalli.mug.org |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Vadim B. Mikheev wrote:
>Billy G. Allie wrote:
>>
>> I encountered a problem (bug? feature?) where "select currval('sequence')"
>> will generate an error if "select nextval('sequence')" is not executed
first.
>
>This is feature :)
>1. This is what Oracle does.
>2. currval () is described as returning value returned by
> last nextval() in _session_.
>
>Vadim
>
Does this mean we should not modify this behavior because "this is what Oracle
does"? I can envision where using currval() before nextval() can be useful.
--
____ | Billy G. Allie | Domain....: Bill(dot)Allie(at)mug(dot)org
| /| | 7436 Hartwell | Compuserve: 76337,2061
|-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie(at)email(dot)msn(dot)com
|/ |LLIE | (313) 582-1540 |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | D'Arcy J.M. Cain | 1998-03-06 05:14:44 | PyGreSQL 2.1 released |
| Previous Message | Vadim B. Mikheev | 1998-03-06 02:25:46 | Re: WG: [QUESTIONS] Re: [HACKERS] text should be a blob field |