Oracle 5.0 Reference Manual page 2082

elideSetAutoCommits
enableQueryTimeouts
holdResultsOpenOverStatementClose
largeRowSizeThreshold
loadBalanceStrategy
locatorFetchBufferSize
rewriteBatchedStatements
Connector/J (JDBC) Reference
If using MySQL-4.1 or newer, should the driver
only issue 'set autocommit=n' queries when the
server's state doesn't match the requested state
by Connection.setAutoCommit(boolean)?
When enabled, query timeouts set via
Statement.setQueryTimeout() use a shared
java.util.Timer instance for scheduling. Even if
the timeout doesn't expire before the query is
processed, there will be memory used by the
TimerTask for the given timeout which won't be
reclaimed until the time the timeout would have
expired if it hadn't been cancelled by the driver.
High-load environments might want to consider
disabling this functionality.
Should the driver close result sets on
Statement.close() as required by the JDBC
specification?
What size result set row should the JDBC driver
consider "large", and thus use a more memory-
efficient way of representing the row internally?
If using a load-balanced connection to
connect to SQL nodes in a MySQL Cluster/
NDB configuration (by using the URL prefix
"jdbc:mysql:loadbalance://"), which load balancing
algorithm should the driver use: (1) "random" - the
driver will pick a random host for each request.
This tends to work better than round-robin, as the
randomness will somewhat account for spreading
loads where requests vary in response time, while
round-robin can sometimes lead to overloaded
nodes if there are variations in response times
across the workload. (2) "bestResponseTime" -
the driver will route the request to the host that
had the best response time for the previous
transaction.
If 'emulateLocators' is configured to 'true', what
size buffer should be used when fetching BLOB
data for getBinaryInputStream?
Should the driver use multiqueries (irregardless
of the setting of "allowMultiQueries") as well as
rewriting of prepared statements for INSERT
into multi-value inserts when executeBatch()
is called? Notice that this has the potential for
SQL injection if using plain java.sql.Statements
and your code doesn't sanitize input correctly.
Notice that for prepared statements, server-
side prepared statements can not currently
take advantage of this rewrite option, and that
if you don't specify stream lengths when using
PreparedStatement.set*Stream(), the driver won't
be able to determine the optimum number of
parameters per batch and you might receive an
error from the driver that the resultant packet
is too large. Statement.getGeneratedKeys() for
2062
false 3.1.3
true 5.0.6
false 3.1.7
2048 5.1.1
random 5.0.6
1048576 3.2.1
false 3.1.13