From: | Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> |
---|---|
To: | Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us> |
Cc: | PostgreSQL-development <hackers(at)postgreSQL(dot)org> |
Subject: | Re: subselects |
Date: | 1999-05-10 20:30:18 |
Message-ID: | 199905102030.QAA11035@candle.pha.pa.us |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgsql-hackers |
> Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us> writes:
> >> If the / were the toplevel operator in the WHERE then the message would
> >> make sense, because the WHERE clause as a whole must yield boolean.
> >> But that doesn't mean that the operator immediately above the subselect
> >> must yield boolean.
> >>
> >> Besides, I already fixed this ;-)
> ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
>
> > Added to TODO list.
>
> Added what to the TODO list? The particular behavior complained of
> is history...
Oh, I thought you had already fixed this long ago, but it was now being
reported as broken. Removed from list.
--
Bruce Momjian | http://www.op.net/~candle
maillist(at)candle(dot)pha(dot)pa(dot)us | (610) 853-3000
+ If your life is a hard drive, | 830 Blythe Avenue
+ Christ can be your backup. | Drexel Hill, Pennsylvania 19026
From | Date | Subject | |
---|---|---|---|
Next Message | Adam H. Pendleton | 1999-05-10 20:32:09 | plpgsql error |
Previous Message | Tom Lane | 1999-05-10 19:52:04 | Re: subselects |