ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Martin <ghx02...@126.com>
Subject Re:Re: encountering a character encoding problem when DML SQL is used
Date Thu, 20 Jul 2017 01:13:57 GMT



I called it from Java, and i am using Ignite 2.0.
seems many chinese developer are encountering this problem. 
is there any configuration that can set as encoding? or is there any API method can do this?






thanks,
Martin







At 2017-07-20 00:34:45, "afedotov" <alexander.fedotoff@gmail.com> wrote:

Hi Martin,

I've checked the same with 2.0 and it works on my side.

Which version of Ignite do you use?
Do you call it from Java, .NET or C++ ?
Please check that source files encoding is consistent. It's better to stick with UTF-8.


Kind regards,
Alex.


On Wed, Jul 19, 2017 at 4:47 AM, Martin [via Apache Ignite Users] <[hidden email]> wrote:

Hi guys,


    I am now encountering a character encoding problem when DML SQL is used.
For example, if i run the DML SQL like the following sentence:
 update tableA set columnA="测试" and columnB="你好" where _key=1
it can works, but when i get it(_key=1) from the cache , i get the messy word. 


any ideas about this? is there any way to set character encoding?




thanks for your help






Thanks,
Martin






 




If you reply to this email, your message will be added to the discussion below:
http://apache-ignite-users.70518.x6.nabble.com/encountering-a-character-encoding-problem-when-DML-SQL-is-used-tp15094.html
To start a new topic under Apache Ignite Users, email [hidden email]
To unsubscribe from Apache Ignite Users, click here.
NAML




View this message in context: Re: encountering a character encoding problem when DML SQL is
used
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Mime
View raw message