From: sad <sad@bankir.ru>
To: pgsql-sql@postgresql.org
Subject: Re: currval() within one statement
Date: Tue, 22 Jan 2008 10:54:58 +0300
Message-ID: <4795A152.3080400@bankir.ru> (raw)
In-Reply-To: <20080122073637.GB21676@a-kretschmer.de>
References: <4795984E.7030904@bankir.ru>
<20080122073637.GB21676@a-kretschmer.de>
A. Kretschmer wrote:
>> is it expected that the currval() changes its value between calls within
>> one statement ?
> Conclusion, don't call nextval() within a TRIGGER, and insert either
> nextval() for the column or omit this column.
I only note that i still want to discuss the titled problem or to be
given an exact pointer to documentation regarding the currval() behavior
in the described situation, that i had.
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Reply to all the recipients using the --to and --cc options:
reply via email
To: pgsql-sql@postgresql.org
Cc: sad@bankir.ru
Subject: Re: currval() within one statement
In-Reply-To: <4795A152.3080400@bankir.ru>
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
This inbox is served by DDX for PostgreSQL; see mirroring instructions
for how to clone and mirror all data and code used for this inbox