List:Commits« Previous MessageNext Message »
From:martin.brown Date:January 20 2010 11:09am
Subject:svn commit - mysqldoc@docsrva: r18716 - trunk/refman-common
View as plain text  
Author: docauto
Date: 2010-01-20 12:09:08 +0100 (Wed, 20 Jan 2010)
New Revision: 18716

Log:
Automatic update from connector-j

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


Modified: trunk/refman-common/connector-j-connprops.xml
===================================================================
--- trunk/refman-common/connector-j-connprops.xml	2010-01-20 11:08:10 UTC (rev 18715)
+++ trunk/refman-common/connector-j-connprops.xml	2010-01-20 11:09:08 UTC (rev 18716)
Changed blocks: 2, Lines Added: 15, Lines Deleted: 10; 2642 bytes

@@ -642,8 +642,8 @@
             </row>
             <row>
               <entry>holdResultsOpenOverStatementClose</entry>
-              <entry>Should the driver close result sets on Statement.close() as required by
-                the JDBC specification?</entry>
+              <entry>Should the driver leave the result sets open on Statement.close()
+                (enabling violates JDBC specification)</entry>
               <entry>false</entry>
               <entry>3.1.7</entry>
             </row>

@@ -981,20 +981,25 @@
             </row>
             <row>
               <entry>useUnicode</entry>
-              <entry>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'</entry>
+              <entry>Forces the driver to use Unicode character encodings. Should only be set
+                to false either when the driver can't determine the
+                character set mapping (in which case, specify the Java
+                character encoding in the characterEncoding property),
+                or you are trying to force the driver to use a character
+                set that MySQL doesn't natively support. Should be
+                'true' for all versions of MySQL 4.1 or higher unless
+                you are trying to emulate the character set handling
+                support provided in MySQL 4.0. Value is true/false,
+                defaults to 'true'</entry>
               <entry>true</entry>
               <entry>1.1g</entry>
             </row>
             <row>
               <entry>characterEncoding</entry>
-              <entry>If 'useUnicode' is set to true, what character encoding should the
+              <entry>If 'useUnicode' is set to true, what Java character encoding should the
                 driver use when dealing with strings? (defaults is to
-                'autodetect')</entry>
+                'autodetect'). If the encoding cannot be determined,
+                then an exception will be raised.</entry>
               <entry/>
               <entry>1.1g</entry>
             </row>


Thread
svn commit - mysqldoc@docsrva: r18716 - trunk/refman-commonmartin.brown20 Jan