Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SHOW DATABASES & SHOW TABLES parse conflict with Oracle DatabaseType #30466

Closed
strongduanmu opened this issue Mar 12, 2024 · 1 comment · Fixed by #30518 or #31365
Closed

SHOW DATABASES & SHOW TABLES parse conflict with Oracle DatabaseType #30466

strongduanmu opened this issue Mar 12, 2024 · 1 comment · Fixed by #30518 or #31365

Comments

@strongduanmu
Copy link
Member

Bug Report

Which version of ShardingSphere did you use?

9462a44

Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?

ShardingSphere-Proxy

Expected behavior

When I parse SHOW DATABASES and SHOW TABLES with Oracle databaseType, it should not supported exception.

Actual behavior

Parse correctly.

Reason analyze (If you can)

systemVariable sytax in Oracle DALStatement.g4 is too loose. According to Oracle doc - https://docs.oracle.com/en/database/oracle/oracle-database/23/sqpug/SET-system-variable-summary.html#GUID-A6A5ADFF-4119-4BA4-A13E-BC8D29166FAE, systemVariable should only support system variables SET by the SET statement, not generic identifiers.

Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.

Example codes for reproduce this issue (such as a github link).

Copy link

There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment