| From: | Christopher Kings-Lynne <chriskl(at)familyhealth(dot)com(dot)au> |
|---|---|
| To: | Dann Corbit <DCorbit(at)connx(dot)com> |
| Cc: | Alvaro Herrera <alvherre(at)dcc(dot)uchile(dot)cl>, Tom Lane <tgl(at)sss(dot)pgh(dot)pa(dot)us>, Jason Earl <jason(dot)earl(at)simplot(dot)com>, PostgreSQL-development <pgsql-hackers(at)postgresql(dot)org> |
| Subject: | Re: Two weeks to feature freeze |
| Date: | 2003-06-21 05:24:30 |
| Message-ID: | 20030621132228.M14306-100000@houston.familyhealth.com.au |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
> Sounds like testing for the existence of a bug.
> X = NULL
> X <= NULL
> X >= NULL
> Etc. must always test false, regardless of the contents of X. Test for
> equality with NULL is a conformance error if NULL == NULL returns true.
They should all return NULL, not false...
> > dates like '00-00-0000');
Yes, that's MySQL's idea of a NULL date. In fact, it's exactly what you
get when you insert a NULL date into a NOT NULL column - hooray the test
proves that MySQL accepts NULL values in NOT NULL columns...
Chris
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Tom Lane | 2003-06-21 05:33:36 | Re: Two weeks to feature freeze |
| Previous Message | Christopher Kings-Lynne | 2003-06-21 05:22:00 | Re: Two weeks to feature freeze |