NYCPHP Meetup

[Rahmin Pavlovic]

On 5/10/06 10:11 AM, "Daniel Convissor" <danielc at analysisandsolutions.com>
wrote:

> On Tue, May 09, 2006 at 12:46:12PM -0400, Rahmin Pavlovic wrote:
>> 
>> All the high-bit chars -- which were stored fine in MySQL 5 -- are being
>> mangled in MySQL 4.
> 
> I'm guessing the default character set for all the tables on your system
> in 5 was UTF-8 while in 4 it's latin1.
> 

I already tried setting the charset / collation to utf-8 -- both on tables /
fields -- but resaving data produces the same mangled results.

Unfortunately -- and this is really just corporate politics (meh) -- another
firm setup Apache/MySQL, and they haven't exactly been forthcoming with
this, so I can't as of yet compare old-new charset's.

Also unfortunately, all I can tell on my end is that when we moved data from
Apache 1.3.33 (Unix) / MySQL 5.02-alpha to Apache 2.0.52 (CentOS) / MySQL
4.1.12, high-bit data became mangled.  I'd be more than happy to suggest
changes on the Apache-level, but my job is the management of content by way
of PHP, and I don't know what I'd suggest that would help..