Driver version

All (tested with 9.2.1 but same code is present in latest main branch).

Problem description

The normal behaviour of executeBatch is to clear the pending batch of operations, regardless of whether the batch execution completes successfully, succeeds for some rows and fails for others, or fails entirely with an exception:

(the code to reset batchParamValues to null is in a finally block and fires in all cases, even when an exception is thrown).

However, in the case where the bulk update API is used, batchParamValues is not cleared in the case of an exception:

(batchParamValues = null is not in a finally so does not run if any of the bcOperation methods were to throw an exception). This means that subsequent addBatch calls following a failure will append to the existing batch rather than starting a new one, and the next executeBatch will re-submit the previous batch of rows along with the new data.

Expected behavior

The logic should be the same in all cases - executeBatch should always clear the batch state so subsequent addBatch calls begin a new batch.

Actual behavior

As described above - in the bulk update case the batch is not cleared on failure.

Any other details that can be helpful

Since clearBatch is idempotent, a workaround would be for user code to do an explicit stmt.clearBatch() call (in a finally) after every call to executeBatch().