Open strongduanmu opened 1 year ago
I want to try it
@lushaorong Welcome, I will assign this issue to you.
I run AdditionalDMLE2EIT.assertExecuteUpdateWithColumnIndexes
test and I get error message No tests found matching assertExecuteUpdateWithColumnIndexes with any parameter from org.junit.runner.Request
. It doesn't seem to work.
@strongduanmu
Sorry, I can't finish this task,Please reassign someone else to finish it.
@lushaorong Thank you for your remind.
Bug Report
Which version of ShardingSphere did you use?
f52f484
Which project did you use? ShardingSphere-JDBC or ShardingSphere-Proxy?
ShardingSphere-JDBC
Expected behavior
Execute
INSERT INTO t_user (user_id, user_name_cipher, user_name_like, user_name_plain, password_cipher, email_cipher, telephone_cipher, telephone_like, telephone_plain, creation_date) VALUES (?, ?, ?, ?, 'MyOShk4kjRnds7CZfU5NCw==', 'VvWKtMDr5+58OMAAu6BH5A==', '8Rj1Bg696vJMKwPNxzxGOg==', '01450145014', '12341234123', '2018-08-08'), (?, ?, ?, ?, 'qbUuBn0oxdrV8sNNyoqDCg==', 'FRo1h44oclER1+0MeI1T0w==', 'cD36lxxtVApK4QLzec87zg==', '14541454545', '23452345456', '2019-08-08')
successfully with JDBC executeUpdateForPreparedStatementWithColumnNames interfaceActual behavior
Reason analyze (If you can)
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).