List:Commits« Previous MessageNext Message »
From:mcbrown Date:September 14 2007 2:00pm
Subject:svn commit - mysqldoc@docsrva: r7857 - trunk/refman-common
View as plain text  
Author: mcbrown
Date: 2007-09-14 14:00:51 +0200 (Fri, 14 Sep 2007)
New Revision: 7857

Log:
Some miscellaneous fixes, FAQ entries and corrections from the inbox.



Modified:
   trunk/refman-common/connector-net.xml
   trunk/refman-common/connector-odbc.xml


Modified: trunk/refman-common/connector-net.xml
===================================================================
--- trunk/refman-common/connector-net.xml	2007-09-14 10:35:06 UTC (rev 7856)
+++ trunk/refman-common/connector-net.xml	2007-09-14 12:00:51 UTC (rev 7857)
Changed blocks: 1, Lines Added: 12, Lines Deleted: 0; 964 bytes

@@ -5883,6 +5883,18 @@
         <literal>MySqlTransaction</literal> object.
       </para>
 
+      <note>
+        <para>
+          Once you have started a transaction on a connection all
+          subsequent commands on that connection are applied within the
+          scope of the transaction. You cannot execute an SQL statement
+          on the same connection outside of the transaction scope. If
+          you need to do this while executing statements that are part
+          of a transaction, open a second a connection to be used for
+          execution the non-transaction statements.
+        </para>
+      </note>
+
       <para>
         <emphasis role="bold">Examples</emphasis>
       </para>


Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml	2007-09-14 10:35:06 UTC (rev 7856)
+++ trunk/refman-common/connector-odbc.xml	2007-09-14 12:00:51 UTC (rev 7857)
Changed blocks: 1, Lines Added: 57, Lines Deleted: 0; 2029 bytes

@@ -9014,6 +9014,63 @@
 
         </qandaentry>
 
+        <qandaentry>
+
+          <question>
+
+            <para>
+              When connecting to a MySQL server using ADODB and Excel,
+              occasionally the application fails to communicate with the
+              server and the error <literal>Got an error reading
+              communication packets</literal> appears in the error log.
+            </para>
+
+          </question>
+
+          <answer>
+
+            <para>
+              This error may be related to Keyboard Logger 1.1 from
+              PanteraSoft.com, which is known to interfere with the
+              network communication between MySQL Connector/ODBC and
+              MySQL.
+            </para>
+
+          </answer>
+
+        </qandaentry>
+
+        <qandaentry>
+
+          <question>
+
+            <para>
+              When using some applications to access a MySQL server
+              using C/ODBC and outer joins, an error is reported
+              regarding the Outer Join Escape Sequence.
+            </para>
+
+          </question>
+
+          <answer>
+
+            <para>
+              This is a known issue with MySQL Connector/ODBC which is
+              not correctly parsing the "Outer Join Escape Sequence", as
+              per the specs at
+              <ulink
+            url="http://msdn2.microsoft.com/en-us/library/ms710299.aspx">Microsoft
+              ODBC Specs</ulink>. Currently, Connector/ODBC will return
+              value > 0 when asked for
+              <literal>SQL_OJ_CAPABILITIES</literal> even though no
+              parsing takes place in the driver to handle the outer join
+              escape sequence.
+            </para>
+
+          </answer>
+
+        </qandaentry>
+
       </qandaset>
 
     </section>


Thread
svn commit - mysqldoc@docsrva: r7857 - trunk/refman-commonmcbrown14 Sep