liyimingcust opened a new issue, #24333:
URL: https://github.com/apache/shardingsphere/issues/24333
### Which version of ShardingSphere did you use?
5.0.0
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
Considering sql_mode without NO_BACKSLASH_ESCAPES,cipher column should
escape the backslash before encrypt and store;
### Actual behavior
Cipher column encrypt the value with backslash;
### Reason analyze (If you can)
Mysql could properly handle backslash as an escape character,SS considers it
as plaintext instead;
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
You guys could try sqls like this(make sure that SS's address_json has a
cipher column address_json_cipher )
A : insert into table_a set `address_json` = '{\"full_address\":\"\"}';
B : insert into table_a set `address_json` = '{"full_address":""}';
if the service side was origin Mysql, address_json should be the same.
But if the service side was SS, address_json are same,address_json_cipher
are different;
--
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.
To unsubscribe, e-mail:
[email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
