Re: Question about SQL and Nulls

depends...

If you must have a field that allows a value of "not known" or "not supplied" then, IMHO, there is no better way. Anything else requires hard coding some isolated value and then you not only have to remember to check for that value every time, (just like nulls) you also have to remember and document the isolated value. And that isolated value is more likely to "slip" through and appear to the user or skew the results of some other operation, than a null value would.

Just select which fields to allow null values carefully and thoughfully. Ask yourself "Can this element be absent in valid data, and do I need to represent the absence of this data element accurately?".


Bob Anderson wrote:

Good Afternoon,
I am working with a new table design and wonder about the wisdom of
using Null capable fields in the design.
Is it worth the trouble making fields Null capable and if so how do you
handle the fields in a Select Into or an Update operation operation. I know I will need Null indicators and such but I wondering if it is
worth it.
Thanks Bob Anderson
IT Guy
Kent Sporting Goods
433 Park Ave. S
New London OH 44851
419-929-7021 x315
email: banderson@xxxxxxxxxxxxxxxxxxx