Re: [GENERAL] immutable stable volatile

2004-12-06 Thread Tom Lane
"PostgreSQL general mail list" <[EMAIL PROTECTED]> writes: > if a function does insert/update/delete it needs to be stable or volatile ? > if a immutable function executes 'nextval' should itself be also volatile ? A function that has side-effects must be marked volatile; there are no exceptions.

[GENERAL] immutable stable volatile

2004-12-06 Thread PostgreSQL general mail list
hello, I have read the documentation couple of times and I still can not figure out the following aspects. if a function does insert/update/delete it needs to be stable or volatile ? if a immutable function executes 'nextval' should itself be also volatile ? thanks, Razvan Radu

[GENERAL] immutable stable volatile

2004-12-06 Thread pgsql-general
hello, I have read the documentation couple of times and I still can not figure out the following aspects. if a function does insert/update/delete it needs to be stable or volatile ? if a immutable function executes 'nextval' should itself be also volatile ? thanks, Razvan Radu ---