Author: mcbrown
Date: 2008-04-29 12:42:15 +0200 (Tue, 29 Apr 2008)
New Revision: 10609
Log:
Automatic update from C/J build
Modified:
trunk/refman-common/connector-j-connprops.xml
Modified: trunk/refman-common/connector-j-connprops.xml
===================================================================
--- trunk/refman-common/connector-j-connprops.xml 2008-04-29 02:30:20 UTC (rev 10608)
+++ trunk/refman-common/connector-j-connprops.xml 2008-04-29 10:42:15 UTC (rev 10609)
Changed blocks: 7, Lines Added: 73, Lines Deleted: 20; 7478 bytes
@@ -97,6 +97,12 @@
<entry>5.0.5</entry>
</row>
<row>
+ <entry>mysqlIOFactory</entry>
+ <entry>!ConnectionProperties.mysqlIOFactory!</entry>
+ <entry>com.mysql.jdbc.MysqlIOprotocol</entry>
+ <entry>6.0.0</entry>
+ </row>
+ <row>
<entry>propertiesTransform</entry>
<entry>An implementation of com.mysql.jdbc.ConnectionPropertiesTransform that
the driver will use to modify URL properties passed to
@@ -276,6 +282,24 @@
<entry>3.0.2</entry>
</row>
<row>
+ <entry>selfDestructOnPingMaxOperations</entry>
+ <entry>=If set to a non-zero value, the driver will report close the connection
+ and report failure when Connection.ping() or
+ Connection.isValid(int) is called if the connnection's
+ count of commands sent to the server exceeds this value.</entry>
+ <entry>0</entry>
+ <entry>5.1.6</entry>
+ </row>
+ <row>
+ <entry>selfDestructOnPingSecondsLifetime</entry>
+ <entry>If set to a non-zero value, the driver will report close the connection
+ and report failure when Connection.ping() or
+ Connection.isValid(int) is called if the connnection's
+ lifetime exceeds this value.</entry>
+ <entry>0</entry>
+ <entry>5.1.6</entry>
+ </row>
+ <row>
<entry>resourceId</entry>
<entry>A globally unique name that identifies the resource that this datasource
or connection is connected to, used for
@@ -330,21 +354,18 @@
<entry>3.1.0</entry>
</row>
<row>
- <entry>allowLoadLocalInfile</entry>
- <entry>Should the driver allow use of 'LOAD DATA LOCAL INFILE...' (defaults to
- 'true').</entry>
+ <entry>verifyServerCertificate</entry>
+ <entry>If "useSSL" is set to "true", should the driver verify the server's
+ certificate? When using this feature, the keystore
+ parameters should be specified by the
+ "clientCertificateKeyStore*" properties, rather than
+ system properties.</entry>
<entry>true</entry>
- <entry>3.0.3</entry>
+ <entry>5.1.6</entry>
</row>
<row>
- <entry>allowUrlInLocalInfile</entry>
- <entry>Should the driver allow URLs in 'LOAD DATA LOCAL INFILE' statements?</entry>
- <entry>false</entry>
- <entry>3.1.4</entry>
- </row>
- <row>
- <entry>clientCertificateKeyStorePassword</entry>
- <entry>Password for the client certificates KeyStore</entry>
+ <entry>clientCertificateKeyStoreUrl</entry>
+ <entry>URL to the client certificate KeyStore (if not specified, use defaults)</entry>
<entry/>
<entry>5.1.0</entry>
</row>
@@ -359,14 +380,15 @@
<entry>5.1.0</entry>
</row>
<row>
- <entry>clientCertificateKeyStoreUrl</entry>
- <entry>URL to the client certificate KeyStore (if not specified, use defaults)</entry>
+ <entry>clientCertificateKeyStorePassword</entry>
+ <entry>Password for the client certificates KeyStore</entry>
<entry/>
<entry>5.1.0</entry>
</row>
<row>
- <entry>trustCertificateKeyStorePassword</entry>
- <entry>Password for the trusted root certificates KeyStore</entry>
+ <entry>trustCertificateKeyStoreUrl</entry>
+ <entry>URL to the trusted root certificate KeyStore (if not specified, use
+ defaults)</entry>
<entry/>
<entry>5.1.0</entry>
</row>
@@ -381,13 +403,25 @@
<entry>5.1.0</entry>
</row>
<row>
- <entry>trustCertificateKeyStoreUrl</entry>
- <entry>URL to the trusted root certificate KeyStore (if not specified, use
- defaults)</entry>
+ <entry>trustCertificateKeyStorePassword</entry>
+ <entry>Password for the trusted root certificates KeyStore</entry>
<entry/>
<entry>5.1.0</entry>
</row>
<row>
+ <entry>allowLoadLocalInfile</entry>
+ <entry>Should the driver allow use of 'LOAD DATA LOCAL INFILE...' (defaults to
+ 'true').</entry>
+ <entry>true</entry>
+ <entry>3.0.3</entry>
+ </row>
+ <row>
+ <entry>allowUrlInLocalInfile</entry>
+ <entry>Should the driver allow URLs in 'LOAD DATA LOCAL INFILE' statements?</entry>
+ <entry>false</entry>
+ <entry>3.1.4</entry>
+ </row>
+ <row>
<entry>paranoid</entry>
<entry>Take measures to prevent exposure sensitive information in error
messages and clear data structures holding sensitive
@@ -859,6 +893,14 @@
<entry>5.0.5</entry>
</row>
<row>
+ <entry>profilerEventHandler</entry>
+ <entry>Name of a class that implements the interface
+ com.mysql.jdbc.profiler.ProfilerEventHandler that will
+ be used to handle profiling/tracing events.</entry>
+ <entry>com.mysql.jdbc.profiler.LoggingProfilerEventHandler</entry>
+ <entry>5.1.6</entry>
+ </row>
+ <row>
<entry>resultSetSizeThreshold</entry>
<entry>If the usage advisor is enabled, how many rows should a result set
contain before the driver warns that it is suspiciously
@@ -1354,12 +1396,23 @@
<entry>5.0.0</entry>
</row>
<row>
+ <entry>useLegacyDatetimeCode</entry>
+ <entry>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?</entry>
+ <entry>true</entry>
+ <entry>5.1.6</entry>
+ </row>
+ <row>
<entry>useOldAliasMetadataBehavior</entry>
<entry>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?</entry>
+ original column/table name? In 5.0.x, the default value
+ was true.</entry>
<entry>false</entry>
<entry>5.0.4</entry>
</row>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r10609 - trunk/refman-common | mcbrown | 29 Apr |
