-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
problem in SQLServerStatementSQLVisitor.class #32354
Comments
No plan to enhance with SQLServer for now, does any one want to do it? |
Is it that I want to be simple, I think it should only take |
I cannot suggest without investigate. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug Report
Which version of ShardingSphere did you use?
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
execute sql like
then parse to
Actual behavior
Reason analyze (If you can)
In class
SQLServerStatementSQLVisitor.class#visitOrderBy
,offset paramIndex and rowcount paramIndex not right, causedPaginationContext
get param in List params out of bounds.Steps to reproduce the behavior, such as: SQL to execute, sharding rule configuration, when exception occur etc.
SpringBoot + Mybatis + Similar to the
sql
mentioned aboveExample codes for reproduce this issue (such as a github link).
The text was updated successfully, but these errors were encountered: