Bug #79183 Cannot save some Slovenian/Croatian/Serbian letters into database
Submitted: 9 Nov 2015 10:20 Modified: 11 Jan 2016 16:22
Reporter: Marko Frelih Email Updates:
Status: No Feedback Impact on me:
None 
Category:Connector / J Severity:S1 (Critical)
Version:5.1.37 OS:Ubuntu
Assigned to: CPU Architecture:Any
Tags: internationalization

[9 Nov 2015 10:20] Marko Frelih 
Description:
Dear Sirs and Madams!

I have Java application which communicates with some database. Identical database resided on hosted mysql server (5.5.40-cll-lve - MySQL Community Server (GPL) by Atomicorp; Server charset: UTF-8 Unicode (utf8)), local testing mysql server (5.5.46-0ubuntu0.14.04.2 - (Ubuntu), Server charset: UTF-8 Unicode (utf8)) and 2nd local testing server (5.6.27-0ubuntu0.15.04.1 - (Ubuntu), UTF-8 Unicode (utf8)). With Java app I enter some products into database and for instance, in their names I use Slovenian/Croatian/Serbian letters "Č", "Ć", "Đ", "č", "ć" and "đ", and when I save them into database, the Connector transforms them into "?". Why am I suspicious about connector character transforming?
I've debuged Java app and when I enter text into JTextField, the problematic character(s) is/are present, when I click "Save", the problematic character(s) is/are also present int SQL statement, which is ok. Now, the database itself is also ok, because if I insert/change record field name with value "ČĆŽŠĐ čćžšđ", all characters are present after commiting changes.

How can I overcome this problem?

How to repeat:
I do not know how to repeat it since I have closed source app from customer which I am working on.
[1 Dec 2015 13:07] Alexander Soklakov 
Hi Marko,

Please provide details about how do you use c/J to save/restore these letters, especially the connection string. Can't say much about possible fix without that. But you could check first if the connection properties contain characterEncoding=UTF-8.

Thanks,
Alex
[12 Jan 2016 1:00] Bugs System 
No feedback was provided for this bug for over a month, so it is
being suspended automatically. If you are able to provide the
information that was originally requested, please do so and change
the status of the bug back to "Open".