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

EncryptDatasource does not support sql which is not DML #2081

Closed
codefairy08 opened this issue Mar 25, 2019 · 1 comment
Closed

EncryptDatasource does not support sql which is not DML #2081

codefairy08 opened this issue Mar 25, 2019 · 1 comment

Comments

@codefairy08
Copy link
Contributor

Bug Report

For English only, other languages will not accept.

Before report a bug, make sure you have:

Please pay attention on issues you submitted, because we maybe need more details.
If no response more than 7 days and we cannot reproduce it on current information, we will close it.

Please answer these questions before submitting your issue. Thanks!

Which version of ShardingSphere did you use?

4.0.0-RC1-SNAPSHOT

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

Sharding-JDBC

Expected behavior

execute sql which is not DML

Actual behavior

throw Exception, Message is "Unsupported SQL of ${SQL}"

Reason analyze (If you can)

current just fill DML statement to DMLStatement, the other sql does not fill,design a new class for the sql which is not DML. do not execute filler logic.

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

use EncryptDatasource execute a DDL statement: "CREATE TABLE t_test (id int primary key auto_increment, pwd varchar(100), pwd_assist varchar(100));"

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

@codefairy08 codefairy08 self-assigned this Mar 25, 2019
codefairy08 added a commit to codefairy08/incubator-shardingsphere that referenced this issue Mar 26, 2019
terrymanu added a commit that referenced this issue Mar 29, 2019
@tristaZero
Copy link
Contributor

Testing for this issue has been done. Everything is ok.

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

No branches or pull requests

3 participants