[CONJ-629] Incorrect SQL exception thrown when referential integrity Created: 2018-07-31 Updated: 2018-08-22 Resolved: 2018-08-22 |
|
| Status: | Closed |
| Project: | MariaDB Connector/J |
| Component/s: | batch |
| Affects Version/s: | 2.1.0 |
| Fix Version/s: | 2.1.2 |
| Type: | Bug | Priority: | Minor |
| Reporter: | Radek Wikturna | Assignee: | Diego Dupin |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Environment: |
Java 8, Windows 10, MariaDB 10.2.13 |
||
| Description |
|
After executing a DELETE statement on a row which cannot be deleted due to violation of a referential contraint, an SQL exception is thrown as expected. The exception is: However, when the same DELETE statement is executed as a batch (PreparedStatement.executeBatch()), then an incorrect exception is thrown: calling getCause() returns: java.sql.SQLException: Error reading results Index: 1, Size: 1 Details on the BatchUpdateException : |
| Comments |
| Comment by Diego Dupin [ 2018-08-22 ] |
|
this has been corrected since in 2.1.2. |