Re: UPDATE using query; per-row function calling problem

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: pasman pasmański <pasman(dot)p(at)gmail(dot)com>
Cc: pgsql-general(at)postgresql(dot)org
Subject: Re: UPDATE using query; per-row function calling problem
Date: 2011-09-02 17:20:26
Message-ID: 19724.1314984026@sss.pgh.pa.us
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-general

=?ISO-8859-2?Q?pasman_pasma=F1ski?= <pasman(dot)p(at)gmail(dot)com> writes:
> That's interpretation of subselect is ok, when it contains only stable
> functions.

> Maybe add a warning when subselect contains volatile function.

We're not likely to do that, because this sort of notation is actually
fairly commonly used to hide the volatility of non-stable functions.

regards, tom lane

In response to

Browse pgsql-general by date

  From Date Subject
Next Message Bob Pawley 2011-09-02 17:33:22 Re: Variable column name
Previous Message pasman pasmański 2011-09-02 14:48:34 Re: UPDATE using query; per-row function calling problem