[nycphp-talk] MySQL 4 vs. 5 and character encoding (?)
Rahmin Pavlovic
rahmin at insite-out.com
Fri May 12 09:44:19 EDT 2006
On 5/12/06 8:52 AM, "Daniel Convissor" <danielc at analysisandsolutions.com>
wrote:
> Dude:
>
> On Thu, May 11, 2006 at 12:51:42PM -0400, Rahmin Pavlovic wrote:
>>
>> So -- just so I get this straight -- say I ALTER TABLE to set the default
>> character set to be UTF-8, then insert a brand new record filled with
>> high-bit chars, it will still not be able to read certain characters and
>> introduce '?' and whatnot in their stead?
>
> No. OLD DATA will not magically fixed, which is what you were talking
> about when you started this thread. NEW DATA will be fine.
>
That's just the thing: new data gets mangled in the exact same way, which
is why I thought it wasn't a charset-collation issue.
More information about the talk
mailing list