From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Chapman Flack <chap(at)anastigmatix(dot)net> |
Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org> |
Subject: | Re: a word-choice question |
Date: | 2015-12-06 16:03:23 |
Message-ID: | 10218.1449417803@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
Chapman Flack <chap(at)anastigmatix(dot)net> writes:
> In PL/Java's function annotations, 'type' has been used for the
> volatility category:
> @Function(type=IMMUTABLE)
> public static String hello() { return "Hello, world!"; }
> It seems a bit infelicitous because you would probably sooner guess that
> 'type' was telling you something about the function's _data_ type
Yeah ...
> But I've been trying think of something short, clear, preferably
> monosyllabic, less geeky than 'v8y', and I don't have a winner yet.
Instead of thinking about "volatility", maybe something based on
"stability" or "constancy"? I suppose "const" is too much of a conflict,
but "stable=IMMUTABLE" doesn't seem awful.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Tom Lane | 2015-12-06 16:38:09 | Re: [PATCH] Equivalence Class Filters |
Previous Message | Kouhei Kaigai | 2015-12-06 16:00:07 | Re: CustomScan in a larger structure (RE: CustomScan support on readfuncs.c) |