Re: Unclear documentation (IMMUTABLE functions)

Not my place to say, but...

I think this likely should be worded something like this (if true):
...
Also note that the current_timestamp family of functions qualify as stable,
since their values do not change within SQL statement, and to be more
concise the current_timestamp functions do not change within a transaction.

Terry Fielder
Manager Software Development and Deployment
Great Gulf Homes / Ashton Woods Homes
terry(at)greatgulfhomes(dot)com
Fax: (416) 441-9085

> -----Original Message-----
> From: pgsql-bugs-owner(at)postgresql(dot)org
> [mailto:pgsql-bugs-owner(at)postgresql(dot)org]On Behalf Of Neil Conway
> Sent: Friday, September 05, 2003 2:32 PM
> To: Stephan Szabo
> Cc: Daniel Schreiber; pgsql-bugs(at)postgresql(dot)org
> Subject: Re: [BUGS] Unclear documentation (IMMUTABLE functions)
>
>
> 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
>
>
>
> ---------------------------(end of
> broadcast)---------------------------
> TIP 6: Have you searched our list archives?
>
> http://archives.postgresql.org
>