[prev in list] [next in list] [prev in thread] [next in thread] 

List:       rt-users
Subject:    Re: [rt-users] Case sensitive searching?
From:       Ruslan Zakirov <ruz () bestpractical ! com>
Date:       2011-07-29 20:25:33
Message-ID: CAMOxC8uTiK9AqweFOL=88CcVs+iKYcJLdMBcySJerOg2Jcn23w () mail ! gmail ! com
[Download RAW message or body]

On Fri, Jul 29, 2011 at 11:23 PM, Kevin Falcone
<falcone@bestpractical.com> wrote:
> On Fri, Jul 29, 2011 at 09:30:59AM -0700, Yan Seiner wrote:
>> I just found some strange behavior in the Ticket Search.
>>
>> When I try to search on content, it appears to be case sensitive.
>>
>> Per the MySQL docs, the LIKE operator is case inseinsitive:
>>
>> http://dev.mysql.com/doc/refman/4.1/en/string-comparison-functions.html
>
> Check the type of the Content field, that will probably explain part
> of it.  Also check your collation.  Be careful changing your
> collation, and please don't change the type of the Content field.

In RT3.8 Content is a BLOB column and it's how it should be. So search
is binary and case sensitive.

> If you're on RT4 you should really be setting up and using the sphinx
> integration if you can, since Content like 'foo' is *really* slow.
>
> -kevin
>
>> Howner, if I search using
>>
>> Content LIKE 'phase'
>>
>> I get a different result than if I search for
>>
>> Content LIKE 'Phase'
>>
>> In the former, I get only tickets with the word "phase" in all lower case;
>> in the latter I get only tickets with the word "Phase" with capitalized
>> leading "P".
>
>
> --------
> 2011 Training: http://bestpractical.com/services/training.html
>



-- 
Best regards, Ruslan.

--------
2011 Training: http://bestpractical.com/services/training.html

[prev in list] [next in list] [prev in thread] [next in thread]