Subject Re: [ib-support] Strange query results, based on where clause
Author Ann W. Harrison
There are problems with making the index code follow the
precedence order in CVT.

The index isn't used for a comparison, exactly, but for
a lookup. The values to be matched are coded as if they
were an index key and that value is retrieved if it
exists. There's no way to look up something that might
be '0617', or '617' or '00000617' or might be a double
precision number representing the value 617.

I think changing the index behavior is a non-starter.


Ann