Open zxh-im opened 1 week ago
The markdown format in your issue is incorrect. To facilitate reading, could you please revise it?
The markdown format in your issue is incorrect. To facilitate reading, could you please revise it?
I've already revised the Markdown format in my issue.
The issue involves other third-party dependencies, but our focus is solely on ShardingSphere itself. Since ShardingSphere implements the JDBC interface, standard applications should be functional. We wish to allocate more effort towards enhancing the current version, and therefore will no longer handle such issues. Please read the documentation or provide more effective information when submitting an issue.
The issue involves other third-party dependencies, but our focus is solely on ShardingSphere itself. Since ShardingSphere implements the JDBC interface, standard applications should be functional. We wish to allocate more effort towards enhancing the current version, and therefore will no longer handle such issues. Please read the documentation or provide more effective information when submitting an issue.
I see the error occurs in the SimpleTableSegmentBinder.checkTableExists method. The binderContext.getMetaData().getDatabase(databaseName).getSchema(schemaName).containsTable(tableName) method does not contain the current shard table. I debugged and found that this data should only have a single table. Can you tell me what to check?
The best way is to provide an operation that can be reproduced, such as executing reproducible SQL through JDBC or Proxy.
The SINGLE table is normal, while the SHARDING table reports an error version:shardingsphere-jdbc 5.5.1 sharding.yml:
createDataSource:
this is the stacktrace: