| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: 3 value logic. Why is SQL so special?
Evan Keel wrote:
> "Karen Hill" <karen_hill22_at_yahoo.com> wrote in message > news:1157742315.903040.15430_at_b28g2000cwb.googlegroups.com... >
Actually, I don't know that and neither does anyone else really. The 3-vl semantics in SQL are inconsistent. Sometimes null behaves like unknown and other times it behaves like inapplicable.
The problem
> with null is that it is often used as a default value which is almost always
> surely wrong.
That's hardly the only or even the primary problem. Null--even when handled with the utmost care--breaks fundamental identities.
Null does not mean N/A, or missing.
Except that sometimes it does.
That's why you can't do
> arithmetic with it.
What do you mean? x + null = null <-- that's arithmetic.
Except that sometimes x + null = x due to the inconsistencies in SQL.
Null is a semantic construct that started out correctly > and ended up in most RDMS implementations.
Some of the best minds in database management would disagree that it ever started out correctly.
FWIW, I try to create subtypes
> where there are no nulls.
That's nice. I simply don't allow null in any database I design. Received on Fri Sep 08 2006 - 21:33:08 CDT
![]() |
![]() |