Bug #118201 | A potential bug in Mysql Connector/J | ||
---|---|---|---|
Submitted: | 15 May 2:37 | Modified: | 7 Jul 22:05 |
Reporter: | 策 吕 | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | Connector / J | Severity: | S3 (Non-critical) |
Version: | 9.0.0 | OS: | Any |
Assigned to: | CPU Architecture: | Any |
[15 May 2:37]
策 吕
[19 May 5:34]
策 吕
Sorry, there was a spelling error in the code, didn't notice it on commit: stmt.execute("DROP TABLE IF EXIST t0"); Fix it as stmt.execute("DROP TABLE IF EXISTS t0");
[20 May 10:29]
Filipe Silva
Thank you for your interest in MySQL Connector/J and for taking the time to file this bug report. Regardless what the documentation says about the connection property `allowMultiQueries`, it does affect batched statements. This is the behavior since the early days of the driver. What remains to see if whether this should be fixed in the documentation or if it makes sense to change the behavior of this property. Note that two other connection properties have the power to affect how batched statements are executed: `rewriteBatchedStatements` and `continueBatchOnError`. For these reasons, I'm setting this report as "verified".
[7 Jul 22:05]
Daniel So
Posted by developer: Added an entry to the Connector/J 9.4.0 changelog: "Enabling allowMultiQueries without also enabling rewriteBatchedStatements caused statements to be rewritten, which was not the expected behavior. With this fix, allowMultiQueries only allows users to execute multiple queries in a single Statement, whereas batching, including statement rewriting, is governed exclusively by rewriteBatchedStatements."
[16 Jul 19:52]
Axyoan Marcelo
Duplicated by Bug#118167