Re: subselects

From: Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>
To: Bruce Momjian <maillist(at)candle(dot)pha(dot)pa(dot)us>
Cc: PostgreSQL-development <hackers(at)postgreSQL(dot)org>
Subject: Re: subselects
Date: 1999-05-10 19:52:04
Message-ID: 8786.926365924@sss.pgh.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...

regards, tom lane

Responses

Browse pgsql-hackers by date

  From Date Subject
Next Message Bruce Momjian 1999-05-10 20:30:18 Re: subselects
Previous Message Michael J Davis 1999-05-10 19:32:46 RE: [HACKERS] NULL = col