Hi Beau, basically, you can use anything from MySQL 3.x, as you like it. I'm on an Internet Newsboard System for a while and switched that to UTF-8 for all data handling, display and storage. (Even sending out UTF-8 e-mails and Jabber messages...) You just have to give MySQL the UTF-8 encoded string, there's no problem with that.
But there is one exception I have found by now: You may experience problems with sorting of non-ANSI characters. They will be sorted by their byte values, with no respect to multibyte characters (except from MySQL 4.1 on). If that's not a too big problem for you, it should work anyway. (You could check the sorted output and re-sort them manually...) And there's another problem with it: FULLTEXT indices might cause problems with words containing non-ANSI characters, specifically, MySQL won't index them (AFAIK). -- Yves Goergen [EMAIL PROTECTED] Please don't CC me (causes double mails) On Monday, February 23, 2004 11:48 PM CET, Beau Hartshorne wrote: > Hi, > > I am about to start using UTF-8 for my internal data storage and > display > for a CMS that I'm building. Are there any issues that I should be > aware > of related to mysql and storing UTF-8 encoded characters? What > versions > of mysql offer full UTF-8 support, and are there any weird caveats > with > the implementation? > > Thank you, > > Beau -- MySQL General Mailing List For list archives: http://lists.mysql.com/mysql To unsubscribe: http://lists.mysql.com/[EMAIL PROTECTED]
