| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: 3 value logic. Why is SQL so special?
Paul wrote:
> "JOG" <jog_at_cs.nott.ac.uk> wrote:
>
>>>>That's nice. I simply don't allow null in any database I design. >>> >>>Why not? >> >>you're kidding right?
>>>Scheduled_Departure_Time = 'DD:MM:YYYY 10:15' >>>Actual_Departure_Time = <null> untill we know different, then we put >>>in a value.
>>So an aircraft might not take off and yet it has a departure time >>attribute? That makes absolutely no sense at all.
Not if it doesn't yet exist.
> That "something" is normally some arbitrary value - i.e. 01/01/1970 or
> whatever - the point is any application programmer has to take that
> system defined arbitrary value into account when writing code against
> the system.
Since your assumption that it has to be something is false, everything you predicate on the assumption is unsound.
> *_WHEN_* the value used is <null>, then the programmer doesn't need
> any special knowledge of the system - i.e. "By the way, the date for
> planes which haven't taken off yet is xxx/yyy/zzzz" - just a simple,
> "Oh, that's null until the VR is filed".
>
> What could be simpler or more logical?
Logic. Received on Tue Sep 12 2006 - 14:26:44 CDT
![]() |
![]() |