On Tue, Jun 08, 2010 at 04:57:25PM +0200, V?clav Ovs?k wrote:
> Hi Ken,
>
> On Tue, Jun 08, 2010 at 07:48:15AM -0500, Kenneth Marshall wrote:
> > ILIKE is fine on PostgreSQL as long as the search is anchored on
> > the left and there is an index. Otherwise it will do a sequential
> > scan of the a
Hi Ken,
On Tue, Jun 08, 2010 at 07:48:15AM -0500, Kenneth Marshall wrote:
> ILIKE is fine on PostgreSQL as long as the search is anchored on
> the left and there is an index. Otherwise it will do a sequential
> scan of the attachments table to find matching records. The wiki
> entries for full-tex
On Tue, Jun 08, 2010 at 09:10:23AM +0200, V?clav Ovs?k wrote:
> ... 3rd try to mail ...
>
> On Sun, Jun 06, 2010 at 02:34:58PM -0500, Kenneth Marshall wrote:
> > Hi Zito,
> >
> > You can look in the mailing list archives for several similar "discoveries"
> > on
> > how MySQL works with content s
... 3rd try to mail ...
On Sun, Jun 06, 2010 at 02:34:58PM -0500, Kenneth Marshall wrote:
> Hi Zito,
>
> You can look in the mailing list archives for several similar "discoveries" on
> how MySQL works with content searches and the longblob data type. I would
> definitely recommend using PostgreS
Hi,
I'm preparing migration from RT 3.2.2 + Mysql 3.x to RT 3.8.8
+ Mysql or Pg.
I just discovered a problem with the case insensitive searching in the
column Attachments.Content (longblob) while playing with a new RT
instance.
Ticket SQL query
Content like 'outlook'
on our current (old) RT in
