From: "Lex de Haan" <lex.de.haan@xxxxxxxxxxxxxx> > my only point (somewhere at the beginning of this thread :-) was that > certain seemingly obvious logical equivalences don't hold in three-valued > logic. People who work with DBs that implement NULLs distinguish the difference earlier on. Or they produce wrong results. Not sure what your theoritical argument is. In practice, NULLs work. Do you have a theory that says they should not? Something that does not work doesn't need a theory to say so - it will crash and burn by itself. > and I guess it is hard to make your workaround generic -- what if the > <condition> is constructed dynamically, at run time, and can e.g. be a > compound predicate with some ANDs and ORs? > then your "outer IF" becomes almost impossible to generate... / I have written some complex PL/SQL routines (like parsing free-format name/address lines). Had to use IF/AND/ORs and lots of brackets but never came across an "impossible" case. Within an Oracle context, I'm really quite puzzled to see someone suggesting something like 'Mort subite' = NULL. You shoudl never, never equal" NULL. It is a meaningless comparison -- noone writing Oracle code should be caught dead writing 'something' = NULL. ---------------------------------------------------------------- Please see the official ORACLE-L FAQ: http://www.orafaq.com ---------------------------------------------------------------- To unsubscribe send email to: oracle-l-request@xxxxxxxxxxxxx put 'unsubscribe' in the subject line. -- Archives are at //www.freelists.org/archives/oracle-l/ FAQ is at //www.freelists.org/help/fom-serve/cache/1.html -----------------------------------------------------------------