From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | brian(dot)williams(at)mayalane(dot)com, pgsql-docs(at)lists(dot)postgresql(dot)org |
Subject: | Re: Nit: "Immutable" should be "pure" |
Date: | 2019-11-07 17:38:11 |
Message-ID: | 14397.1573148291@sss.pgh.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-docs |
Bruce Momjian <bruce(at)momjian(dot)us> writes:
> On Thu, Nov 7, 2019 at 02:17:58PM +0000, PG Doc comments form wrote:
>> The adjective "immutable" describing the functions and operators used in an
>> index (see two occurrences in doc snippet below) is incorrect and should be
>> replaced with "pure".
> I think the best we can do is to mention that IMMUTABLE functions mean
> pure, but I am not sure there is even enough demand for that, vs.
> confusing people.
Yeah. I don't think this terminology is nearly as universal
as the OP believes, so I don't feel a need to change anything.
If we adopt Corey's proposal to create a glossary [1], there'd be
room for a parenthetical comment like "(In some circles, "pure" is the
preferred term for this function property.)" in the glossary entry for
"immutable". I suspect it won't be the only entry that needs
cross-references to other terminology.
regards, tom lane
From | Date | Subject | |
---|---|---|---|
Next Message | Brian Williams | 2019-11-07 18:04:28 | Re: Nit: "Immutable" should be "pure" |
Previous Message | Bruce Momjian | 2019-11-07 17:28:30 | Re: Nit: "Immutable" should be "pure" |