List:Commits« Previous MessageNext Message »
From:mcbrown Date:May 14 2007 11:52am
Subject:svn commit - mysqldoc@docsrva: r6437 - trunk/refman-common
View as plain text  
Author: mcbrown
Date: 2007-05-14 13:52:30 +0200 (Mon, 14 May 2007)
New Revision: 6437

Log:
Updating properties table



Modified:
   trunk/refman-common/connector-j.xml


Modified: trunk/refman-common/connector-j.xml
===================================================================
--- trunk/refman-common/connector-j.xml	2007-05-14 06:16:52 UTC (rev 6436)
+++ trunk/refman-common/connector-j.xml	2007-05-14 11:52:30 UTC (rev 6437)
Changed blocks: 5, Lines Added: 60, Lines Deleted: 2; 5477 bytes

@@ -1547,6 +1547,24 @@
                   <entry>3.1.7</entry>
                 </row>
                 <row>
+                  <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
+                    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 will somewhat account for spreading loads
+                    where requests vary in response time, while
+                    round-robin can sometimes lead to overloaded nodes
+                    if there are variations in response times across the
+                    workload. (2) "bestResponseTime" - the driver will
+                    route the request to the host that had the best
+                    response time for the previous transaction.</entry>
+                  <entry>random</entry>
+                  <entry>5.0.6</entry>
+                </row>
+                <row>
                   <entry>locatorFetchBufferSize</entry>
                   <entry>If 'emulateLocators' is configured to 'true', what size buffer should be
                     used when fetching BLOB data for

@@ -1575,6 +1593,19 @@
                   <entry>3.1.13</entry>
                 </row>
                 <row>
+                  <entry>useDynamicCharsetInfo</entry>
+                  <entry>Should the driver use a per-connection cache of character set
+                    information queried from the server when necessary,
+                    or use a built-in static mapping that is more
+                    efficient, but isn't aware of custom character sets
+                    or character sets implemented after the release of
+                    the JDBC driver?(this only affects the
+                    "padCharsWithSpace" configuration property and the
+                    ResultSetMetaData.getColumnDisplayWidth() method).</entry>
+                  <entry>true</entry>
+                  <entry>5.0.6</entry>
+                </row>
+                <row>
                   <entry>useFastDateParsing</entry>
                   <entry>Use internal String-&gt;Date/Time/Teimstamp conversion routines to avoid
                     excessive object creation?</entry>

@@ -1601,8 +1632,11 @@
                   <entry>Should the driver refer to the internal values of autocommit and
                     transaction isolation that are set by
                     Connection.setAutoCommit() and
-                    Connection.setTransactionIsolation(), rather than
-                    querying the database?</entry>
+                    Connection.setTransactionIsolation() and transaction
+                    state as maintained by the protocol, rather than
+                    querying the database or blindly sending commands to
+                    the database for commit() or rollback() method
+                    calls?</entry>
                   <entry>false</entry>
                   <entry>3.1.7</entry>
                 </row>

@@ -2006,6 +2040,15 @@
                   <entry>3.1.12</entry>
                 </row>
                 <row>
+                  <entry>padCharsWithSpace</entry>
+                  <entry>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)?</entry>
+                  <entry>false</entry>
+                  <entry>5.0.6</entry>
+                </row>
+                <row>
                   <entry>pedantic</entry>
                   <entry>Follow the JDBC spec to the letter.</entry>
                   <entry>false</entry>

@@ -2021,6 +2064,21 @@
                   <entry>5.0.1</entry>
                 </row>
                 <row>
+                  <entry>populateInsertRowWithDefaultValues</entry>
+                  <entry>When using ResultSets that are CONCUR_UPDATABLE, should the driver
+                    pre-poulate 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.</entry>
+                  <entry>false</entry>
+                  <entry>5.0.5</entry>
+                </row>
+                <row>
                   <entry>processEscapeCodesForPrepStmts</entry>
                   <entry>Should the driver process escape codes in queries that are prepared?</entry>
                   <entry>true</entry>


Thread
svn commit - mysqldoc@docsrva: r6437 - trunk/refman-commonmcbrown14 May