Hi, I'm not too clear what you mean. In creating the test system, I did backup & restore the db. But I built a 3.6.6 system and then tested the upgrade from that database. So I stopped Apache and Postfix, removed the old /opt/rt3 folder, make install to get the new 3.8 files, and then followed the upgrade instructions including the rt-setup-database and upgrade-mysql-schema.pl scripts.
At this point, I'm simply trying to get a handful of binary attachments working with a simple script to spit out the image entirely independent of RT. So I'm doing this: mysqldump --default-character-set=binary --compact -c -t -q -Q -w "TransactionId < 2500 AND ContentType=\"image/bmp\"" -u root rt3 Attachments > /data/attachments-dump4.sql mysql --default-character-set=binary -u root rttest < attachments-dump4.sql As you can sortof see, I'm trying to dump a couple attachments from the 3.6.6 rt3 database which contain image/bmp data and then restoring to the test database. I have a couple PHP scripts which simply spit out the ContentType as the Content-type header first and then echo the Content second. And it looks to me like the data coming out of the rttest database still is broken. However, I know that if I push new tickets in to the upgraded RT 3.8.3, those images do come out good the same as the old data does under 3.6.6. I must still be confused or missing something though, what do I do now? Thanks, - Dominic Ruslan Zakirov wrote: > I believe you used backup&restore of original production DB, didn't > you? In this case you probably mangled data on load. Use > --default-character-set=binary on mysqldump and later on mysql load. > This only required for not upgraded DBs, after proper upgrade you > don't need this option. > > On Wed, Jun 3, 2009 at 12:55 AM, Dominic Lepiane > <[email protected]> wrote: > >> Dear RT users, >> >> I am trying to get our RT installation moved from RT 3.6.6 to 3.8.3. >> I've tried following the upgrade steps in the UPGRADING.mysql and the >> README files as diligently as I can. The DBMS is MySQL 5.0.45. I >> updated all the perl modules... When I try the new version, everything >> coming in works okay, but all the old binary attachments are broken, in >> truth, anything other than regular ascii is mangled (e.g. diacritical >> marks like é, ô, ç etc). If I try to open an image, it says "The image >> http://rt/Ticket/Attachment/672/883/spots1.bmp"cannot be displayed, >> because it contains errors.". >> >> Clearly I've either missed something or something has to be done to >> convert this data. If I convert the Content column back to longtext >> from longblob, then the binary data works again. >> >> Please advise what can I do to get the data into the new table schema. >> >> Thanks, >> - Dominic >> >> _______________________________________________ >> http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users >> >> Community help: http://wiki.bestpractical.com >> Commercial support: [email protected] >> >> >> Discover RT's hidden secrets with RT Essentials from O'Reilly Media. >> Buy a copy at http://rtbook.bestpractical.com >> >> > > > >
_______________________________________________ http://lists.bestpractical.com/cgi-bin/mailman/listinfo/rt-users Community help: http://wiki.bestpractical.com Commercial support: [email protected] Discover RT's hidden secrets with RT Essentials from O'Reilly Media. Buy a copy at http://rtbook.bestpractical.com
![http://rt/Ticket/Attachment/672/883/spots1.bmp"cannot](http://rt/Ticket/Attachment/672/883/spots1.bmp"cannot){kind=link}