From: | "Igal (at) Lucee(dot)org" <igal(at)lucee(dot)org> |
---|---|
To: | "David G(dot) Johnston" <david(dot)g(dot)johnston(at)gmail(dot)com> |
Cc: | pgsql-general <pgsql-general(at)postgresql(dot)org> |
Subject: | Re: Function Volatility Stable vs Immutable |
Date: | 2019-06-25 02:54:27 |
Message-ID: | fc4f4a3c-8aec-b559-a655-f76b43e7ee6a@lucee.org |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-general |
On 6/24/2019 7:38 PM, David G. Johnston wrote:
> On Mon, Jun 24, 2019 at 7:31 PM Igal @ Lucee.org <igal(at)lucee(dot)org
> <mailto:igal(at)lucee(dot)org>> wrote:
>
> If a function select data from a table, and the rows in the table may
> change, would that function qualify for Immutable or does it have
> to be
> Stable? I'm asking because according to the docs [1]: "An IMMUTABLE
> function cannot modify the database and is guaranteed to return
> the same
> results given the same arguments forever".
>
> So for the same arguments, the result would change only if the
> data in
> the table changes. Does that mean that it violates the "forever"
> clause
> and therefore can be only marked as Stable and not Immutable?
>
>
> Yes
>
> Forever means beyond the lifetime of a single transaction and thus it
> is possible for the changing of the table contents to impact the
> return value of the function.
Thanks for clarifying, David.
Igal
From | Date | Subject | |
---|---|---|---|
Next Message | Adrian Klaver | 2019-06-25 04:13:57 | Re: minor upgrade |
Previous Message | David G. Johnston | 2019-06-25 02:38:33 | Re: Function Volatility Stable vs Immutable |