Connector/J (JDBC) Reference
2069
should the driver instead create basic metadata
(all parameters reported as IN VARCHARs, but
allowing registerOutParameter() to be called on
them anyway) instead of throwing an exception?
noDatetimeStringSync
Don't ensure that
ResultSet.getDatetimeType().toString().equals(ResultSet.getString())
false
3.1.7
noTimezoneConversionForTimeType
Don't convert TIME values using the server
timezone if 'useTimezone'='true'
false
5.0.0
nullCatalogMeansCurrent
When DatabaseMetadataMethods ask for a
'catalog' parameter, does the value null mean use
the current catalog? (this is not JDBC-compliant,
but follows legacy behavior from earlier versions
of the driver)
true
3.1.8
nullNamePatternMatchesAll
Should DatabaseMetaData methods that accept
*pattern parameters treat null the same as '%' (this
is not JDBC-compliant, however older versions
of the driver accepted this departure from the
specification)
true
3.1.8
overrideSupportsIntegrityEnhancementFacility
Should the driver return "true" for
DatabaseMetaData.supportsIntegrityEnhancementFacility()
even if the database doesn't support it to
workaround applications that require this method
to return "true" to signal support of foreign keys,
even though the SQL specification states that this
facility contains much more than just foreign key
support (one such application being OpenOffice)?
false
3.1.12
padCharsWithSpace
If a result set column has the CHAR type and
the value does not fill the amount of characters
specified in the DDL for the column, should the
driver pad the remaining characters with space
(for ANSI compliance)?
false
5.0.6
pedantic
Follow the JDBC spec to the letter.
false
3.0.0
pinGlobalTxToPhysicalConnection
When using XAConnections, should the driver
ensure that operations on a given XID are
always routed to the same physical connection?
This allows the XAConnection to support "XA
START ... JOIN" after "XA END" has been called
false
5.0.1
populateInsertRowWithDefaultValues
When using ResultSets that are
CONCUR_UPDATABLE, should the driver pre-
populate the "insert" row with default values from
the DDL for the table used in the query so those
values are immediately available for ResultSet
accessors? This functionality requires a call to the
database for metadata each time a result set of
this type is created. If disabled (the default), the
default values will be populated by the an internal
call to refreshRow() which pulls back default
values and/or values changed by triggers.
false
5.0.5
processEscapeCodesForPrepStmts
Should the driver process escape codes in queries
that are prepared?
true
3.1.12
queryTimeoutKillsConnection If the timeout given in
Statement.setQueryTimeout() expires, should
false
5.1.9
Summary of Contents for 5.0
Page 1: ...MySQL 5 0 Reference Manual ...
Page 18: ...xviii ...
Page 60: ...40 ...
Page 396: ...376 ...
Page 578: ...558 ...
Page 636: ...616 ...
Page 844: ...824 ...
Page 1234: ...1214 ...
Page 1427: ...MySQL Proxy Scripting 1407 ...
Page 1734: ...1714 ...
Page 1752: ...1732 ...
Page 1783: ...Configuring Connector ODBC 1763 ...
Page 1793: ...Connector ODBC Examples 1773 ...
Page 1839: ...Connector Net Installation 1819 2 You must choose the type of installation to perform ...
Page 2850: ...2830 ...
Page 2854: ...2834 ...
Page 2928: ...2908 ...
Page 3000: ...2980 ...
Page 3122: ...3102 ...
Page 3126: ...3106 ...
Page 3174: ...3154 ...
Page 3232: ...3212 ...