Thread

1. Re: [HACKERS] Re: [PATCHES] Changes to sequence.c

   bill.allie@mug.org — 1998-03-06T03:44:31Z

   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.Allie@mug.org
   |  /|      | 7436 Hartwell     | Compuserve: 76337,2061
   |-/-|----- | Dearborn, MI 48126| MSN.......: B_G_Allie@email.msn.com
   |/  |LLIE  | (313) 582-1540    | 
   
   
   
   

2. Re: [HACKERS] Re: [PATCHES] Changes to sequence.c

   Vadim Mikheev <vadim@sable.krasnoyarsk.su> — 1998-03-06T12:39:58Z

   Billy G. Allie wrote:
   > 
   > 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.
   
   Actually, what you are proposing was initial behaviour of currval().
   This was changed to be more consistent with 1. & 2. (note - not only 1.,
   but 2. also).
   
   But personally I haven't objection against changing this again.
   Men, vote pls!
   
   Vadim