The lesson is very clear from the evidence. With SQL NULL is ambiguous and subject to intepretation so good design requires that you completely avoid it. Then you sidestep intractable implementation interptrations.
A project management technique dating back further than I can remember was to define elments of languages and tools which were problem ridden and forbid their usage. Quality problems were slashed. D. Richard Hipp wrote: > On Jun 25, 2008, at 12:48 PM, Wilson, Ron P wrote: > > >>It seems to me that using NULL ... could >>create a lot of confusion in queries. > > > Yes, yes. SQL-NULL excels at creating confusion! > > D. Richard Hipp > [EMAIL PROTECTED] > > > > _______________________________________________ > sqlite-users mailing list > sqlite-users@sqlite.org > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users _______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
