[CONJ-206] Take max_allowed_packet into consideration when rewriting statements Created: 2015-10-20 Updated: 2015-11-02 Resolved: 2015-11-02 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | Other |
| Affects Version/s: | 1.2.2, 1.2.3 |
| Fix Version/s: | 1.3.0 |
| Type: | Task | Priority: | Major |
| Reporter: | Andrei Anishchenko | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 1 |
| Labels: | None | ||
| Environment: |
Windows 7 Professional java version "1.8.0_51" |
||
| Attachments: |
|
||||||||
| Issue Links: |
|
||||||||
| Description |
|
Attached please find a couple of tests, one with MariaDB Connector and another with MySQL Connector. Both do the same, but with the default value of max_allowed_packet the first test fails while the other stands. As per MySQL Connector, on the other hand, rewrites the statement, splitting the result as needed in order not to exceed the value of max_allowed_packet (see com.mysql.jdbc.PreparedStatement#computeBatchSize).
|
| Comments |
| Comment by Diego Dupin [ 2015-10-23 ] |
|
Good remark. That is something that will be done to avoid max_allowed_packet Exception. |
| Comment by Diego Dupin [ 2015-11-02 ] |
|
fixed in 1.3.0 |