I started this topic is a spin-off of
Funny Thing topic
I know almost nothing of databases. But...
When designing database we really have to be careful if we'll allow NULL condition of a field. But, if allowed, it'd be good when importing/erasing data, for instance, to trigger a dialog box, if it's possible, something like this: "Empty value for ____ record is to be imported/erased. Should it be empty or NULL?"
But what's the creepiest thing here is what I read following mgp's excellent link:
"NULL values in a database: A programmer's nightmare"It analyzed what I noticed and felt with my firt post in
Funny Thing topic. It might be the future of our world as we know it in the matter, if it's already not.
And mgp: not only ones who care; and Aim: not database gurus, but we mortals at first should be allowed by Constitution to use IS NOT NULL to check if someone was (is) messing up with our lives violating use of NULL and vice versa. Or, even better, what I feel at the moment, NULL at all, as I see it now, should be explicitly forbidden by Constitution.
Imagine if your database birth record field is allowed to be NULL? Can you? 
Using only one, IS NULL or IS NOT NULL, could proclaim you dead. And the truth today more than ever before, and less than tomorrow, is stored in and generated by different databases.
Any thoughts?
