Sure... but as Walter has observed repeatedly, this sort of technique seems to assume that NULL is not used for its intended purpose in database fields.

...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. (though 'RVBoy' from Australia seemed to eschew that approach)