[rt-users] Problem with character encodings after migration to new rt 3.8.8

[Kevin Falcone]

On Thu, Dec 16, 2010 at 03:37:47PM +0200, Kiriaki Konstantinidou wrote:
> This is the output in the new database
> 
> CREATE TABLE `Attachments` (\n  `id` int(11) NOT NULL auto_increment,\n
> `TransactionId` int(11) NOT NULL,\n  `Parent` int(11) NOT NULL default
> '0',\n  `MessageId` varchar(160) character set ascii default NULL,\n
> `Subject` varchar(255) default NULL,\n  `Filename` varchar(255) default
> NULL,\n  `ContentType` varchar(80) character set ascii default NULL,\n
> `ContentEncoding` varchar(80) character set ascii default NULL,\n
> `Content` longblob,\n  `Headers` longtext,\n  `Creator` int(11) NOT NULL
> default '0',\n  `Created` datetime default NULL,\n  PRIMARY KEY  (`id`),\n
> KEY `Attachments2` (`TransactionId`),\n  KEY `Attachments3`
> (`Parent`,`TransactionId`)\n) ENGINE=InnoDB DEFAULT CHARSET=utf8
> 
> For the old database, I used the backup (an export from phpMyAdmin)
> and did an import in the same server. Here is the output:

If you actually had a utf8 table in rt3.4, that is weird and really
not right.

What was the output of updgrade-mysql-schema.pl on the old database?

> CREATE TABLE `Attachments` (\n  `id` int(11) NOT NULL
> auto_increment,\n  `TransactionId` int(11) NOT NULL,\n  `Parent`
> int(11) NOT NULL default '0',\n  `MessageId` varchar(160) default
> NULL,\n  `Subject` varchar(255) default NULL,\n  `Filename`
> varchar(255) default NULL,\n  `ContentType` varchar(80) default
> NULL,\n  `ContentEncoding` varchar(80) default NULL,\n  `Content`
> longtext,\n  `Headers` longtext,\n  `Creator` int(11) NOT NULL
> default '0',\n  `Created` datetime default NULL,\n  PRIMARY KEY
> (`id`),\n  KEY `Attachments2` (`TransactionId`),\n  KEY
> `Attachments3` (`Parent`,`TransactionId`)\n) ENGINE=InnoDB DEFAULT
> CHARSET=utf8
> 
> Unfortunately with the upgrade, the new database was written over
> the old one (as adviced by the manual) so I don't really have the
> original database.

Nothing stops you from using a different database name, examples are
written using the rt3 database name for convenience.  The manual also
explains that having good backups before running the conversion is
important.

-kevin

> On 1/12/2010 7:17 μμ, Kevin Falcone wrote:
> >On Wed, Dec 01, 2010 at 04:25:00PM +0200, Kiriaki Konstantinidou wrote:
> >>Hi.
> >>
> >>After I migrated my installation from rt 3.4.1 to rt 3.8.8, Greek
> >>characters don't appear correctly. New records in Greek are OK. Only
> >>the old records have this problem.
> >>
> >>I use Mysql 5.0.27 with innoDB backend with collation
> >>utf8_general_ci (default Mysql and for the rt database).
> >>
> >>During the migration I didn't change the mysql version or the
> >>collation. For the upgrade I followed the instructions in README and
> >>UPGRADING.mysql.
> >
> >Please provide 'show create table Attachments'
> >on the old and new databases.
> >
> >-kevin
> >
> >>If I recall well even in rt 3.4.1 I had a problem reading greek
> >>characters from phpMyAdmin GUI while the rt GUI was displaying them
> >>correctly. Now rt displays correctly only the new records.
> >>
> >>I can't find anything in the net. Any help would be very much appreciated.
> >>
> >>Thank you,
> >>Kiriaki Konstantinidou

> begin:vcard
> fn:Kiriaki Konstantinidou
> n:Konstantinidou;Kiriaki
> org:Institute of Engineeering Seismology & Earthquake Engineering;Information Technology Division
> adr:;;Cosmos Offices, 5 Ag. Georgiou Str, Patriarchica, Pylaia;Thessaloniki;;555 35;Greece
> email;internet:kiriaki at itsak.gr
> title:Computer Engineer
> tel;work:+30 2310 476081 (141)
> tel;fax:+30 2310 476085
> note;quoted-printable:Skype ID: konstantinidou=0D=0A=
> 	
> url:http://www.itsak.gr
> version:2.1
> end:vcard
> 

-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 195 bytes
Desc: not available
URL: <http://lists.bestpractical.com/pipermail/rt-users/attachments/20101216/0b768a89/attachment.sig>