Oracle 5.0 Reference Manual page 2085

resultSetSizeThreshold
traceProtocol
useNanosForElapsedTime
Miscellaneous.
Property Name
useUnicode
characterEncoding
characterSetResults
connectionAttributes
connectionCollation
useBlobToStoreUTF8OutsideBMP
utf8OutsideBmpExcludedColumnNamePattern
utf8OutsideBmpIncludedColumnNamePattern
Connector/J (JDBC) Reference
If the usage advisor is enabled, how many rows
should a result set contain before the driver warns
that it is suspiciously large?
Should trace-level network protocol be logged?
For profiling/debugging functionality that measures
elapsed time, should the driver try to use
nanoseconds resolution if available (JDK >= 1.5)?
Definition
Should the driver use Unicode character
encodings when handling strings? Should only
be used when the driver can't determine the
character set mapping, or you are trying to 'force'
the driver to use a character set that MySQL either
doesn't natively support (such as UTF-8), true/
false, defaults to 'true'
If 'useUnicode' is set to true, what character
encoding should the driver use when dealing with
strings? (defaults is to 'autodetect')
Character set to tell the server to return results as.
A comma-delimited list of user-defined key:value
pairs (in addition to standard MySQL-defined
key:value pairs) to be passed to MySQL Server
for display as connection attributes in the
PERFORMANCE_SCHEMA.SESSION_CONNECT_ATTRS
table. Example usage:
connectionAttributes=key1:value1,key2:value2
This functionality is available for use with MySQL
Server version 5.6 or later only. Earlier versions
of MySQL Server do not support connection
attributes, causing this configuration option will
be ignored. Setting connectionAttributes=none
will cause connection attribute processing to
be bypassed, for situations where Connection
creation/initialization speed is critical.
If set, tells the server to use this collation via 'set
collation_connection'
Tells the driver to treat [MEDIUM/LONG]BLOB
columns as [LONG]VARCHAR columns holding
text encoded in UTF-8 that has characters outside
the BMP (4-byte encodings), which MySQL server
can't handle natively.
When "useBlobToStoreUTF8OutsideBMP"
is set to "true", column names matching the
given regex will still be treated as BLOBs
unless they match the regex specified for
"utf8OutsideBmpIncludedColumnNamePattern".
The regex must follow the patterns used for the
java.util.regex package.
Used to specify exclusion rules to
"utf8OutsideBmpExcludedColumnNamePattern".
2065
100 5.0.5
false 3.1.2
false 5.0.7
Default Since
Value Version
true 1.1g
1.1g
3.0.13
5.1.25
3.0.13
false 5.1.3
5.1.3
5.1.3