Author: mcbrown
Date: 2007-08-03 12:21:04 +0200 (Fri, 03 Aug 2007)
New Revision: 7322
Log:
Documenting Dev Bugs:
Bug #9927
Bug #27862
Bug #19345
Bug #6741
Bug #7445
Modified:
trunk/refman-common/connector-odbc.xml
trunk/refman-common/mysql-proxy.xml
trunk/refman-common/news-connector-odbc.xml
Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml 2007-08-03 02:39:35 UTC (rev 7321)
+++ trunk/refman-common/connector-odbc.xml 2007-08-03 10:21:04 UTC (rev 7322)
Changed blocks: 4, Lines Added: 44, Lines Deleted: 12; 3096 bytes
@@ -138,24 +138,23 @@
<xref linkend="myodbc-support"/>.
</para>
</listitem>
-
- </itemizedlist>
-
+
+ </itemizedlist>
+
<formalpara role="mnmas-kb">
-
+
<title>MySQL Enterprise</title>
-
+
<para>
MySQL Enterprise subscribers will find more information
about MySQL and ODBC in the Knowledge Base articles about
<ulink url="https://kb.mysql.com/search.php?cat=search&category=9">
- ODBC</ulink>. Access to the MySQL
- Knowledge Base collection of articles is one of the
- advantages of subscribing to MySQL Enterprise. For more
- information see
+ ODBC</ulink>. Access to the MySQL Knowledge Base collection of
+ articles is one of the advantages of subscribing to MySQL
+ Enterprise. For more information see
<ulink url="&base-url-enterprise;advisors.html"/>.
</para>
-
+
</formalpara>
<section id="myodbc-introduction">
@@ -3627,7 +3626,8 @@
<literal>XXXX-01-01</literal>. This resolves an issue
where some statement swill not work because the date
returned and the minimumd ODBC date value are
- incompatible.</entry>
+ incompatible.This option was enabled in Connector/ODBC
+ 3.5.17.</entry>
</row>
<row>
<entry>33554432</entry>
@@ -3637,8 +3637,15 @@
(<literal>XXXX-00-00</literal>). This resolves an issue
where some statement swill not work because the date
returned and the minimumd ODBC date value are
- incompatible.</entry>
+ incompatible. This option was enabled in Connector/ODBC
+ 3.5.17.</entry>
</row>
+ <row>
+ <entry>67108864</entry>
+ <entry>Allow multiple statements</entry>
+ <entry>Enables support for batched statements. This option was enabled in
+ Connector/ODBC 3.5.18.</entry>
+ </row>
</tbody>
</tgroup>
</informaltable>
@@ -8833,6 +8840,31 @@
</qandaentry>
+ <qandaentry>
+
+ <question>
+
+ <para>
+ When I try to use batched statements, the excution of the
+ batched statements fails.
+ </para>
+
+ </question>
+
+ <answer>
+
+ <para>
+ Batched statement support was added in 3.51.18. Support
+ for batched statements is not enabled by default. You must
+ enable option <literal>FLAG_MULTI_STATEMENTS</literal>,
+ value 67108864, or select the <guilabel>Allow multiple
+ statements</guilabel> flag within a GUI configuration.
+ </para>
+
+ </answer>
+
+ </qandaentry>
+
</qandaset>
</section>
Modified: trunk/refman-common/mysql-proxy.xml
===================================================================
--- trunk/refman-common/mysql-proxy.xml 2007-08-03 02:39:35 UTC (rev 7321)
+++ trunk/refman-common/mysql-proxy.xml 2007-08-03 10:21:04 UTC (rev 7322)
Changed blocks: 1, Lines Added: 2, Lines Deleted: 4; 425 bytes
@@ -1395,9 +1395,7 @@
<title>Using MySQL Proxy for Query Profiling</title>
</section>
- -->
- </section>
- <!--/section-->
-
+-->
+ </section>
</chapter>
Modified: trunk/refman-common/news-connector-odbc.xml
===================================================================
--- trunk/refman-common/news-connector-odbc.xml 2007-08-03 02:39:35 UTC (rev 7321)
+++ trunk/refman-common/news-connector-odbc.xml 2007-08-03 10:21:04 UTC (rev 7322)
Changed blocks: 2, Lines Added: 56, Lines Deleted: 0; 2634 bytes
@@ -874,6 +874,27 @@
<listitem>
<para>
+ Connector/ODBC now supports batched statements. In order to
+ enable catched statement support you must switch enable the
+ batched statement option
+ (<literal>FLAG_MULTI_STATEMENTS</literal>, 67108864, or
+ <guilabel>Allow multiple statements</guilabel> within a GUI
+ configuration). Be aware that batched statements create an
+ increased chance of SQL injection attacks and you must ensure
+ that your application protects against this scenario. (Bug
+ #7445)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>SQL_ATTR_ROW_BIND_OFFSET_PTR</literal> is now
+ supported for row bind offsets. (Bug #6741)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
When connecting to a specific database using the DSN, the
system tables from the <literal>mysql</literal> database are
no longer also available. (Bug #28662)
@@ -891,8 +912,43 @@
</para>
</listitem>
+ </itemizedlist>
+
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
<listitem>
<para>
+ Obtaining the length of a column when using a character set
+ for the connection of <literal>utf8</literal> would result in
+ the length being returned incorrectly. (Bug #19345)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>SQL_COLUMN_TYPE</literal>,
+ <literal>SQL_COLUMN_DISPLAY</literal> and
+ <literal>SQL_COLUMN_PRECISION</literal> values would be
+ returned incorrectly when accessing character columns,
+ especially those generated through
+ <function>concat()</function>. (Bug #27862)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When using a table with multiple <literal>TIMESTAMP</literal>
+ columns, the final <literal>TIMESTAMP</literal> column within
+ the table definition would not be updateable. (Bug #9927)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Fixed an issue where the <command>myodbc3i</command> would
update the the user ODBC configuration file
(<filename>~/Library/ODBC/odbcinst.ini</filename>) instead of
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7322 - trunk/refman-common | mcbrown | 3 Aug |
