Re: Suggestions please: names for function cachability

Peter Eisentraut <peter_e@gmx.net>

From: Peter Eisentraut <peter_e@gmx.net>
To: Tom Lane <tgl@sss.pgh.pa.us>
Cc: mlw <markw@mohawksoft.com>, <pgsql-hackers@postgresql.org>
Date: 2002-04-03T16:54:20Z
Lists: pgsql-hackers
Tom Lane writes:

> mlw <markw@mohawksoft.com> writes:
> > (1) const or constant
> > (2) cacheable
> > (3) volatile
>
> I was wondering about "const" for case 1, also.  I think there is some
> precedent for using "const" with this meaning in other programming
> languages.

I think the meaning of "const" tends to be "cannot change the result" --
which may actually make sense in SQL in a future life if you can pass
around table descriptors or cursor references.

-- 
Peter Eisentraut   peter_e@gmx.net