I second, full UTF-8 is awesome down the line for internationalization. First see if MySQL even supports UTF-8 on your system, execute: "SHOW CHARACTER SET;" and utf8 should appear in the list. Then "ALTER TABLE tbl_name CONVERT TO CHARACTER SET charset_name COLLATION collation_name;". Since I have not done this myself I can't verify that it will rebuild indexes on the table, I don't think it should but might want to look into that as rebuilding indexes on a large table could be time consuming.
________________________________ From: Chris Snyder <chsny...@gmail.com> To: NYPHP Talk <talk@lists.nyphp.org> Sent: Thu, May 6, 2010 11:56:09 AM Subject: Re: [nyphp-talk] utf-8, iso-8859-1... On Thu, May 6, 2010 at 11:46 AM, David Mintz <da...@davidmintz.org> wrote: > Would this regex work if the data were utf-8? Should I consider converting > everything and working in utf-8, and if so, how painful is it to convert a > MySQL database? My initial research suggests that it isn't painless. > Full-stack utf-8 is worth the pain of conversion. It makes a whole class of issues disappear and gives you the ability to accept anything the world is going to throw at you. Many php functions are not unicode aware (and php6 will be release right after perl6) but in practice those issues are much easier to deal with than trying to limit your data to iso-8859-1. _______________________________________________ New York PHP Users Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/Show-Participation
_______________________________________________ New York PHP Users Group Community Talk Mailing List http://lists.nyphp.org/mailman/listinfo/talk http://www.nyphp.org/Show-Participation
