Re: connection collation
Posted by: Rick James
Date: August 05, 2010 08:12PM

(I cannot address the BMP issues. Java uses, I think, ucs2; this has a limit of 64K encodings unless it extends to 2-word encodings. Similarly, utf8 allows 1-byte, 2-byte, 3-byte, etc encodings.)

The link to 5.5 handling 4-byte utf8 characters; 5.1 stops at 3 bytes. A small number of Chinese characters are 4 bytes; these cannot be represented until you move to 5.5 and that particular charset.

As for performance -- I suspect the diff between 5.1 and 5.5 is not big enough to matter. Usually performance is dictated by (1) disk hits and (2) number of rows "examined", before getting into the computational costs.

Options: ReplyQuote

Written By
August 03, 2010 03:10PM
August 04, 2010 10:16PM
August 05, 2010 08:44AM
Re: connection collation
August 05, 2010 08:12PM
August 06, 2010 10:06AM
August 07, 2010 10:04AM

Sorry, you can't reply to this topic. It has been closed.

Content reproduced on this site is the property of the respective copyright holders. It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.