Oracle 5.0 Reference Manual page 2081

alwaysSendSetIsolation
maintainTimeStats
useCursorFetch
blobSendChunkSize
cacheCallableStmts
cachePrepStmts
cacheResultSetMetadata
cacheServerConfiguration
defaultFetchSize
dontTrackOpenResources
dynamicCalendars
Connector/J (JDBC) Reference
Map<String, String>>, which will be used to create
caches for MySQL server configuration values
Should the driver always
communicate with the database when
Connection.setTransactionIsolation() is
called? If set to false, the driver will only
communicate with the database when the
requested transaction isolation is different than
the whichever is newer, the last value that was
set via Connection.setTransactionIsolation(),
or the value that was read from the server
when the connection was established. Note
that useLocalSessionState=true will force the
same behavior as alwaysSendSetIsolation=false,
regardless of how alwaysSendSetIsolation is set.
Should the driver maintain various internal
timers to enable idle time calculations as well
as more verbose error messages when the
connection to the server fails? Setting this
property to false removes at least two calls to
System.getCurrentTimeMillis() per query.
If connected to MySQL > 5.0.2, and
setFetchSize() > 0 on a statement, should that
statement use cursor-based fetching to retrieve
rows?
Chunk to use when sending BLOB/CLOBs via
ServerPreparedStatements
Should the driver cache the parsing stage of
CallableStatements
Should the driver cache the parsing stage of
PreparedStatements of client-side prepared
statements, the "check" for suitability of server-
side prepared and server-side prepared
statements themselves?
Should the driver cache ResultSetMetaData for
Statements and PreparedStatements? (Req.
JDK-1.4+, true/false, default 'false')
Should the driver cache the results of 'SHOW
VARIABLES' and 'SHOW COLLATION' on a per-
URL basis?
The driver will call setFetchSize(n) with this value
on all newly-created Statements
The JDBC specification requires the driver to
automatically track and close resources, however
if your application doesn't do a good job of
explicitly calling close() on statements or result
sets, this can cause memory leakage. Setting this
property to true relaxes this constraint, and can be
more memory efficient for some applications.
Should the driver retrieve the default calendar
when required, or cache it per connection/
session?
2061
true 3.1.7
true 3.1.9
false 5.0.0
1048576 3.1.9
false 3.1.2
false 3.0.10
false 3.1.1
false 3.1.5
0 3.1.9
false 3.1.7
false 3.1.5