Peter Eisentraut wrote:
>
> 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.
I can buy that. Ok, const isn't a good name.
How about 'immutable' ?
