Skip site navigation (1) Skip section navigation (2)

Re: currval() within one statement

From: sad <sad(at)bankir(dot)ru>
To: pgsql-sql(at)postgresql(dot)org
Subject: Re: currval() within one statement
Date: 2008-01-22 07:54:58
Message-ID: (view raw, whole thread or download thread mbox)
Lists: pgsql-sql
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.

In response to


pgsql-sql by date

Next:From: Stuart BrooksDate: 2008-01-22 08:05:04
Subject: TIMESTAMP comparison problem
Previous:From: A. KretschmerDate: 2008-01-22 07:36:37
Subject: Re: currval() within one statement

Privacy Policy | About PostgreSQL
Copyright © 1996-2017 The PostgreSQL Global Development Group