| From: | Tatsuo Ishii <t-ishii(at)sra(dot)co(dot)jp> |
|---|---|
| To: | lockhart(at)alumni(dot)caltech(dot)edu |
| Cc: | mha(at)sollentuna(dot)net, tgl(at)sss(dot)pgh(dot)pa(dot)us, t-ishii(at)sra(dot)co(dot)jp, pgsql-hackers(at)postgresql(dot)org |
| Subject: | Re: comparing rows |
| Date: | 2000-08-04 01:07:38 |
| Message-ID: | 20000804100738M.t-ishii@sra.co.jp |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> btw, it appears that SQL99 (haven't checked SQL92) specifies that
>
> test=# select (1,2,3) = (1,2,null);
> ?column?
> ----------
>
> (1 row)
>
> should return FALSE, not NULL. I haven't looked to see if this is
> consistant with other comparisons involving NULL.
This is interesting. If "(1,2,3) = (1,2,null)" is legal from the point
of view of the standard, isn't "(1,2,null) = (1,2,null)" legal
comparison too? no?
BTW, I would like to object the "null = null" support in
PostgreSQL. It is against the standard. That's enough reason to reject
the syntax.
--
Tatsuo Ishii
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2000-08-04 01:10:53 | Re: [HACKERS] pg_dump/restore to convert BLOBs to LZTEXT (optional!) |
| Previous Message | Larry Rosenman | 2000-08-04 00:57:11 | MAC.C (still?) |