Subject Re: [Firebird-Architect] IN LIST
Author Doug Chamberlin
At 11:42 AM 12/3/2006, Adriano dos Santos Fernandes wrote:
>The parser knows nothing, it only pass the strings to others layers.
>
>Then, each item are separated and evaluated as:
> X IN ('01-01-2006', '05-15-2006') OR (X BETWEEN '02-27-2006' AND
>'03-01-2006')
>
>The engine already knows how to evaluate this. :-)

Ok, I guess I didn't get it because I have always thought of the
IN(x,y,z,...) construct to represent an *unordered* set of values of any
type. Your syntax, and LIST construct (passable as a single parameter),
would only be usable when the list of values is to be interpreted as an
ordered list that can be expressed with an equivalent combination of
IN(x,y,z..) and BETWEEN(x and y).