List:Commits« Previous MessageNext Message »
From:mcbrown Date:December 4 2006 2:01pm
Subject:svn commit - mysqldoc@docsrva: r4103 - in trunk: refman-5.0 refman-5.1 refman-common
View as plain text  
Author: mcbrown
Date: 2006-12-04 15:01:01 +0100 (Mon, 04 Dec 2006)
New Revision: 4103

Log:
Documenting bugs: #24565, #20650, #23207 (plus manual updates)



Modified:
   trunk/refman-5.0/connector-j.xml
   trunk/refman-5.1/connector-j.xml
   trunk/refman-common/news-connector-j.xml
   trunk/refman-common/news-connector-net.xml


Modified: trunk/refman-5.0/connector-j.xml
===================================================================
--- trunk/refman-5.0/connector-j.xml	2006-12-04 13:06:06 UTC (rev 4102)
+++ trunk/refman-5.0/connector-j.xml	2006-12-04 14:01:01 UTC (rev 4103)
Changed blocks: 10, Lines Added: 37, Lines Deleted: 13; 3867 bytes

@@ -2122,7 +2122,7 @@
 
         <listitem>
           <para>
-            Blob
+            <emphasis role="bold">Blob</emphasis>
           </para>
 
           <para>

@@ -2155,7 +2155,7 @@
 
         <listitem>
           <para>
-            CallableStatement
+            <emphasis role="bold">CallableStatement</emphasis>
           </para>
 
           <para>

@@ -2170,7 +2170,7 @@
 
         <listitem>
           <para>
-            Clob
+            <emphasis role="bold">Clob</emphasis>
           </para>
 
           <para>

@@ -2186,7 +2186,7 @@
 
         <listitem>
           <para>
-            Connection
+            <emphasis role="bold">Connection</emphasis>
           </para>
 
           <para>

@@ -2204,7 +2204,7 @@
 
         <listitem>
           <para>
-            DatabaseMetaData
+            <emphasis role="bold">DatabaseMetaData</emphasis>
           </para>
 
           <para>

@@ -2220,7 +2220,7 @@
 
         <listitem>
           <para>
-            PreparedStatement
+            <emphasis role="bold">PreparedStatement</emphasis>
           </para>
 
           <para>

@@ -2307,7 +2307,7 @@
 
         <listitem>
           <para>
-            ResultSet
+            <emphasis role="bold">ResultSet</emphasis>
           </para>
 
           <para>

@@ -2326,8 +2326,7 @@
             instance in the following manner:
           </para>
 
-<programlisting>
-stmt = conn.createStatement(java.sql.ResultSet.TYPE_FORWARD_ONLY,
+<programlisting>stmt = conn.createStatement(java.sql.ResultSet.TYPE_FORWARD_ONLY,
               java.sql.ResultSet.CONCUR_READ_ONLY);
 stmt.setFetchSize(Integer.MIN_VALUE);</programlisting>
 

@@ -2372,7 +2371,7 @@
 
         <listitem>
           <para>
-            ResultSetMetaData
+            <emphasis role="bold">ResultSetMetaData</emphasis>
           </para>
 
           <para>

@@ -2383,17 +2382,42 @@
 
         <listitem>
           <para>
-            Statement
+            <emphasis role="bold">Statement</emphasis>
           </para>
 
           <para>
             When using versions of the JDBC driver earlier than 3.2.1,
             and connected to server versions earlier than 5.0.3, the
-            "setFetchSize()" method has no effect, other than to toggle
-            result set streaming as described above.
+            <literal>setFetchSize()</literal> method has no effect,
+            other than to toggle result set streaming as described
+            above.
           </para>
 
           <para>
+            Connector/J 5.0.0 and later include the support for both
+            <literal>Statement.cancel()</literal> and
+            <literal>Statement.setQueryTimeout()</literal>. Both require
+            MySQL 5.0.0 or newer server, and require a separate
+            connection to issue the <literal>KILL QUERY</literal>
+            statement. In the case of
+            <literal>setQueryTimeout()</literal>, the implementation
+            creates an additional thread to handle the timeout
+            functionality.
+          </para>
+
+          <note>
+            <para>
+              Failures to cancel the statement for
+              <literal>setQueryTimeout()</literal> may manifest
+              themselves as <literal>RuntimeException</literal> rather
+              than failing silently, as there is currently no way to
+              unblock the thread that is executing the query being
+              cancelled due to timeout expiration and have it throw the
+              exception instead.
+            </para>
+          </note>
+
+          <para>
             MySQL does not support SQL cursors, and the JDBC driver
             doesn't emulate them, so "setCursorName()" has no effect.
           </para>


Modified: trunk/refman-5.1/connector-j.xml
===================================================================
--- trunk/refman-5.1/connector-j.xml	2006-12-04 13:06:06 UTC (rev 4102)
+++ trunk/refman-5.1/connector-j.xml	2006-12-04 14:01:01 UTC (rev 4103)
Changed blocks: 8, Lines Added: 35, Lines Deleted: 10; 3312 bytes

@@ -2122,7 +2122,7 @@
 
         <listitem>
           <para>
-            Blob
+            <emphasis role="bold">Blob</emphasis>
           </para>
 
           <para>

@@ -2155,7 +2155,7 @@
 
         <listitem>
           <para>
-            CallableStatement
+            <emphasis role="bold">CallableStatement</emphasis>
           </para>
 
           <para>

@@ -2170,7 +2170,7 @@
 
         <listitem>
           <para>
-            Clob
+            <emphasis role="bold">Clob</emphasis>
           </para>
 
           <para>

@@ -2186,7 +2186,7 @@
 
         <listitem>
           <para>
-            Connection
+            <emphasis role="bold">Connection</emphasis>
           </para>
 
           <para>

@@ -2204,7 +2204,7 @@
 
         <listitem>
           <para>
-            DatabaseMetaData
+            <emphasis role="bold">DatabaseMetaData</emphasis>
           </para>
 
           <para>

@@ -2307,7 +2307,7 @@
 
         <listitem>
           <para>
-            ResultSet
+            <emphasis role="bold">ResultSet</emphasis>
           </para>
 
           <para>

@@ -2372,7 +2372,7 @@
 
         <listitem>
           <para>
-            ResultSetMetaData
+            <emphasis role="bold">ResultSetMetaData</emphasis>
           </para>
 
           <para>

@@ -2383,17 +2383,42 @@
 
         <listitem>
           <para>
-            Statement
+            <emphasis role="bold">Statement</emphasis>
           </para>
 
           <para>
             When using versions of the JDBC driver earlier than 3.2.1,
             and connected to server versions earlier than 5.0.3, the
-            "setFetchSize()" method has no effect, other than to toggle
-            result set streaming as described above.
+            <literal>setFetchSize()</literal> method has no effect,
+            other than to toggle result set streaming as described
+            above.
           </para>
 
           <para>
+            Connector/J 5.0.0 and later include support for
+            <literal>Statement.cancel()</literal> and
+            <literal>Statement.setQueryTimeout()</literal>. Both require
+            MySQL 5.0.0 or newer server, and require a separate
+            connection to issue the <literal>KILL QUERY</literal>
+            statement. In the case of
+            <literal>setQueryTimeout()</literal>, the implementation
+            creates an additional thread to handle the timeout
+            functionality.
+          </para>
+
+          <note>
+            <para>
+              Failures to cancel the statement for
+              <literal>setQueryTimeout()</literal> may manifest
+              themselves as <literal>RuntimeException</literal> rather
+              than failing silently, as there is currently no way to
+              unblock the thread that is executing the query being
+              cancelled due to timeout expiration and have it throw the
+              exception instead.
+            </para>
+          </note>
+
+          <para>
             MySQL does not support SQL cursors, and the JDBC driver
             doesn't emulate them, so "setCursorName()" has no effect.
           </para>


Modified: trunk/refman-common/news-connector-j.xml
===================================================================
--- trunk/refman-common/news-connector-j.xml	2006-12-04 13:06:06 UTC (rev 4102)
+++ trunk/refman-common/news-connector-j.xml	2006-12-04 14:01:01 UTC (rev 4103)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 754 bytes

@@ -226,6 +226,18 @@
 
       </itemizedlist>
 
+<para>Bugs fixed:</para>
+
+<itemizedlist>
+  <listitem><para>If the connection to the server has been closed due to a
+    server failure, then the cleanup process will call <literal>
+    Statement.cancel()</literal>, triggering a
+    <literal>NullPointerException</literal>, even though there is no active
+    connection.  (Bug
+    #20650)</para></listitem>
+</itemizedlist>
+      
+      
     </section>
 
     <section id="cj-news-5-0-2">


Modified: trunk/refman-common/news-connector-net.xml
===================================================================
--- trunk/refman-common/news-connector-net.xml	2006-12-04 13:06:06 UTC (rev 4102)
+++ trunk/refman-common/news-connector-net.xml	2006-12-04 14:01:01 UTC (rev 4103)
Changed blocks: 2, Lines Added: 23, Lines Deleted: 2; 1631 bytes

@@ -12,9 +12,25 @@
 
   <title>&connector_net; Change History</title>
 
+<section id="connector-net-news-5.0.3">
+  <title>Changes in MySQL Connector/NET Version 5.0.3 (Not yet release</title>
+  
+  <para>Bugs fixed:</para>
+  
+  <itemizedlist>
+    <listitem><para>When using a <literal>DbNull.Value</literal> as the value
+      for a parameter
+      value, and then later setting a specific value type, the command would fail
+    with an exception because the wrong type was implied from the
+      <literal>DbNull.Value</literal>. (Bug #24565)</para></listitem>
+  </itemizedlist>
+  
+  
+  </section>
+
   <section id="connector-net-news-5.0.2">
 
-    <title>Changes in MySQL Connector/NET Version 5.0.2 (6 November 2006))</title>
+    <title>Changes in MySQL Connector/NET Version 5.0.2 (6 November 2006)</title>
 
     <para>
       <emphasis role="bold">Important change:</emphasis> Due to a number

@@ -399,7 +415,12 @@
       Bugs fixed:
     </para>
 
-    <itemizedlist>
+      <itemizedlist>
+        <listitem><para>When using a <literal>DbNull.Value</literal> as the value
+          for a parameter
+          value, and then later setting a specific value type, the command would fail
+          with an exception because the wrong type was implied from the
+          <literal>DbNull.Value</literal>. (Bug #24565)</para></listitem>
 
       <listitem>
         <para>


Thread
svn commit - mysqldoc@docsrva: r4103 - in trunk: refman-5.0 refman-5.1 refman-commonmcbrown4 Dec