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
Ticket SQL query
Content like 'outlook’
on our current (old) RT instance, returns some result set. Column Content has
data-type longtext in the old database schema, so every letter case
combination are found.
On a new testing platform RT 3.8.8 + Mysql only partial set of tickets is
returned with the same query. I must to modify the query to
Content like ‘outlook’ or Content like 'Outlook’
at least to see the most of the tickets.
On the other hand RT 3.8.8 + Pg has Content column data-type text, so
case-insensitive searching works, but there is another issue with non
UTF-8 attachments encoded in quoted-printable, but this is a minor
problem. Pg database behaves better than Mysql in this aspect.
Is there any intention to detach non textual data from the Content
column into e.g. ContentB in future?
Have anyone some knowledge or suggestion about this?