> -----Original Message----- > From: Isaac Raway [mailto:[EMAIL PROTECTED] > Sent: Monday, November 27, 2006 7:05 AM > To: sqlite-users@sqlite.org > Subject: Re: [sqlite] SELECT on empty fields ?? > > I'd like to strongly second this. Avoid NULL columns, even at apparent > cost. > Having a valid default value is always better. If a design appears to > require NULL values, then the design is likely critically flawed. For > something this simple, a default '' string would be much better.
There's a difference between allowing NULL values and requiring NULL values. NULL has its place in the world of data. There's a difference between "Has no last name" and "Last name is unknown". A '' last name should mean "no last name" and a NULL last name should mean "last name is not known". If your design pattern allows one to fill in partial bits of information like a first name without a last name or vice versa, then NULL is a useful value. Robert ----------------------------------------------------------------------------- To unsubscribe, send email to [EMAIL PROTECTED] -----------------------------------------------------------------------------
