[rt-users] Binary files broken since upgrade to RT 3.8

[Dominic Lepiane]

This worked fine for us in the end.  Did a select on the Content from
the restored old database, and then just updated the Content in the
corresponding row in the new database.  We also have similar problems
with other fields, like Headers, where there is any unicode / extended
acsii characters (diacritics or Asian characters) and these fields are
fixed in the same way.

Thank all for your help,
 - Dominic

Dominic Lepiane wrote:
> Thanks, it looks like this might work.  We basically have a script
> which selects the data out of the 3.6 db and then update the
> corresponding row in the 3.8 db and so far I'm getting better results.
>
> Thanks,
> - Dominic
>
>
> Aaron Guise wrote:
>> Hi,
>>
>> I too had a similar problem. I inherited our RT System from an
>> earlier administrator whom didn't complete some step correctly
>> earlier in the life of the system.  We were going from 3.6.5 to 3.8.0
>> and all worked fine.  Since then to enable some plugins I attempted
>> to update to 3.8.2. 
>>
>> I did use --default-character-set=binary on mysqldump and completed
>> all of the upgrade steps as per UPGRADING.mysql but upon browsing the
>> newly updated RT System to my surprise all the binary attachments had
>> been corrupted as you are mentioning.
>>
>> To get around this I created a couple of perl scripts.
>> 1.  Pulls all attachments out of the functioning database
>> (Pre-Upgrade) and dumps them to the filesystem
>> 2.  Inserts all attachments back into the newly updated schema.
>>
>> This approach worked for me, I was then able to use 3.8.2 without any
>> trouble at all.
>>
>>     *Regards,*
>>
>>     *Aaron Guise
>>     *
>>
>>