On 8/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I have a question about whether I can safely declare a function IMMUTABLE.
> Citing the documentation under "Function Volatility Categories" in the
> section on "Extending SQL":
>
> It is
On 8/27/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> Well, I am considering a function that does read from a table, but the
> table contents change extremely infrequently (the table is practically a
> list of constants). Would it be safe to declare the function IMMUTABLE
> provided that the
Hello,
I have a question about whether I can safely declare a function IMMUTABLE.
Citing the documentation under "Function Volatility Categories" in the
section on "Extending SQL":
It is generally unwise to select from database tables within an IMMUTABLE
"Tom Lane" <[EMAIL PROTECTED]> writes:
> [EMAIL PROTECTED] writes:
>> Well, I am considering a function that does select from a table, but the
>> table contents change extremely infrequently (the table is practically a
>> list of constants). Would it be safe to declare the function IMMUTABLE
[EMAIL PROTECTED] writes:
> Well, I am considering a function that does select from a table, but the
> table contents change extremely infrequently (the table is practically a
> list of constants). Would it be safe to declare the function IMMUTABLE
> provided that the table itself is endowed wi
Hello,
I have a question about whether I can safely declare a function IMMUTABLE.
Citing the PostgreSQL documentation under "Function Volatility
Categories" in the section on "Extending SQL":
It is generally unwise to select from database tables within a
In response to [EMAIL PROTECTED]:
> Hello,
>
> I have a question about whether I can safely declare a function IMMUTABLE.
> Citing the PostgreSQL documentation under "Function Volatility
> Categories" in the section on "Extending SQL":
>
> It is general
