| From: | Richard Broersma Jr <rabroersma(at)yahoo(dot)com> |
|---|---|
| To: | Mark Morgan Lloyd <markMLl(dot)pgsql-odbc(at)telemetry(dot)co(dot)uk>, pgsql-odbc(at)postgresql(dot)org |
| Subject: | Re: '= NULL' is not the same as 'IS NULL' |
| Date: | 2006-09-06 20:56:32 |
| Message-ID: | 20060906205632.30759.qmail@web31803.mail.mud.yahoo.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-odbc |
> I'm afraid so, in Joe Celko's "SQL for Smarties" book, after which I simply
> accepted that that was the way SQL worked.
Yes for what I recall from my reading that he mentions that there are specific reasons to allow
nulls. During Table design, if one cannot see how these specific rules apply to the data to of a
column, then the column should be constrained as NOT NULL, with a DEFAULT value as '{left blank}'
or 0 or some other value that would produce this effect.
But I am sure that this is just one particular philosophy of table design.
Regards,
Richard Broersma Jr.
| From | Date | Subject | |
|---|---|---|---|
| Next Message | greg.campbell | 2006-09-06 22:07:44 | Re: '= NULL' is not the same as 'IS NULL' |
| Previous Message | Mark Morgan Lloyd | 2006-09-06 20:40:50 | Re: '= NULL' is not the same as 'IS NULL' |