RaigorJiang opened a new issue, #38846:
URL: https://github.com/apache/shardingsphere/issues/38846
## Bug Report
### Which version of ShardingSphere did you use?
5.5.4-SNAPSHOT c65bed3358a66f71d744cdc95e3e46cbf0c1d0e4
### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
### Expected behavior
When storage units of different case exist, `SHOW RULES USED STORAGE UNIT
xxx` can retrieve the specified target.
### Actual behavior
SHOW RULES USED STORAGE UNIT cannot distinguish between them.
### Steps to reproduce the behavior, such as: SQL to execute, sharding rule
configuration, when exception occur etc.
1. register storage units
```sql
REGISTER STORAGE UNIT ds_0 (
URL="jdbc:mysql://127.0.0.1:3306/demo_ds_0?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true",
USER="root",
PASSWORD="123456",
PROPERTIES("maximumPoolSize"=10,"minimumIdle"=1)
), ds_1 (
URL="jdbc:mysql://127.0.0.1:3306/demo_ds_1?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true",
USER="root",
PASSWORD="123456",
PROPERTIES("maximumPoolSize"=10,"minimumIdle"=1)
), DS_0 (
URL="jdbc:mysql://127.0.0.1:3306/demo_ds_2?serverTimezone=UTC&useSSL=false&allowPublicKeyRetrieval=true",
USER="root",
PASSWORD="123456",
PROPERTIES("maximumPoolSize"=10,"minimumIdle"=1)
);
```
2. Create rule
```sql
CREATE READWRITE_SPLITTING RULE group_0 (
WRITE_STORAGE_UNIT=ds_0,
READ_STORAGE_UNITS(ds_1),
TRANSACTIONAL_READ_QUERY_STRATEGY='PRIMARY',
TYPE(NAME="RANDOM")
);
```
3. Show rule
```sql
SHOW READWRITE_SPLITTING RULE group_0;
```
4. SHOW RULES USED STORAGE UNIT
```sql
SHOW RULES USED STORAGE UNIT ds_0;
SHOW RULES USED STORAGE UNIT ds_1;
SHOW RULES USED STORAGE UNIT DS_0;
```
<img width="1089" height="617" alt="Image"
src="https://github.com/user-attachments/assets/bfa4639e-4089-46a1-be2e-fcecf23955f4";
/>
--
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]
