Oracle 5.0 Reference Manual page 2089

noDatetimeStringSync
noTimezoneConversionForTimeType
nullCatalogMeansCurrent
nullNamePatternMatchesAll
overrideSupportsIntegrityEnhancementFacility
padCharsWithSpace
pedantic
pinGlobalTxToPhysicalConnection
populateInsertRowWithDefaultValues
processEscapeCodesForPrepStmts
queryTimeoutKillsConnection If the timeout given in
Connector/J (JDBC) Reference
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?
Don't ensure that
ResultSet.getDatetimeType().toString().equals(ResultSet.getString())
Don't convert TIME values using the server
timezone if 'useTimezone'='true'
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)
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)
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)?
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)?
Follow the JDBC spec to the letter.
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
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.
Should the driver process escape codes in queries
that are prepared?
Statement.setQueryTimeout() expires, should
2069
false 3.1.7
false 5.0.0
true 3.1.8
true 3.1.8
false 3.1.12
false 5.0.6
false 3.0.0
false 5.0.1
false 5.0.5
true 3.1.12
false 5.1.9