Re: Are there performance advantages in storing bulky field in separate table?

Robert Treat wrote on 08.04.2009 23:06:

> http://www.databasedesign-resource.com/null-values-in-a-database.html

That is a very - hmm - strange article.

One of the proofs that nulls are bad is that "SELECT * FROM theTable" (theTable 
being empty) returns nothing, whereas SELECT COUNT(*) FROM theTable returns a 
single row with 0 (zero):

"This last example is even worse: The SELECT * returns 'No rows selected', but 
the SELECT COUNT(*) returns ONE row with the value 0!"

I stopped reading the article at that point...