|
I disagree with the use of "dummy" values to
represent missing data. It reminds me of the olden days when we coded in
12/31/99 and such. Shades of COBOL HIGH-VALUES! You're introducing a
lot of dependencies and non-intuitive information. For instance, how do
you ensure that these dummy values are used consistently across an application
or database?
Yes, you will simply your SQL and perhaps improve
performance (there are workarounds), but you will corresponding need to add
special logic to reports and screens to suppress displaying these dummy
values. Or you'll have to explain to the HR manager why all of the
employees appear to be terminated!
A null value means there is missing
data. It is not clear that 01/01/4000 represents missing data or
incorrectly entered data.
Leave me my nulls!
Marc Perkowitz
|
Title: RE: No Nulls? (was: Warehouse design: snowflake vs star schem
- RE: No Nulls? (was: Warehouse design: ... Jesse, Rich
- Re:No Nulls? (was: Warehouse desi... dgoulet
- RE: No Nulls? (was: Warehouse des... DENNIS WILLIAMS
- RE: No Nulls? (was: Warehouse des... Adams, Matthew (GECP, MABG, 088130)
- Re: No Nulls? (was: Warehouse des... Igor Neyman
- RE: No Nulls? (was: Warehouse des... Fink, Dan
- Re: No Nulls? (was: Warehouse des... Marc Perkowitz
- Re: No Nulls? (was: Warehouse des... Igor Neyman
- RE: No Nulls? (was: Warehouse des... Grabowy, Chris
- Re: No Nulls? (was: Warehouse des... Igor Neyman
- Re: No Nulls? (was: Warehouse des... Ora NT DBA
- Re: No Nulls? (was: Warehouse des... Marc Perkowitz
- RE: No Nulls? (was: Warehouse des... Jesse, Rich
- RE: No Nulls? (was: Warehouse des... Grabowy, Chris
- RE: No Nulls? (was: Warehouse des... Robson, Peter
- RE: No Nulls? (was: Warehouse des... Toepke, Kevin M
