| Oracle FAQ | Your Portal to the Oracle Knowledge Grid | |
Home -> Community -> Usenet -> comp.databases.theory -> Re: So what's null then if it's not nothing?
Alexandr Savinov wrote:
> Jon Heggland schrieb:
>> In article <438456fe$1_at_news.fhg.de>, spam_at_conceptoriented.com says... >>>> You mean you would create a table for each *combination* of >>>> attributes? What on earth for? >>> In order to avoid nulls (there is an opinion that they need to be >>> removed from schema). >> I get that part. But why one for each combination? Why not just one >> per attribute?
Nice summary.
My understanding is that Fabian Pascal espouses approach 1, Hugh Darwen espouses approach 2 (more or less), but I've not come across any theorist who espouses approach 3 (though that probably means I've simply not been reading in the correct places).
References:
1. http://www.dbdebunk.com/page/page/1396241.htm
(The Final NULL in the Coffin - available at a fee). 2. http://www.thethirdmanifesto.com/
(How to Handle Missing Information Without Using Nulls).
-- Jonathan Leffler #include <disclaimer.h> Email: jleffler_at_earthlink.net, jleffler_at_us.ibm.com Guardian of DBD::Informix v2005.02 -- http://dbi.perl.org/Received on Wed Nov 23 2005 - 22:33:56 CST
![]() |
![]() |