Select bug or bad indices -- OR ignore collation of field?

[Ruslan Zasukhin]

On 11/18/13, 7:45 PM, "Chris Jones" <cjones at daz3d.com> wrote:

> Not sure if this is related or different, but if I do a select with more than
> one compare:
> 
> SELECT RecID,fldKeyword FROM tblKeyword WHERE fldKeyword = 'Col 02
> Strands.duf' OR fldKeyword = 'Default' OR fldKeyword = 'Materials' OR
> fldKeyword = 'Plant'
> 
> The query seems to ignore the columns collation (in this case making it case
> sensitive).  If I do the same search:
> 
> SELECT RecID,fldKeyword FROM tblKeyword WHERE fldKeyword = 'Default';
> 
> without the OR it returns the correct result.  I get the same weirdness using
> the IN operator instead of OR,

I think you can report this into mantis and provide smallest DB that
reproduce this to Ivan.


-- 
Best regards,

Ruslan Zasukhin
VP Engineering and New Technology
Paradigma Software, Inc

Valentina - Joining Worlds of Information
http://www.paradigmasoft.com

[I feel the need: the need for speed]