Oracle 5.0, Reference Manual

Page: 2091 / 3232

Connector/J (JDBC) Reference
2071
(value of "false" is legacy behavior, "true" leads to
more JDBC-compliant behavior.
useHostsInPrivileges Add '@hostname' to users in
DatabaseMetaData.getColumn/TablePrivileges()
(true/false), defaults to 'true'. true 3.0.2
useInformationSchema When connected to MySQL-5.0.7
or newer, should the driver use the
INFORMATION_SCHEMA to derive information
used by DatabaseMetaData? false 5.0.0
useJDBCCompliantTimezoneShift Should the driver use JDBC-compliant rules
when converting TIME/TIMESTAMP/DATETIME
values' timezone information for those JDBC
arguments which take a java.util.Calendar
argument? (Notice that this option is exclusive of
the "useTimezone=true" configuration option.) false 5.0.0
useLegacyDatetimeCode Use code for DATE/TIME/DATETIME/
TIMESTAMP handling in result sets and
statements that consistently handles timezone
conversions from client to server and back again,
or use the legacy code for these datatypes
that has been in the driver for backwards-
compatibility? true 5.1.6
useOldAliasMetadataBehavior Should the driver use the legacy behavior
for "AS" clauses on columns and tables,
and only return aliases (if any) for
ResultSetMetaData.getColumnName() or
ResultSetMetaData.getTableName() rather than
the original column/table name? In 5.0.x, the
default value was true.
false 5.0.4
useOldUTF8Behavior Use the UTF-8 behavior the driver did when
communicating with 4.0 and older servers false 3.1.6
useOnlyServerErrorMessages Don't prepend 'standard' SQLState error
messages to error messages returned by the
server.
true 3.0.15
useSSPSCompatibleTimezoneShift If migrating from an environment
that was using server-side prepared
statements, and the configuration property
"useJDBCCompliantTimeZoneShift" set to
"true", use compatible behavior when not using
server-side prepared statements when sending
TIMESTAMP values to the MySQL server. false 5.0.5
useServerPrepStmts Use server-side prepared statements if the server
supports them? false 3.1.0
useSqlStateCodes Use SQL Standard state codes instead of 'legacy'
X/Open/SQL state codes (true/false), default is
'true' true 3.1.3
useStreamLengthsInPrepStmtsHonor stream length parameter in
PreparedStatement/ResultSet.setXXXStream()
method calls (true/false, defaults to 'true')?
true 3.0.2
useTimezone Convert time/date types between client and server
timezones (true/false, defaults to 'false')? false 3.0.2
useUnbufferedInput Don't use BufferedInputStream for reading data
from the server true 3.0.11