From: | Andrew Dunstan <andrew(at)dunslane(dot)net> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, 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 17:58:21 |
Message-ID: | 5664773D.8080702@dunslane.net |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
On 12/06/2015 11:03 AM, Tom Lane wrote:
> 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.
>
>
I would stick with "volatility". It makes for consistency - pg_proc has
"provolatile" for example. I think it's a moderately well understood
term in the Postgres world.
cheers
andrew
From | Date | Subject | |
---|---|---|---|
Next Message | Olson, Ken | 2015-12-06 19:16:24 | Re: dynloader.h missing in prebuilt package for Windows? |
Previous Message | Andreas Seltenreich | 2015-12-06 17:52:26 | [sqlsmith] Failed to generate plan on lateral subqueries |