svn commit - mysqldoc@docsrva: r9545 - trunk/dynamic-docs/changelog

[mcbrown]

Author: mcbrown
Date: 2008-01-10 10:35:22 +0100 (Thu, 10 Jan 2008)
New Revision: 9545

Log:
Documenting ODBC bugs: 

Bug #28617
Bug #10128
Bug #33130
Bug #19923



Modified:
   trunk/dynamic-docs/changelog/connector-odbc.xml


Modified: trunk/dynamic-docs/changelog/connector-odbc.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-odbc.xml	2008-01-10 08:47:33 UTC (rev 9544)
+++ trunk/dynamic-docs/changelog/connector-odbc.xml	2008-01-10 09:35:22 UTC (rev 9545)
Changed blocks: 1, Lines Added: 105, Lines Deleted: 0; 2245 bytes

@@ -5,6 +5,111 @@
   <logentry entrytype="bug">
 
     <bugs>
+      <fixes bugid="28617"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Reading a <literal>TEXT</literal> column that had been used to
+        store UTF8 data would result in the wrong information being
+        returned during a query.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="10128"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        Evaluating a simple numeric expression when using the OLEDB for
+        ODBC provider and ADO would return an error, instead of the
+        result.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="33130"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <function>SQLGetInfo()</function> reported characters for
+        <literal>SQL_SPECIAL_CHARACTERS</literal> that were not encoded
+        correctly.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
+      <fixes bugid="19923"/>
+    </bugs>
+
+    <versions>
+      <version ver="5.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        <literal>SQLForeignKeys</literal> would return an empty string
+        for the schema columns instead of <literal>NULL</literal>.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="feature">
+
+    <versions>
+      <version ver="5.1.2"/>
+    </versions>
+
+    <message>
+
+      <para>
+        A full implementation of SQLForeignKeys based on the information
+        available from INFORMATION_SCHEMA in 5.0 and later versions of
+        the server has been implemented.
+      </para>
+
+    </message>
+
+  </logentry>
+
+  <logentry entrytype="bug">
+
+    <bugs>
       <fixes bugid="31165"/>
     </bugs>