From: | Peter Eisentraut <peter_e(at)gmx(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | mlw <markw(at)mohawksoft(dot)com>, <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: Suggestions please: names for function cachability |
Date: | 2002-04-03 16:54:20 |
Message-ID: | Pine.LNX.4.30.0204031152470.684-100000@peter.localdomain |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general pgsql-hackers |
Tom Lane writes:
> mlw <markw(at)mohawksoft(dot)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(at)gmx(dot)net
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-03 16:57:26 | Re: Suggestions please: names for function cachability |
Previous Message | mlw | 2002-04-03 16:46:37 | Re: Suggestions please: names for function |
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2002-04-03 16:57:26 | Re: Suggestions please: names for function cachability |
Previous Message | mlw | 2002-04-03 16:46:37 | Re: Suggestions please: names for function |