Hello, Kevin. ;-)
...and as others have also responded, you can get around that with generated stored procs that assign a token default value that will never be used, to distinguish between an explicit NULL and an implicit one.Perhaps we can agree that somebody considering this technique would be well advised to include the whole issue of NULL in their consideration, including the various work-arounds? There was no mention of this in the citation.
"... They ne'er cared for us
yet: suffer us to famish, and their store-houses
crammed with grain; make edicts for usury, to
support usurers; repeal daily any wholesome act
established against the rich, and provide more
piercing statutes daily, to chain up and restrain
the poor. If the wars eat us not up, they will; and
there's all the love they bear us."
-- Shakespeare: Coriolanus, Act 1, scene 1
