apache / apache/shardingsphere

ShardingSphere-Proxy MySQL replied incorrect binary flags in column definition

Open
#22,322 2 comments 0 reactions 0 assignees View on GitHub
db: MySQL in: proxy type: enhancement
Dominant language
Java
Stars
20.8k
Forks
6.9k
Avg merge
11h 38m
Merged PRs (30d)
326

Description

## Bug Report

### Which version of ShardingSphere did you use?

947c8c484b6eb6227891bc0500a52ce39f211584

### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy MySQL

### Expected behavior

MySQL:
![image](https://user-images.githubusercontent.com/20503072/203194313-b879bd85-626e-4f13-9ce4-9a2a774bb44f.png)

### Actual behavior

ShardingSphere-Proxy MySQL:
![image](https://user-images.githubusercontent.com/20503072/203194389-fc28a51d-24b0-4346-af3c-fb5f21bf76f8.png)

### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

```sql
select _binary'abc', X'20', X'41'
```

Contributor guide

Open the contributing guide

Research direction

Reproduce `select _binary'abc', X'20', X'41'` against ShardingSphere-Proxy MySQL and compare its column-definition binary flags with MySQL, using the expected and actual results in the report. Trace the Proxy's MySQL response handling for these expressions; done means the returned flags match MySQL.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, mysql
Domain
databases
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.