sandynz opened a new issue, #37579: URL: https://github.com/apache/shardingsphere/issues/37579
## Bug Report ### Which version of ShardingSphere did you use? master branch ### Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy? JDBC ### Expected behavior Get correct schema name from parsed CREATE INDEX SQL. ### Actual behavior Run PostgreSQLMigrationGeneralE2EIT on openGauss, it failed. I added a new unit test `OpenGaussSQLParserEngineTest`, it could not get correct schema name too. ### Reason analyze (If you can) `TablesContext` doesn't extract owner as schema name: <img width="2816" height="1310" alt="Image" src="https://github.com/user-attachments/assets/6e306163-26c2-43a8-ad7a-b68ede799fb2"; /> -- Some test on openGauss: ``` openGauss=# select * from ds_0.schema1.t_user; ERROR: cross-database references are not implemented: "ds_0.schema1.t_user" LINE 1: select * from ds_0.schema1.t_user; ^ openGauss=# \c ds_0 Non-SSL connection (SSL connection is recommended when requiring high-security) You are now connected to database "ds_0" as user "omm". ds_0=# select * from schema1.t_user; id | username | password | schema1_flag | email ----+-----------+----------+--------------+-------- ``` `cross-database references are not implemented`, so could we just use owner as schema name for openGauss? ### Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc. Run unit test on `OpenGaussSQLParserEngineTest` (need to change assert code near TODO comment). ### Example codes for reproduce this issue (such as a github link). See `OpenGaussSQLParserEngineTest`. -- 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]
