Michelle de Beer wrote:
3) I read some of the things on unicode.org, but thisIf you do primarily english but want other language support, UTF-8 is _exactly_ the same as ASCII for the first 127 characters. If you store UTF-8 in binary fields you're fine -- and you can compare and sort it properly, since its in proper language search order for the most part already (accents and combination characters excluded). Full Unicode support in MySQL will best be described by the team, but will probably just mean that it knows how to combine characters for comparisons and sorting.
is only the pros. Is there any cons for using unicode?
When should I use it?
Hopefully, they support UTF-8 and not just UCS-16 (like Microsoft does). UCS-16 is more efficient for storage but its a pain to rewrite code to use it (I convert to UTF-8 immediately for internal processing and any I/O I do in Unicode. UCS-16 is useful for storing the data on disk in only specific circumstances; like a database).
--
Michael T. Babcock
C.T.O., FibreSpeed Ltd.
http://www.fibrespeed.net/~mbabcock
---------------------------------------------------------------------
Before posting, please check:
http://www.mysql.com/manual.php (the manual)
http://lists.mysql.com/ (the list archive)
To request this thread, e-mail <[EMAIL PROTECTED]>
To unsubscribe, e-mail <[EMAIL PROTECTED]>
Trouble unsubscribing? Try: http://lists.mysql.com/php/unsubscribe.php
