From: | Robert Haas <robertmhaas(at)gmail(dot)com> |
---|---|
To: | Bruce Momjian <bruce(at)momjian(dot)us> |
Cc: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, David Fetter <dfetter(at)vmware(dot)com>, pgsql-bugs(at)postgresql(dot)org |
Subject: | Re: BUG #6067: In PL/pgsql, EXISTS(SELECT ... INTO...) fails |
Date: | 2011-11-30 20:36:11 |
Message-ID: | CA+TgmoZC9vwRD0rJVFE5rG4HtWQCZ9S9WSHb8nHyRBDtsPUQ2Q@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-bugs |
On Tue, Nov 29, 2011 at 9:32 PM, Bruce Momjian <bruce(at)momjian(dot)us> wrote:
> Tom Lane wrote:
>> "David Fetter" <dfetter(at)vmware(dot)com> writes:
>> > IF EXISTS (SELECT 1 INTO STRICT i) THEN
>> > RAISE NOTICE '%', a;
>> > END IF;
>>
>> Umm ... are you just complaining that the error message isn't very
>> helpful, or are you actually expecting that to do something useful?
>> If the latter, what exactly? I'm particularly confused by your use
>> of the STRICT option here, because if we did support that, I would
>> expect the STRICT to throw an error if there were not exactly one
>> matching row, making the EXISTS test 100% pointless.
>>
>> But the short answer is that we don't support INTO in sub-selects,
>> and in general I doubt that we ever will, since in most cases the
>> behavior wouldn't be very well-defined. It might be worth a TODO
>> to provide a better error message than "syntax error", though.
>
> Is it worth documenting, fixing, or adding this to the TODO list?
At most I would say we could try to improve the error message.
--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Jeff Davis | 2011-11-30 21:59:17 | possible bug seen with -DCLOBBER_CACHE_ALWAYS and changing GUCs |
Previous Message | Kasia Tuszynska | 2011-11-30 19:30:26 | Re: transaction error handling |