[GitHub] [shardingsphere] xiaojingkai opened a new issue #10107: (sharding-proxy)The value of character_set is transformed between utf8 and utf8mb4

Fri, 16 Apr 2021 00:44:30 -0700 


xiaojingkai opened a new issue #10107:
URL: https://github.com/apache/shardingsphere/issues/10107


   
   
   
   ### Which version of ShardingSphere did you use?
   
   shardingsphere-5.0.0-alpha
   
   ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
   
   ShardingSphere-Proxy
   
   ### Expected behavior
   
   insert emoji through utf8mb4
   
   ### Actual behavior
   
   Unable to insert Emoji ，and the value of character_set is transformed 
between utf8 and utf8mb4 when I connect to the proxy to execute the "SHOW 
VARIABLES WHERE Variable_name LIKE 'character\_set\_%' OR Variable_name LIKE 
'collation%';" sql，but , the value of character_set  is always utf8mb4 when I 
connect to master DB or slave DB 
   
   ### Reason analyze (If you can)
   
   I think,  sometimes the value of character_set will become utf8 instead of 
utf8mb4, so Emoji cannot be inserted
   
   ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule 
configuration, when exception occur etc.
   
   1、config config-master_slave.yaml & server.yaml
   2、mysql drive is  mysql-connector-java-5.1.49.jar
   3、connect sharding-proxy:  can not insert emoji
   4、connect real mysql:  can insert emoji
   
   ### Example codes for reproduce this issue (such as a github link).
   INSERT INTO spider_xhs_note (
           fd_id,
           fd_desc,
           id
           )
   VALUES
           (
                   '6072e0d800000000210369d4',
                   '我个人是追崇轻松感氛围穿搭的，错误穿搭对我而言更多的是不够松，我在现实里，这几年真的重来没有这样穿过😂@小红书视频号  
 @穿搭薯',
                   '178d554a96d8ae6b8ba0e814206a1f2b'
           )


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to