We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
9462a44
ShardingSphere-Proxy
When I parse SHOW DATABASES and SHOW TABLES with Oracle databaseType, it should not supported exception.
SHOW DATABASES
SHOW TABLES
Parse correctly.
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.
The text was updated successfully, but these errors were encountered:
There hasn't been any activity on this issue recently, and in order to prioritize active issues, it will be marked as stale.
Sorry, something went wrong.
yydeng626
Successfully merging a pull request may close this issue.
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
andSHOW 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).
The text was updated successfully, but these errors were encountered: