>>>>And if you don't define as what it is you will have problems.
>>
>>I'll only have problems if I allow it to exist.
>>There are no NULLS in any column in any row in any table I've ever designed and created, period.
>>If I run into them in other people's data, I mutter the unutterable and deal with them.
>
>Whatever the merits or demerits my suggestion would be that hired gun programmers learn to deal with databases like the ones you describe. In my experience they are ubiquitous and one needs to be able to program against them and submit scripts that honor the prohibition against nulls.
>
>I know that in the hundreds of tables I deal with every day in dozens of databases in a fairly large enterprise there are no null columns in production, period.

I do not understand the issue with nulls (and yes, I've bitten by them once, I even posted a message here not long time ago for an issue with a SELECT IN where I forgot about the null and did not get the expected results, but I blame myself), I think of them as very elegant, but I am digressing, the fact that there are no nulls stored in your tables does not mean that you are free of nulls, as Fabio pointed out long time ago (one of the first messages in the thread that went largely ignored) for at least you have nulls when you do ~INNER JOINS (LEFT, RIGHT, FULL), and this might be part of a view, so I wonder what you guys do with them? I think it is more cumbersome to find a work-around for this than just plainly embrace the use of NULLS <g>