| From: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
|---|---|
| To: | "Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> |
| Cc: | "Michal szymanski" <szymanskim(at)datera(dot)pl>, pgsql-bugs(at)postgresql(dot)org |
| Subject: | Re: BUG #4516: FOUND variable does not work after RETURN QUERY |
| Date: | 2008-11-06 18:19:31 |
| Message-ID: | 3904.1225995571@sss.pgh.pa.us |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-bugs pgsql-hackers |
"Pavel Stehule" <pavel(dot)stehule(at)gmail(dot)com> writes:
> 2008/11/6 Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>:
>> RETURN isn't one of them.
> It should be enhanced - my initial proposal of return query expected
> so return query is last statement, that isn't now. So we could add
> this check there.
Well, changing the semantics of an already-released statement carries a
risk of breaking existing apps that aren't expecting it to change FOUND.
So I'd want to see a pretty strong case why this is important --- not
just that it didn't meet someone's didn't-read-the-manual expectation.
regards, tom lane
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pavel Stehule | 2008-11-06 21:18:35 | Re: BUG #4516: FOUND variable does not work after RETURN QUERY |
| Previous Message | Pavel Stehule | 2008-11-06 17:48:02 | Re: BUG #4516: FOUND variable does not work after RETURN QUERY |
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Andrew Dunstan | 2008-11-06 18:25:46 | Re: plperl needs upgrade for Fedora 10 |
| Previous Message | Tom Lane | 2008-11-06 18:13:00 | Re: plperl needs upgrade for Fedora 10 |