-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Mysql limit does not support variant #6527
Comments
did you try:
|
I tried it. |
@Simbafa Please set sql.show: true and show me the log of ShardingSphere-Proxy. |
@Simbafa I can't reproduce this problem. Can you use the existing codes to connect directly to a MySQL server, and find whether there's the same problem? |
I have tried connecting to MySql directly, It's OK. |
|
Can you update the Connect-Java from 5.1.42 to 5.1.47? |
Have you modified any codes of ShardingSphere-Proxy? |
MySQLPacketCodecEngine.java is modified, because sometimes resetReaderIndex() is called.
When using 5.1.47, "java.sql.SQLException: Unknown system variable 'transaction_isolation'" is thrown.
|
5.1.47 is used both in client and sharding-proxy. |
What is your MySQL server version? |
mariadb:10.5 |
Can you change to MySQL server and have a test? |
I suggest you to download a binary version of Proxy to do this test. The download page as follows: |
I tested MySql:5.7, "transaction_isolation" issue disappear. |
I downloaded the tar file, and tested. |
I can't reproduce it with sharding strategy. |
Can you please try 5.0.0-SNAPSHOT of master branch? |
server.yaml
config-sharding.yaml
I will try 5.0.0-SNAPSHOT |
I have reproduced this problem with you configuration. |
* apache#6527, parameters for transparent mode * apache#6527, refine
* Visit CreateDataSourcesStatement * add setter * Modify interface for DatabaseTypes * add insert select and replace select statement doc (#6521) * add insert select statement doc * add replace select statement doc * modify doc description * Fix #3954 : Sharding-JDBC querying support PostgreSQL array type (#6524) * Sharding-JDBC support PostgreSQL array type * Sharding-JDBC support PostgreSQL array type * Sharding-JDBC support PostgreSQL array type, try to fix ci error * check style * Refactor sqlStatement context converter * Rename ProxyConfigurationLoader (#6540) * refactor OrchestrationShardingSphereDataSource * refactor OrchestrationShardingSphereDataSource * refactor OrchestrationShardingSphereDataSource * Rename ProxyConfigurationLoader * Refactor ProxyConfigurationLoader * Refactor ProxyConfigurationConverter * Fix javadoc * Fix javadoc * Refactor OrchestrationShardingSphereDataSource * Refactor OrchestrationShardingSphereDataSource * #6294 oracle support select for update (#6538) * #6527, parameters for transparent mode (#6545) * #6527, parameters for transparent mode * #6527, refine * update release guide of elasticjob (#6549) * support select '' as a from order (#6542) * Adjust executor and engine package directory (#6552) * Create ShardingSphereSQLParserEngine and factory (#6553) * Adjust sql engine package dir (#6554) * Add BootstrapArguments (#6555) * Refactor ProxyConfigurationConverterFactory * Refactor ProxyConfigurationLoader * Adjust private method order of Bootstrap * Add BootstrapArguments * use ShardingSphereSQLParserEngine instead of SQLParserEngine (#6557) * Refactor Bootstrap's log (#6559) * Refactor Bootstrap * Refactor Bootstrap's log * fix docs (#6560) * Remove ProxyConfigurationConverter (#6564) * rename Bootstrap.init * Refactor Bootstrap.log * Remove useless javadoc * Add final * Revise ProxyConfiguration * Revise DataSourceParameter * Revise DataSourceParameter * Refactor OrchestrationConfigurationConverter * Add OrchestrationBootstrap * Add YamlProxyConfigurationSwapper * Remove ProxyConfigurationConverter * Refactor Bootstrap * Refactor Bootstrap * Refactor Bootstrap * Remove Serializable for ProxyConfiguration * refactor OrchestrationBootstrap * For checkstyle * Add orchestrationEnabled for Bootstrap (#6565) * Refactor Bootstrap * Add orchestrationEnabled for Bootstrap * update release guide about docker (#6566) * docker release guide for elasticjob (#6567) * docker release for elasticjob * docker release guide for elasticjob ui * Create maven.yml (#6563) * Remove ShardingSphereSchema.dataSourceParameters (#6569) * Decouple ShardingSphereSchema.dataSourceParameters * Remove ShardingSphereSchema.dataSourceParameters * Add ProxyDataSourceContext * Refactor SchemaContextsBuilder * Visit CreateDataSourcesStatement * Adjust executor and engine package directory (#6552) * Adjust sql engine package dir (#6554) * Adjust executor and engine package directory (#6552) * Adjust sql engine package dir (#6554) * Adjust executor and engine package directory (#6552) * Adjust sql engine package dir (#6554) * Rename "unfinish" to "unfinished"(#6571) * Rename "unfinish" to "unfinished"(#6571) Co-authored-by: tristaZero <[email protected]> Co-authored-by: DuanZhengqiang <[email protected]> Co-authored-by: sandynz <[email protected]> Co-authored-by: Liang Zhang <[email protected]> Co-authored-by: zangyk <[email protected]> Co-authored-by: Zhang Yonglun <[email protected]> Co-authored-by: cmonkey <[email protected]> Co-authored-by: Juan Pan(Trista) <[email protected]> Co-authored-by: kimmking <[email protected]> Co-authored-by: qiulu3 <Lucas209910>
Bug Report
Which version of ShardingSphere did you use?
The latest version: Shardingsphere-ui-4.1.1
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-Proxy
Expected behavior
limit/offset can use variants.
Actual behavior
ERROR: Statement parameter 1 not set., SqlState: S1009, code:0
Reason analyze (If you can)
I searched internet, someone says that Mysql does not support limit variant before 5.5 version.
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: