terrymanu commented on issue #33784:
URL:
https://github.com/apache/shardingsphere/issues/33784#issuecomment-3536574567
🔍 Problem Analysis
Based on the information provided, I noticed a critical detail: The table
name used in your configuration file and SQL is HuangHStu (starting with
uppercase), but the actual table name shown in the error screenshot is
huanghstu (starting with lowercase).
🎯 Possible Root Cause
This is likely a table name case mismatch issue:
- MySQL is case-sensitive for table names on Linux systems
- HuangHStu ≠ huanghstu
- ShardingSphere routes to the correct database, but MySQL cannot find the
table with the correct name
📋 Key Information Needed
To accurately identify the problem, please provide the following
information:
1. MySQL Case Sensitivity Setting
SHOW VARIABLES LIKE 'lower_case_table_names';
2. Actual Table Name Verification
SHOW TABLES FROM ds_0;
SHOW TABLES FROM ds_1;
3. Complete ShardingSphere Configuration File
Please provide your complete configuration file, not just screenshot
fragments.
4. Complete Error Log
Please provide the complete error stack trace, not just "Route table does
not exist".
5. Environment Information
- Operating system (Linux/Windows/macOS)
- MySQL installation method
- Exact SQL statements used when creating tables
💡 Temporary Solutions
If it's indeed a case sensitivity issue, you can try:
Solution 1: Modify Configuration File
rules:
- SHARDING:
tables:
huanghstu: # Change to lowercase
actualDataNodes: ds_${0..1}.huanghstu
Solution 2: Recreate Tables
CREATE TABLE HuangHStu (
Sno VARCHAR(20) PRIMARY KEY,
-- other fields
);
🔧 Verification Steps
1. Confirm the value of lower_case_table_names
2. Verify the matching relationship between logical and physical table
names
3. Provide complete configuration and log information
With this information, we can determine if it's a table name case
sensitivity issue and provide a precise solution.
Looking forward to your response! 🚀
--
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]
