Re: [Info-ingres] sequence .nextval evaluating twice when used inside an INSERT cmd
- From: Betty & Karl Schendel <schendel@xxxxxxxxxxxxxx>
- Date: Fri, 22 Jul 2005 09:46:50 -0400
At 2:42 PM +0100 7/22/05, morgan brickley wrote:
Call anyone spot the difference in the newsessionid value in these two examples ?
[snipped]
In the first the newsessionid being called twice whereas in the second it gets called once (the expected behaviour). It seems that if you use a sequence directly as a parameter it gets stepped twice. Not using it as a paramter directly solves the issue.
I think I saw an R3 bug-fix for something like this very recently. It wouldn't be in the current posted builds yet.
Karl .
- References:
- sequence .nextval evaluating twice when used inside an INSERT cmd
- From: morgan brickley
- sequence .nextval evaluating twice when used inside an INSERT cmd
- Prev by Date: sequence .nextval evaluating twice when used inside an INSERT cmd
- Next by Date: Re: [Info-ingres] session tenporary tables and STAR ddbs
- Previous by thread: sequence .nextval evaluating twice when used inside an INSERT cmd
- Next by thread: INGRES SREPORT Problem (solved)
- Index(es):
Relevant Pages
|