On Nov 10, 12:39 pm, George Sakkis <[EMAIL PROTECTED]> wrote: George Sakkis wrote: > On Nov 10, 2:21 pm, [EMAIL PROTECTED] wrote: > >> So you could say that 3.0 is forcing us to acknowledge database >> >> > reality ;-) >> >> (Again) huh? >> Reality in databases is that NULL *is* comparable. >> "NULL==something" returns False, it doesn't raise an error. > > Given that in SQL "NULL `op` something" is False for all comparison > operators (even NULL=NULL), raising an error seems a much lesser evil
s/False/NULL/. Why is that evil? It is logically consistent, and more importantly, useful. In Python, the logically consistent argument is a little weaker (not having tri-state logic) but the useful argument certainly still seems true. -- http://mail.python.org/mailman/listinfo/python-list
