Re: Unclear documentation (IMMUTABLE functions)
От
Neil Conway
Тема
Re: Unclear documentation (IMMUTABLE functions)
Дата
Msg-id
1062786722.447.5.camel@tokyo
Ответ на
Re: Unclear documentation (IMMUTABLE functions) (Stephan Szabo)
Список
Дерево обсуждения
Unclear documentation (IMMUTABLE functions) Daniel Schreiber <daniel.schreiber@s1999.tu-chemnitz.de>
Re: Unclear documentation (IMMUTABLE functions) Tom Lane <tgl@sss.pgh.pa.us>
Re: Unclear documentation (IMMUTABLE functions) Daniel Schreiber <daniel.schreiber@s1999.tu-chemnitz.de>
Re: Unclear documentation (IMMUTABLE functions) Tom Lane <tgl@sss.pgh.pa.us>
Re: Unclear documentation (IMMUTABLE functions) Stephan Szabo <sszabo@megazone.bigpanda.com>
Re: Unclear documentation (IMMUTABLE functions) Neil Conway <neilc@samurai.com>
Re: Unclear documentation (IMMUTABLE functions) terry@greatgulfhomes.com
Re: Unclear documentation (IMMUTABLE functions) Tom Lane <tgl@sss.pgh.pa.us>
Re: Unclear documentation (IMMUTABLE functions) Daniel Schreiber <daniel.schreiber@s1999.tu-chemnitz.de>
On Fri, 2003-09-05 at 10:01, Stephan Szabo wrote:
> This is the section in create function reference page about immutable. I'd
> thought it was clear, but do you have a better suggested wording?
While we're on the subject, this adjacent paragraph of the docs seems
unclear:
STABLE indicates that within a single table scan the function
will consistently return the same result for the same argument
values, but that its result could change across SQL statements.
This is the appropriate selection for functions whose results
depend on database lookups, parameter variables (such as the
current time zone), etc. Also note that the current_timestamp
family of functions qualify as stable, since their values do not
change within a transaction.
So, can a STABLE function change across SQL statements (as the beginning
of the paragraph implies), or across transactions (as the end of the
paragraph implies)?
-NeilВ списке pgsql-bugs по дате отправления
От: Mendola Gaetano
Дата: