Author: mcbrown
Date: 2007-08-30 09:06:03 +0200 (Thu, 30 Aug 2007)
New Revision: 7598
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 2007-08-30 05:00:47 UTC (rev 7597)
+++ trunk/refman-common/connector-j-connprops.xml 2007-08-30 07:06:03 UTC (rev 7598)
Changed blocks: 6, Lines Added: 20, Lines Deleted: 4; 3719 bytes
@@ -565,7 +565,7 @@
<entry>loadBalanceStrategy</entry>
<entry>If using a load-balanced connection to connect to SQL nodes in a MySQL
Cluster/NDB configuration (by using the URL prefix
- "jdbc:mysql:loadbalance://"), which load balancin
+ "jdbc:mysql:loadbalance://"), which load balancing
algorithm should the driver use: (1) "random" - the
driver will pick a random host for each request. This
tends to work better than round-robin, as the randomness
@@ -599,7 +599,7 @@
advantage of this rewrite option, and that if you don't
specify stream lengths when using
PreparedStatement.set*Stream(), the driver won't be able
- to determine the optimium number of parameters per batch
+ to determine the optimum number of parameters per batch
and you might receive an error from the driver that the
resultant packet is too large.
Statement.getGeneratedKeys() for these rewritten
@@ -628,7 +628,7 @@
</row>
<row>
<entry>useFastDateParsing</entry>
- <entry>Use internal String->Date/Time/Teimstamp conversion routines to avoid
+ <entry>Use internal String->Date/Time/Timestamp conversion routines to avoid
excessive object creation?</entry>
<entry>true</entry>
<entry>5.0.5</entry>
@@ -970,6 +970,14 @@
<entry>3.1.5</entry>
</row>
<row>
+ <entry>blobsAreStrings</entry>
+ <entry>Should the driver always treat BLOBs as Strings - specifically to work
+ around dubious metadata returned by the server for GROUP
+ BY clauses?</entry>
+ <entry>false</entry>
+ <entry>5.0.8</entry>
+ </row>
+ <row>
<entry>capitalizeTypeNames</entry>
<entry>Capitalize type names in DatabaseMetaData? (usually only useful when
using WebObjects, true/false, defaults to 'false')</entry>
@@ -1042,6 +1050,14 @@
<entry>3.1.7</entry>
</row>
<row>
+ <entry>functionsNeverReturnBlobs</entry>
+ <entry>Should the driver always treat data from functions returning BLOBs as
+ Strings - specifically to work around dubious metadata
+ returned by the server for GROUP BY clauses?</entry>
+ <entry>false</entry>
+ <entry>5.0.8</entry>
+ </row>
+ <row>
<entry>generateSimpleParameterMetadata</entry>
<entry>Should the driver generate simplified parameter metadata for
PreparedStatements when no metadata is available either
@@ -1166,7 +1182,7 @@
<row>
<entry>populateInsertRowWithDefaultValues</entry>
<entry>When using ResultSets that are CONCUR_UPDATABLE, should the driver
- pre-poulate the "insert" row with default values from
+ 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
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7598 - trunk/refman-common | mcbrown | 30 Aug |
