Home Forums Article Discussions Article Discussions by Author Discuss content posted by Edward Pollack Database Design Follies: NULL vs. NOT NULL RE: Database Design Follies: NULL vs. NOT NULL
Stacey Decker
Mr or Mrs. 500
Points: 548
More actions
October 30, 2014 at 6:55 am
#1755755
I agree, why allow two values to mean the same thing? I handle this by allowing optional fields such as AddressLine2 to be NULL and then implement a constraint to prevent an empty string (AddressLine2 <> ''). Thoughts on this approach?