MySQL Bugs: #47334: Wrong mapping for latin1 encoding

Bug #47334	Wrong mapping for latin1 encoding
Submitted:	15 Sep 2009 17:25	Modified:	18 Jan 2010 14:50
Reporter:	Todd Farmer (OCA)	Email Updates:
Status:	Closed	Impact on me:	None
Category:	Connector / J Documentation	Severity:	S3 (Non-critical)
Version:	5.0	OS:	Any
Assigned to:	Tony Bedford	CPU Architecture:	Any

View
Add Comment
Files
Developer
Edit Submission
View Progress Log
Contributions

Description:
The following page states that MySQL's "latin1" encoding is equivalent to Java's "ISO8859_1" encoding.  This is no longer the case, with servers 4.1+, per Mark Matthews.  For MySQL Server 4.1+, "latin1" corresponds to "Cp1252".  The driver determines the appropriate encoding based on the server version to which it is connected.

How to repeat:
See docs.

Suggested fix:
Please update documentation to note the change in corresponding encodings.

Fixed in documentation XML sources.