Oracle 5.0 Reference Manual page 2087

continueBatchOnError
createDatabaseIfNotExist
emptyStringsConvertToZero
emulateLocators
emulateUnsupportedPstmts
exceptionInterceptors
functionsNeverReturnBlobs
generateSimpleParameterMetadata
ignoreNonTxTables
jdbcCompliantTruncation
loadBalanceAutoCommitStatementRegex
Connector/J (JDBC) Reference
Should the driver continue processing batch
commands if one statement fails. The JDBC spec
allows either way (defaults to 'true').
Creates the database given in the URL if it doesn't
yet exist. Assumes the configured user has
permissions to create databases.
Should the driver allow conversions from empty
string fields to numeric values of '0'?
Should the driver emulate java.sql.Blobs with
locators? With this feature enabled, the driver
will delay loading the actual Blob data until the
one of the retrieval methods (getInputStream(),
getBytes(), and so forth) on the blob data stream
has been accessed. For this to work, you must
use a column alias with the value of the column
to the actual name of the Blob. The feature also
has the following restrictions: The SELECT that
created the result set must reference only one
table, the table must have a primary key; the
SELECT must alias the original blob column
name, specified as a string, to an alternate name;
the SELECT must cover all columns that make up
the primary key.
Should the driver detect prepared statements that
are not supported by the server, and replace them
with client-side emulated versions?
Comma-delimited list of classes that implement
com.mysql.jdbc.ExceptionInterceptor. These
classes will be instantiated one per Connection
instance, and all SQLExceptions thrown by the
driver will be allowed to be intercepted by these
interceptors, in a chained fashion, with the first
class listed as the head of the chain.
Should the driver always treat data from functions
returning BLOBs as Strings - specifically to work
around dubious metadata returned by the server
for GROUP BY clauses?
Should the driver generate simplified parameter
metadata for PreparedStatements when no
metadata is available either because the server
couldn't support preparing the statement, or
server-side prepared statements are disabled?
Ignore non-transactional table warning for
rollback? (defaults to 'false').
Should the driver throw java.sql.DataTruncation
exceptions when data is truncated as is required
by the JDBC specification when connected to a
server that supports warnings (MySQL 4.1.0 and
newer)? This property has no effect if the server
sql-mode includes STRICT_TRANS_TABLES.
When load-balancing is enabled
for auto-commit statements (via
loadBalanceAutoCommitStatementThreshold), the
statement counter will only increment when the
2067
true 3.0.3
false 3.1.9
true 3.1.8
false 3.1.0
true 3.1.7
5.1.8
false 5.0.8
false 5.0.5
false 3.0.9
true 3.1.2
5.1.15