[MDEV-18990] Wrong result when binary column is used as a condition in hexadecimal mode Created: 2019-03-21  Updated: 2020-06-08  Resolved: 2020-06-08

Status: Closed
Project: MariaDB Server
Component/s: Storage Engine - Spider
Affects Version/s: None
Fix Version/s: 10.4.5

Type: Bug Priority: Major
Reporter: willhan Assignee: Kentoku Shiba (Inactive)
Resolution: Duplicate Votes: 0
Labels: None


 Description   

Wrong result when binary column is used as a condition in hexadecimal mode
query : select xx from t where name=0x15101408BFF8380088000C458048000C”
before distribution: select xx from t where name=0x15101408 （be cut off）
now distribution: select xx from t where name=0x15101408BFF8380088000C458048000C”

 Comments   
Comment by Kentoku Shiba (Inactive) [ 2019-05-03 ]

willhan
This issue is fixed by MDEV-18992. Please see the test result of the following commit.
6175198

Comment by willhan [ 2019-05-07 ]

kentoku
I only get test suite , but not fix about "hex be cut off" ?

Comment by Kentoku Shiba (Inactive) [ 2019-05-07 ]

willhan
No, it's not cut off. The test case uses same value (0x15101408BFF8380088000C458048000C), and it works well.

Comment by willhan [ 2019-05-08 ]

kentoku
Ok, you are right
Function "Item_hex_string::print" "Item_hex_hybrid::print" in MariaDB 10.3 is different from MySQL 5.5;

Generated at Thu Feb 08 08:48:15 UTC 2024 using Jira 8.20.16#820016-sha1:9d11dbea5f4be3d4cc21f03a88dd11d8c8687422.