mlmw92 opened a new issue, #34350: URL: https://github.com/apache/shardingsphere/issues/34350
I upgraded from sharding-jdbc 4.1.1 to shardingsphere-jdbc 5.5.1, using PostgreSQL as the database. After the upgrade, I encountered an error message stating "**Table or view does not exist.**" I have followed the documentation instructions to add single-table scanning. After debugging, I found that single tables can be registered, but when calling the `getSchemaName` method in `SimpleTableSegmentBinder`, I noticed it returns DefaultSchemaName. However, my schema name is not public. I have specified the currentSchema in the JDBC connection, so I believe getSchemaName should prioritize reading the currentSchema from the JDBC connection. -- 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]
