Insert query with latin1_swedish_ci charset - java

I made a program that is generating me a INSERT queries for a MySql database. The database has 2 fields that are encoded with latin1_swedish_ci charset. If I run the query from PhpMyAdmin when I preview the content with my php script some special char (like "ó", "é"...) is not showed correctly.
I think the problem is that Java is encoding String as utf8 charset so when i copy paste the query in the phpmyadmin and i run it, the inserted record is generated with the wrong charset. How can I generate the correct query (with the correct charset) in Java?
Thanks In advance for your help

Related

how to transform byte[] value of blob field in mysql to insert into statement

I want to select data from a mysql table, and then generate a sql script file for importing to another db.
The value type of blob in mysql is byte array in java. I have try to use new String(byte[], Charset) to transform it to String, using all charsets that java support. It can import successfully, but the imported value is incorrect. All the generated strings are not equal to what SQLyog generates.
how can i do?

Unicode messages in oracle raise_application_error

I am working on enabling globalization support in my DB.
I have done migrating character set to UTF (AL16UTF16).
After migration, I can pass Unicode characters from Java to Oracle and store in table's NVARCHAR2 column. Also I can retrieve from DB and pass to Java.
But, If I do a raise_application_error with the Unicode data. It sends the error message to java like below
; nested exception is java.sql.SQLException: ORA-20001: ¿¿¿ ¿¿¿¿¿¿¿¿¿
Can anyone tell me what's wrong? and how can I get the Unicode error messages in java?
Thanks in advance.
The problem is I have done character set migration using the below steps, but it doesn't work for me.
1.Backup the database.
2.Run CSSCAN command.
3.Restart the DB with RESTRICT mode.
4.Run CSALTER script.
5.Restart the DB.
After that I have tried using the below steps.
1.Take backup of the DB using expdp command.
2.Create a new database with required character set (Unicode AL32UTF8).
3.Import the backup dump file into the newly created DB.
That's all. It works!
Now I don't need to use NVARCHAR2 data type to store unicode data (VARCHAR2 itself stores Unicode). raise_application_error also works fine (sends error messages with Unicode data to Java).
Thanks.

UTF-8 Queries with JDBC

i want to ask the MYSQL an UTF-8 Query but it does not work fine . when i try the following query , the result comes up truly :
String query = "select * from Terms where Term = 'lol'";
but with the following query doesn't make a response :
String query = "select * from Terms where Term = 'خدابخش'";
where the
'خدابخش'
part is in Persian and UTF-8 .
note that the connection to the database is fine .
Chances are that you may need to set your character encoding in your JDBC connection. If you are using MySQL JDBC Connector you do it using the property characterEncoding. Somewhat like this:
jdbc:mysql://localhost/some_db?useUnicode=yes&characterEncoding=UTF-8
You may want to read the reference on encoding and character sets in your connector JDBC documentation.
This is the one that mentions the use of characterEncoding for the MySQL JDBC Connector:
Connector JDBC: Using Character Sets and Unicode
One or more of the following is true:
The Java compiler, compiling your code, is set to read the source file with a different encoding in which the source file was actually stored. In other words, there is a discrepancy between the encoding that your editor uses, the encoding in which the file is actually saved, and the encoding with which the Java compiler is reading your source code.
Your database isn't set correctly to accept/store Unicode characters. Ensure that your database is set correctly. Looks like you're using MySQL. You may want to create a dump of the database using mysqldump and witness how the database was created with respect to character sets.

Execute Mysql query contains chinese character using java program

When I execute SQL query contains chines character, the query is executed successfully. When I open the mysql query browser I could see only ???? instead of Chinese texts. If the same query executed from the mysql query browser it works fine.
Try connecting with following switch
String url = "jdbc:mysql://host/database?characterSetResults=UTF-8&characterEncoding=UTF-8&useUnicode=yes";
All encoding must be the same (there are exceptions but let's forget them): the encoding used by the DB, the connection encoding use by the Java process and the one used by the query browser. You need to change the one used by Java, since the other two seem to be OK.

Problem logging utf-8 strings in MySQL from Java

I am trying to log a string sent from client side to MySQL database from a Java application. The string sent from client is UTF-8 encoded. I have confirmed this as I have taken packet traces using tool like wireshark. The string that the client sends are 3 characters which are Latin OE (0xc593), and beta (0xc39f), Euro sign (0xE2 0x82 0xAC). I am using prepared statement way of setstring to log the string into database. The table is created with support for utf-8 char encoding. Now, when I see the logged string in database I find this
select hex(message) from table1
C385 C293 C383 C29F C3A2 C282 C2AC
Seems like something is changing the string in the middle. Could anyone help me to solve this problem?
Thanks.
According to the MySQL docs,
Client applications that need to
communicate with the server using
Unicode should set the client
character set accordingly; for
example, by issuing a SET NAMES 'utf8'
statement.
You should also check the character_set_client and character_set_connection system variables to get an idea of how MySQL is attempting to interpret your string.
You can check the collation that individual tables are using by running the SHOW TABLE STATUS IN database query, as well.
Hopefully that will give you a clearer picture of exactly what the MySQL server is trying to do with the strings you're sending from the client. Reading up in the docs should be enlightening, as well.
Good luck :-)

Categories