Workaround for containers that 'check' for sane values of
Statement.setFetchSize() so that applications can use
the Java variant of libmysql's mysql_use_result() behavior.
Some prepared statements return multiple results; the execute method
handles these complex statements as well as the simpler form of
statements handled by executeQuery and executeUpdate
Rewrites the already prepared statement into a multi-value insert
statement of 'statementsPerBatch' values and executes the entire batch
using this new statement.
Rewrites the already prepared statement into a multi-statement
query of 'statementsPerBatch' values and executes the entire batch
using this new statement.
Should the driver execute this interceptor only for the
"original" top-level query, and not put it in the execution
path for queries that may be executed from other interceptors?
If an interceptor issues queries using the connection it was created for,
and does not return true for this method, it must ensure
that it does not cause infinite recursion.