Author: mcbrown
Date: 2007-08-07 06:45:13 +0200 (Tue, 07 Aug 2007)
New Revision: 7354
Log:
Syncing release notes for 3.51.18 release
Added FLAG* option names to the options table to make references to these flags clearer
Dev Bugs document:
Bug #14407
Bug #14414
Modified:
trunk/refman-common/connector-odbc.xml
trunk/refman-common/news-connector-odbc.xml
Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml 2007-08-07 04:36:13 UTC (rev 7353)
+++ trunk/refman-common/connector-odbc.xml 2007-08-07 04:45:13 UTC (rev 7354)
Changed blocks: 17, Lines Added: 50, Lines Deleted: 32; 12602 bytes
@@ -146,8 +146,8 @@
<title>MySQL Enterprise</title>
<para>
- MySQL Enterprise subscribers will find more information
- about MySQL and ODBC in the Knowledge Base articles about
+ 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
@@ -3447,24 +3447,28 @@
</para>
<informaltable>
- <tgroup cols="3">
+ <tgroup cols="4">
<colspec colwidth="10*"/>
- <colspec colwidth="30*"/>
- <colspec colwidth="60*"/>
+ <colspec colwidth="20*"/>
+ <colspec colwidth="20*"/>
+ <colspec colwidth="50*"/>
<tbody>
<row>
<entry><emphasis role="bold">Value</emphasis></entry>
- <entry><emphasis role="bold">Windows Checkbox</emphasis></entry>
+ <entry><emphasis role="bold">Flagname</emphasis></entry>
+ <entry><emphasis role="bold">GUI Option</emphasis></entry>
<entry><emphasis role="bold">Description</emphasis></entry>
</row>
<row>
<entry>1</entry>
- <entry>Don't Optimized Column Width</entry>
+ <entry><literal>FLAG_FIELD_LENGTH</literal></entry>
+ <entry>Don't Optimize Column Width</entry>
<entry>The client can't handle that Connector/ODBC returns the real width of a
column.</entry>
</row>
<row>
<entry>2</entry>
+ <entry><literal>FLAG_FOUND_ROWS</literal></entry>
<entry>Return Matching Rows</entry>
<entry>The client can't handle that MySQL returns the true value of affected
rows. If this flag is set, MySQL returns <quote>found
@@ -3473,60 +3477,71 @@
</row>
<row>
<entry>4</entry>
+ <entry><literal>FLAG_DEBUG</literal></entry>
<entry>Trace Driver Calls To myodbc.log</entry>
<entry>Make a debug log in <filename>C:\myodbc.log</filename> on Windows, or
<filename>/tmp/myodbc.log</filename> on Unix variants.</entry>
</row>
<row>
<entry>8</entry>
+ <entry><literal>FLAG_BIG_PACKETS</literal></entry>
<entry>Allow Big Results</entry>
<entry>Don't set any packet limit for results and parameters.</entry>
</row>
<row>
<entry>16</entry>
+ <entry><literal>FLAG_NO_PROMPT</literal></entry>
<entry>Don't Prompt Upon Connect</entry>
<entry>Don't prompt for questions even if driver would like to prompt.</entry>
</row>
<row>
<entry>32</entry>
+ <entry><literal>FLAG_DYNAMIC_CURSOR</literal></entry>
<entry>Enable Dynamic Cursor</entry>
<entry>Enable or disable the dynamic cursor support. (Not allowed in
Connector/ODBC 2.50.)</entry>
</row>
<row>
<entry>64</entry>
+ <entry><literal>FLAG_NO_SCHEMA</literal></entry>
<entry>Ignore # in Table Name</entry>
<entry>Ignore use of database name in
<literal>db_name.tbl_name.col_name</literal>.</entry>
</row>
<row>
<entry>128</entry>
+ <entry><literal>FLAG_NO_DEFAULT_CURSOR</literal></entry>
<entry>User Manager Cursors</entry>
<entry>Force use of ODBC manager cursors (experimental).</entry>
</row>
<row>
<entry>256</entry>
+ <entry><literal>FLAG_NO_LOCALE</literal></entry>
<entry>Don't Use Set Locale</entry>
<entry>Disable the use of extended fetch (experimental).</entry>
</row>
<row>
<entry>512</entry>
+ <entry><literal>FLAG_PAD_SPACE</literal></entry>
<entry>Pad Char To Full Length</entry>
<entry>Pad <literal>CHAR</literal> columns to full column length.</entry>
</row>
<row>
<entry>1024</entry>
+ <entry><literal>FLAG_FULL_COLUMN_NAMES</literal></entry>
<entry>Return Table Names for SQLDescribeCol</entry>
<entry><literal>SQLDescribeCol()</literal> returns fully qualified column
names.</entry>
</row>
<row>
<entry>2048</entry>
+ <entry><literal>FLAG_COMPRESSED_PROTO</literal></entry>
<entry>Use Compressed Protocol</entry>
<entry>Use the compressed client/server protocol.</entry>
</row>
<row>
<entry>4096</entry>
+ <entry><literal>FLAG_IGNORE_SPACE</literal></entry>
<entry>Ignore Space After Function Names</entry>
<entry>Tell server to ignore space after function name and before
‘<literal>(</literal>’ (needed by
@@ -3534,12 +3549,14 @@
</row>
<row>
<entry>8192</entry>
+ <entry><literal>FLAG_NAMED_PIPE</literal></entry>
<entry>Force Use of Named Pipes</entry>
<entry>Connect with named pipes to a <command>mysqld</command> server running
on NT.</entry>
</row>
<row>
<entry>16384</entry>
+ <entry><literal>FLAG_NO_BIGINT</literal></entry>
<entry>Change BIGINT Columns to Int</entry>
<entry>Change <literal>BIGINT</literal> columns to <literal>INT</literal>
columns (some applications can't handle
@@ -3547,6 +3564,7 @@
</row>
<row>
<entry>32768</entry>
+ <entry><literal>FLAG_NO_CATALOG</literal></entry>
<entry>No Catalog</entry>
<entry>Forces results from the catalog functions, such as
<literal>SQLTables</literal>, to always return
@@ -3555,6 +3573,7 @@
</row>
<row>
<entry>65536</entry>
+ <entry><literal>FLAG_USE_MYCNF</literal></entry>
<entry>Read Options From <literal>my.cnf</literal></entry>
<entry>Read parameters from the <literal>[client]</literal> and
<literal>[odbc]</literal> groups from
@@ -3562,16 +3581,19 @@
</row>
<row>
<entry>131072</entry>
+ <entry><literal>FLAG_SAFE</literal></entry>
<entry>Safe</entry>
- <entry>Add some extra safety checks (should not be needed but...).</entry>
+ <entry>Add some extra safety checks.</entry>
</row>
<row>
<entry>262144</entry>
- <entry>Disable transaction</entry>
+ <entry><literal>FLAG_NO_TRANSACTIONS</literal></entry>
+ <entry>Disable transactions</entry>
<entry>Disable transactions.</entry>
</row>
<row>
<entry>524288</entry>
+ <entry><literal>FLAG_LOG_QUERY</literal></entry>
<entry>Save queries to <filename>myodbc.sql</filename></entry>
<entry>Enable query logging to
<filename>c:\myodbc.sql</filename>(<filename>/tmp/myodbc.sql</filename>)
@@ -3579,6 +3601,7 @@
</row>
<row>
<entry>1048576</entry>
+ <entry><literal>FLAG_NO_CACHE</literal></entry>
<entry>Don't Cache Result (forward only cursors)</entry>
<entry>Do not cache the results locally in the driver, instead read from server
(<literal>mysql_use_result()</literal>). This works only
@@ -3588,6 +3611,7 @@
</row>
<row>
<entry>2097152</entry>
+ <entry><literal>FLAG_FORWARD_CURSOR</literal></entry>
<entry>Force Use Of Forward Only Cursors</entry>
<entry>Force the use of <literal>Forward-only</literal> cursor type. In case of
applications setting the default static/dynamic cursor
@@ -3597,6 +3621,7 @@
</row>
<row>
<entry>4194304</entry>
+ <entry><literal>FLAG_AUTO_RECONNECT</literal></entry>
<entry>Enable auto-reconnect.</entry>
<entry>Enables auto-reconnection functionality. You should not use this option
with transactions, since a auto reconnection during a
@@ -3607,6 +3632,7 @@
</row>
<row>
<entry>8388608</entry>
+ <entry><literal>FLAG_AUTO_IS_NULL</literal></entry>
<entry>Flag Auto Is Null</entry>
<entry>When set, this option causes the connection to set the
<literal>SQL_AUTO_IS_NULL</literal> option to 1. This
@@ -3620,6 +3646,7 @@
</row>
<row>
<entry>16777216</entry>
+ <entry><literal>FLAG_ZERO_DATE_TO_MIN</literal></entry>
<entry>Flag Zero Date to Min</entry>
<entry>Translates zero dates (<literal>XXXX-00-00</literal>) into the minimum
date values supported by ODBC,
@@ -3631,6 +3658,7 @@
</row>
<row>
<entry>33554432</entry>
+ <entry><literal>FLAG_MIN_DATE_TO_ZERO</literal></entry>
<entry>Flag Min Date to Zero</entry>
<entry>Translates the minimum ODBC date value (<literal>XXXX-01-01</literal>)
to the zero date format supported by MySQL
@@ -3642,6 +3670,7 @@
</row>
<row>
<entry>67108864</entry>
+ <entry><literal>FLAG_MULTI_STATEMENTS</literal></entry>
<entry>Allow multiple statements</entry>
<entry>Enables support for batched statements. This option was enabled in
Connector/ODBC 3.5.18.</entry>
@@ -3877,20 +3906,14 @@
<para>
To enable the trace option on Mac OS X 10.3 or later you
should use the <literal>Tracing</literal> tab within
-
- <application>ODBC
- Administrator</application>
-
- .
+ <application>ODBC Administrator</application> .
</para>
<orderedlist>
<listitem>
<para>
- Open the
-
- <application>ODBC Administrator.</application>
+ Open the <application>ODBC Administrator.</application>
</para>
</listitem>
@@ -4835,17 +4858,13 @@
<para>
With both applications, data is accessed and imported into the
- application using
-
- <application>Microsoft Query</application>
-
- , which enables you to execute a query though an ODBC source.
- You use Microsoft Query to build the SQL statement to be
- executed, selecting the tables, fields, selection criteria and
- sort order. For example, to insert information from a table in
- the World test database into an Excel spreadsheet, using the DSN
- samples shown in
- <xref
+ application using <application>Microsoft Query</application> ,
+ which enables you to execute a query though an ODBC source. You
+ use Microsoft Query to build the SQL statement to be executed,
+ selecting the tables, fields, selection criteria and sort order.
+ For example, to insert information from a table in the World
+ test database into an Excel spreadsheet, using the DSN samples
+ shown in <xref
linkend="myodbc-configuration"/>:
</para>
@@ -4867,10 +4886,9 @@
<listitem>
<para>
- <application>Microsoft Query</application>
-
- will start. First, you need to choose the data source, by
- selecting an existing Data Source Name.
+ <application>Microsoft Query</application> will start.
+ First, you need to choose the data source, by selecting an
+ existing Data Source Name.
</para>
<mediaobject>
Modified: trunk/refman-common/news-connector-odbc.xml
===================================================================
--- trunk/refman-common/news-connector-odbc.xml 2007-08-07 04:36:13 UTC (rev 7353)
+++ trunk/refman-common/news-connector-odbc.xml 2007-08-07 04:45:13 UTC (rev 7354)
Changed blocks: 5, Lines Added: 158, Lines Deleted: 6; 7755 bytes
@@ -867,6 +867,51 @@
<title>Changes in Connector/ODBC 3.51.18 (Not yet released)</title>
<para>
+ Platform specific notes:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ A binary package without an installer is available for
+ Microsoft Windows x64 Edition. There are no installer packages
+ for Microsoft Windows x64 Edition.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Binary packages as disk images with installers are now
+ available for Mac OS X.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Binary packages for Sun Solaris are now available as
+ <literal>PKG</literal> packages.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ There is no binary package for Mac OS X on 64-bit PowerPC
+ because Apple does not currently provide a 64-bit PowerPC
+ version of iODBC.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The HP-UX 11.23 IA64 binary package does not include the GUI
+ bits because of problems building Qt on that platform.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ <para>
Functionality added or changed:
</para>
@@ -895,14 +940,25 @@
<listitem>
<para>
- When connecting to a specific database using the DSN, the
+ When connecting to a specific database when using a DSN, the
system tables from the <literal>mysql</literal> database are
- no longer also available. (Bug #28662)
+ no longer also available. Previously, tables from the mysql
+ database (catalog) were listed as <literal>SYSTEM
+ TABLES</literal> by <literal>SQLTables()</literal> even when a
+ different catalog was being queried.(Bug #28662)
</para>
</listitem>
<listitem>
<para>
+ The <literal>TRACE</literal> and <literal>TRACEFILE</literal>
+ DSN options have been removed. Use the ODBC driver manager
+ trace options instead.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Installed for Mac OS X has been re-instated. The installer
registers the driver at a system (not user) level and makes it
possible to create both user and system DSNs using the
@@ -922,6 +978,24 @@
<listitem>
<para>
+ The <literal>SQLColumns()</literal> function could return
+ incorrect information about <literal>AUTO_INCREMENT</literal>
+ columns, indicating that the field was not nullable. (Bug
+ #14407)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>SQLColumns()</literal> function could return
+ incorrect information about <literal>TIMESTAMP</literal>
+ columns, indicating that the field was not nullable. (Bug
+ #14414)
+ </para>
+ </listitem>
+
+ <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)
@@ -933,17 +1007,81 @@
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)
+ returned incorrectly by <literal>SQLColumns()</literal>,
+ <literal>SQLDescribeCol()</literal> and
+ <literal>SQLColAttribute()</literal> when accessing character
+ columns, especially those generated through
+ <function>concat()</function>. The lengths returned should now
+ conform to the ODBC specification. The
+ <literal>FLAG_FIELD_LENGTH</literal> option no longer has any
+ affect on the results returned. (Bug #27862)
</para>
</listitem>
<listitem>
<para>
+ The <literal>SQL_DATA_TYPE</literal> column in
+ <literal>SQLColumns()</literal> results did not report the
+ correct value for date and time types.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The <literal>SQL_DATETIME_SUB</literal> column in SQLColumns()
+ was not correctly set for date and time types.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The value for <literal>SQL_DESC_FIXED_PREC_SCALE</literal> was
+ not returned correctly for values in MySQL 5.0 and later.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The wrong value from
+ <literal>SQL_DESC_LITERAL_SUFFIX</literal> was returned for
+ binary fields.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The wrong value for <literal>SQL_DESC_TYPE</literal> was
+ returned for date and time types.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The wrong value for <literal>DECIMAL_DIGITS</literal> in
+ <literal>SQLColumns()</literal> was reported for
+ <literal>FLOAT</literal> and <literal>DOUBLE</literal> fields,
+ as well as the wrong value for the scale parameter to
+ <literal>SQLDescribeCol()</literal>, and the
+ <literal>SQL_DESC_SCALE</literal> attribute from
+ <literal>SQLColAttribute()</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>BIT(n)</literal> columns are now treated as
+ <literal>SQL_BIT</literal> data where <literal>n = 1</literal>
+ and binary data where <literal>n > 1</literal>.
+ </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)
+ the table definition would not be updateable. Note that there
+ is still a limitation in MySQL server regarding multiple
+ <literal>TIMESTAMP</literal> columns (Bug #30081). (Bug #9927)
</para>
</listitem>
@@ -953,12 +1091,26 @@
update the the user ODBC configuration file
(<filename>~/Library/ODBC/odbcinst.ini</filename>) instead of
the system <filename>/Library/ODBC/odbcinst.ini</filename>.
+ This was caused because <command>myodbc3i</command> was not
+ honouring the <literal>s</literal> and <literal>u</literal>
+ modifiers for the <option>-d</option> command line option.
(Bug #29964)
</para>
</listitem>
<listitem>
<para>
+ <literal>SQLConnect()</literal> and
+ <literal>SQLDriverConnect()</literal> were rewritten to
+ eliminate duplicate code and ensure all options were supported
+ using both connection methods.
+ <literal>SQLDriverConnect()</literal> now only requires the
+ setup library to be present when the call requires it.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Getting table metadata (through the
<literal>SQLColumns()</literal> would fail, returning a bad
table definition to calling applications. (Bug #29888)
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r7354 - trunk/refman-common | mcbrown | 7 Aug |
