Issue 9: where handling of empty list
Reported by funnyso...@gmail.com, Jun 9, 2009
currently translates to: where foo is null
should translate to an empty recordset.
if present in AND list, return false.
if present in OR list, remove from list.
consider is_false flag to track.

assumes:
  where foo in (null)
is valid.

Aug 11, 2009
#1 daniel.d...@gmail.com
This issue is fixed on the trunk (v230)
Empty sets are treated properly now, and not as Nulls.
Where queries will now short circuit and return an empty resultset if any parameter
in the where clause references an empty set.
Please Test and reopen if you experience any problems.
Status: Fixed
Cc: sdmoses ore...@drjays.com mich...@lagrasta.com msando...@drjays.com