Bug #51526 Unsupported character encoding 'CP932'
Submitted: 25 Feb 2010 19:03 Modified: 26 Mar 2013 13:07
Reporter: Andrii Nikitin Email Updates:
Status: Won't fix Impact on me:
None 
Category:Connector / J Severity:S4 (Feature request)
Version:5.1.12 OS:Any
Assigned to: Mark Matthews CPU Architecture:Any

[25 Feb 2010 19:03] Andrii Nikitin
Description:
When 'CP932' is specified as part of connection string, exception generated:

java.sql.SQLException: Unsupported character encoding 'CP932'.
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1072)
...

This encoding working properly in 3.1.12 .

Probably this bug is duplicate of bug #6549 , just for 5.1.*

How to repeat:
create connection like following:

conn = 
DriverManager.getConnection ("jdbc:mysql://localhost/test?user=root&password=&characterEncoding=CP932");

Suggested fix:
In bug #6549 was introduced some mapping for 3.1.*, probably it should work for 5.1.*
[26 Feb 2010 15:07] Tonci Grgin
Workaround set to W5 as all one has to do is set MP932 instead of CP932.
[26 Feb 2010 15:44] Tonci Grgin
MS932 that is.
[2 Mar 2010 8:54] Tonci Grgin
Related bugs:
  o Bug#6549
  o Bug#7607
[26 Mar 2013 13:07] Alexander Soklakov
Hi Andrii,

According to http://docs.oracle.com/javase/1.5.0/docs/guide/intl/encoding.doc.html there are only "windows-31j" and "MS932" charset name known to Java and common approach is that characterEncoding should use Java naming.

So I close this report as Won't fix. But feel free to reopen it if you find reasonable to implement c/j internal cp932->ms932 mapping.