Re: Does Codd's view of a relational database differ from that ofDate & Darwin? [M.Gittens]

Jon Heggland schrieb:
> In article <42a6eb89$1_at_news.fhg.de>, savinov@host.com says...
>

>>So I find NULL and empty set formally equivalent.

I would prefer not to distinguish NULL and empty set because I do not find enough reasons for that. And I would prefer NULL to be untyped. It is a variable that may have a type while NULL is a value that can be assigned to any variable of any type including relvars.

There might be the following situations where we would like to distinguish between

• a single-valued variable having no value assigned (NULL), for example, Price=NULL, and
• a set-valued variable having no set assigned (empty set), for example, Children={}, and
• a query returning empty result set, for example, SELECT * FROM Orders WHERE date='01.01.2001'
• a query or other operation returning an error

 From practical point of view it is clear: we always have things to be more informative and therefore we overload the existing values (including NULL) with additional inappropriate meaning, for example, NULL as an error, or try to inroduce new special values like empty set, empty salary, salary is not yet computed etc.

But it would be very interesting to know what fundamental reasons might exist for separating NULL as a variable value and empty set as a collection without elements. For example, do we really need to have different meaning for:
1. some_relvar = NULL, and
2. some_relvar = {}

How do you think? What is the fundamental difference between these two lines of code and do we loose a lot if we retain only the first one (with the meaning of the second)?

-- 
alex
http://conceptoriented.com