| From: | "Vadim B(dot) Mikheev" <vadim(at)sable(dot)krasnoyarsk(dot)su> |
|---|---|
| To: | "Meskes, Michael" <meskes(at)topsystem(dot)de> |
| Cc: | Zeugswetter Andreas SARZ <Andreas(dot)Zeugswetter(at)telecom(dot)at>, "'pgsql-hackers(at)hub(dot)org'" <pgsql-hackers(at)hub(dot)org>, ocie(at)paracel(dot)com |
| Subject: | Re: [HACKERS] Re: Subselects open issue Nr. 5 |
| Date: | 1998-02-16 11:56:37 |
| Message-ID: | 34E82975.1A267E8A@sable.krasnoyarsk.su |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
Meskes, Michael wrote:
>
> Yes, and Oracle7 also.
>
> I think with NULL values Andreas is right. The whole statement should be
> NULLed. That to me is the intuitive behaviour.
Not sure.
IMHO, any element, either with defined value or with undefined value (NULL),
can't be contained by empty set.
Hm, btw, just curious, what Informix returns for
select * from taba where (a,b) not in (<a select returning no row>);
having in taba tuples with (a,b) in
(NULL, a_value)
(NULL, NULL)
?
Does it return all tuples except for (NULL,NULL) ?
Vadim
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Pedro J. Lobo | 1998-02-16 12:02:06 | configure doesn't handle --with-compiler correctly |
| Previous Message | Pedro J. Lobo | 1998-02-16 11:53:05 | DEC alpha/6.3beta problems reported on 'ports' |