Author: mcbrown
Date: 2007-02-22 15:36:41 +0100 (Thu, 22 Feb 2007)
New Revision: 5023
Log:
Dev Bugs: #23645, #24360, #23304, #24065, #25073, #24434, #25009, #25514, #25836, #21438, #25787, #24840, #24794, #22628, #19823, #26024, #23818, #25379, #25399, #23303, #26326, #21480, #25047, #26430, #26152, #24263, #25605
Checking some inconsistencies in C/J bugs
Modified:
trunk/refman-common/connector-j.xml
trunk/refman-common/connector-net.xml
trunk/refman-common/connector-odbc.xml
trunk/refman-common/news-connector-j.xml
trunk/refman-common/news-connector-net.xml
trunk/refman-common/news-myodbc.xml
Modified: trunk/refman-common/connector-j.xml
===================================================================
--- trunk/refman-common/connector-j.xml 2007-02-22 11:14:33 UTC (rev 5022)
+++ trunk/refman-common/connector-j.xml 2007-02-22 14:36:41 UTC (rev 5023)
Changed blocks: 1, Lines Added: 3, Lines Deleted: 3; 770 bytes
@@ -2518,13 +2518,13 @@
</informaltable>
</para>
</formalpara>
-
+<note>
<para>
- <emphasis role="bold">Note:</emphasis> round-off, overflow or
+ Round-off, overflow or
loss of precision may occur if you choose a Java numeric data
type that has less precision or capacity than the MySQL data
type you are converting to/from.
- </para>
+ </para></note>
<para>
The <classname>ResultSet.getObject()</classname> method uses the
Modified: trunk/refman-common/connector-net.xml
===================================================================
--- trunk/refman-common/connector-net.xml 2007-02-22 11:14:33 UTC (rev 5022)
+++ trunk/refman-common/connector-net.xml 2007-02-22 14:36:41 UTC (rev 5023)
Changed blocks: 7, Lines Added: 30, Lines Deleted: 13; 4747 bytes
@@ -484,7 +484,7 @@
Unix environments where you want to connect to a MySQL server
through the Mono project. If you are deploying or developing on
a different environment such as Java or Perl then you should use
- a more appropriate connectivity component. See the
+ a more appropriate connectivity component. See
<xref linkend="connectors"
/>, or
<xref linkend="apis"/>, for more information.
@@ -573,13 +573,18 @@
use to build Connector/NET.
</para>
+ <remark role="todo">
+ [MC] Need to add more instructions on compiling unix Unix/Linux
+ and Mono
+ </remark>
+
</section>
</section>
<section id="connector-net-examples">
- <title>Connector/NET Examples</title>
+ <title>Connector/NET Examples and Usage Guide</title>
<para>
Connector/NET comprises several classes that are used to connect
@@ -3596,7 +3601,8 @@
<programlisting>public void CreateSqlConnection()
{
MySqlConnection myConnection = new MySqlConnection();
- myConnection.ConnectionString = "Persist Security Info=False;Username=user;Password=pass;database=test1;server=localhost;Connect Timeout=30";
+ myConnection.ConnectionString = "Persist Security Info=False;Username=user;»
+ Password=pass;database=test1;server=localhost;Connect Timeout=30";
myConnection.Open();
}
</programlisting>
@@ -3626,7 +3632,8 @@
typical connection string.
</para>
-<programlisting>"Persist Security Info=False;database=MyDB;server=MySqlServer;user id=myUser;Password=myPass"</programlisting>
+<programlisting>"Persist Security Info=False;database=MyDB;»
+ server=MySqlServer;user id=myUser;Password=myPass"</programlisting>
<para>
The <literal>ConnectionString</literal> property can be set
@@ -3784,12 +3791,12 @@
<entry><literal>Ignore Prepare</literal></entry>
<entry>true</entry>
<entry>When true, instructs the provider to ignore any calls to
- MySqlCommand.Prepare(). This option is provided to
- prevent issues with corruption of the statements when
- use with server side prepared statements. If you want
- to use server-side prepare statements, set this option
- to false. This option was added in Connector/NET
- 5.0.3.</entry>
+ <literal>MySqlCommand.Prepare()</literal>. This option
+ is provided to prevent issues with corruption of the
+ statements when use with server side prepared
+ statements. If you want to use server-side prepare
+ statements, set this option to false. This option was
+ added in Connector/NET 5.0.3 and Connector/NET 1.0.9.</entry>
</row>
<row>
<entry><literal>Port</literal></entry>
@@ -3908,6 +3915,16 @@
applies to the Windows platform.</entry>
</row>
<row>
+ <entry><literal>Procedure Cache</literal></entry>
+ <entry>25</entry>
+ <entry>Sets the size of the stored procedure cache. By default, Connector/NET
+ will store the metadata (input/output datatypes) about
+ the last 25 stored procedures used. To disable the
+ stored procedure cache, set the value to zero (0).
+ This option was added in Connector/NET 5.0.2 and
+ Connector/NET 1.0.9.</entry>
+ </row>
+ <row>
<entry><literal>Use Procedure Bodies</literal></entry>
<entry>true</entry>
<entry>Setting this option to <literal>false</literal> indicates that the user
@@ -3921,9 +3938,9 @@
information, you should explicitly set the types of
the all the parameters before the call and the
parameters should be added to the command in the exact
- same order as they appear in the procedure definition. This
- option was added in Connector/NET 5.0.4 and Connector/NET
- 1.0.10.</entry>
+ same order as they appear in the procedure definition.
+ This option was added in Connector/NET 5.0.4 and
+ Connector/NET 1.0.10.</entry>
</row>
</tbody>
</tgroup>
Modified: trunk/refman-common/connector-odbc.xml
===================================================================
--- trunk/refman-common/connector-odbc.xml 2007-02-22 11:14:33 UTC (rev 5022)
+++ trunk/refman-common/connector-odbc.xml 2007-02-22 14:36:41 UTC (rev 5023)
Changed blocks: 2, Lines Added: 6, Lines Deleted: 6; 1206 bytes
@@ -5678,10 +5678,10 @@
<literal>SQLGetFunctions</literal>.
</para>
- <para>
- Note: For backward compatibility, the Connector/ODBC 3.51 driver
+<note> <para>
+ For backward compatibility, the Connector/ODBC 3.51 driver
supports all deprecated functions.
- </para>
+ </para></note>
<para>
The following tables list Connector/ODBC API calls grouped by
@@ -8194,11 +8194,11 @@
<literal>#DELETED#</literal> in Access.
</para>
- <para>
- Note: If you are using MySQL 3.22, you must apply the
+ <note> <para>
+ If you are using MySQL 3.22, you must apply the
MDAC patch and use MyODBC 2.50.32 or 2.50.34 and up to
work around this problem.
- </para>
+ </para></note>
</listitem>
<listitem>
Modified: trunk/refman-common/news-connector-j.xml
===================================================================
--- trunk/refman-common/news-connector-j.xml 2007-02-22 11:14:33 UTC (rev 5022)
+++ trunk/refman-common/news-connector-j.xml 2007-02-22 14:36:41 UTC (rev 5023)
Changed blocks: 3, Lines Added: 227, Lines Deleted: 13; 8928 bytes
@@ -52,25 +52,44 @@
<title>Changes in MySQL Connector/J 5.0.5 (Not yet released)</title>
<para>
- <emphasis role="bold">Important change:</emphasis> Due to a
- number of issues with the use of server-side prepared
- statements, Connector/J 5.0.5 has disabled their use by default.
- The disabling of server-side prepared statements does not affect
- the operation of the connector in any way.
+ Functionality added or changed:
</para>
- <para>
- To enable server-side prepared statements you must add the
- following configuration property to your connector string:
- </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">Important change:</emphasis> Due to a
+ number of issues with the use of server-side prepared
+ statements, Connector/J 5.0.5 has disabled their use by
+ default. The disabling of server-side prepared statements
+ does not affect the operation of the connector in any way.
+ </para>
+
+ <para>
+ To enable server-side prepared statements you must add the
+ following configuration property to your connector string:
+ </para>
+
<programlisting>useServerPrepStmts=true</programlisting>
- <para>
- The default value of this property is false (i.e. Connector/J
- does not use server-side prepared statements).
- </para>
+ <para>
+ The default value of this property is false (i.e.
+ Connector/J does not use server-side prepared statements).
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Performance enhancement of initial character set
+ configuration, driver will only send commands required to
+ configure connection character set session variables if the
+ current values on the server do not match what is required.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
Bugs fixed:
</para>
@@ -85,6 +104,185 @@
</para>
</listitem>
+ <listitem>
+ <para>
+ When using a JDBC connection URL that is malformed, the
+ <literal>NonRegisteringDriver.getPropertyInfo</literal>
+ method will throw a Null Pointer Exception (NPE) error. (Bug
+ #22628)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>DatabaseMetaData.getSQLKeywords()</literal>
+ does not return a consistent list of reserved keywords. (Bug
+ #24794)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Specifying <literal>US-ASCII</literal> as the character set
+ in a connection to a MySQL 4.1 or newer server does not map
+ correctly. (Bug #24840)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Storing a <literal>java.util.Date</literal> objection in a
+ <literal>BLOB</literal> column would not be serialized
+ correctly during <literal>setObject</literal>. (Bug #25787)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A query execution which timed out dod not always thow a
+ <literal>MySQLTimeoutException</literal>. (Bug #25836)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ A connection error would occur when connecting to a MySQL
+ server with certai character sets. Some collations/character
+ sets reported as "unknown" (specifically cias variants of
+ existing character sets), and inability to override the
+ detected server character set. (Bug #23645)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>setFetchSize()</literal> breaks prepared
+ <literal>SHOW</literal> and other commands. (Bug #24360)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Using <literal>DATETIME</literal> columnd would result in
+ time shifts when <literal>useServerPrepStmts</literal> was
+ true. (Bug #24344)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Inconsistency between <literal>getSchemas</literal> and
+ <literal>INFORMATION_SCHEMA</literal>. (Bug #23304)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When using the <literal>rewriteBatchedStatements</literal>
+ connection option with
+ <literal>PreparedState.executeBatch()</literal> an internal
+ memory leak would occur. (Bug #25073)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Fixed issue where field-level for metadata from
+ <literal>DatabaseMetaData</literal> when using
+ <literal>INFORMATION_SCHEMA</literal> didn't have references
+ to current connections, sometimes leading to
+ <literal>NullPointerExceptions</literal> when intropsecting
+ them via <literal>ResultSetMetaData</literal>.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Connector/J now returns a better error message when server
+ doesn't return enough information to determine stored
+ procedure/function parameter types. (Bug #24065)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ When using server-side prepared statements and timestamp
+ columns, value would be incorrectly populated (with
+ nanoseconds, not microseconds). (Bug #21438)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Timer instance used for
+ <literal>Statement.setQueryTimeout()</literal> created
+ per-connection, rather than per-VM, causing memory leak.
+ (Bug #25514)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Results sets from <literal>UPDATE</literal> statements with
+ multi-statement queries would cause an
+ <literal>SQLException</literal> error. (Bug #25009)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>StringUtils.indexOfIgnoreCaseRespectQuotes()</literal>
+ isn't case-insensitive on the first character of the target.
+ This bug also affected
+ <literal>rewriteBatchedStatements</literal> functionality
+ when prepared statements did not use uppercase for the
+ <literal>VALUES</literal> clause. (Bug #25047)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Some exceptions thrown out of
+ <literal>StandardSocketFactory</literal> were needlessly
+ wrapped, obscuring their true cause, especially when using
+ socket timeouts. (Bug #21480)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>DatabaseMetaData.getSchemas()</literal> doesn't
+ return a <literal>TABLE_CATALOG</literal> column. (Bug
+ #23303)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>EscapeProcessor</literal> gets confused by multiple
+ backslashes. We now push the responsibility of syntax errors
+ back on to the server for most escape sequences. (Bug
+ #25399)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ <literal>INOUT</literal> parameters in
+ <literal>CallableStatements</literal> get doubly-escaped.
+ (Bug #25379)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Connector/J would ignore the
+ <literal>socketFactory</literal> property, making it
+ difficult to use the
+ <literal>NamedPipeSocketFactory</literal>. (Bug #26326)
+ </para>
+ </listitem>
+
</itemizedlist>
</section>
@@ -589,6 +787,22 @@
does not use server-side prepared statements).
</para>
+ <para>
+ Bugs fixed:
+ </para>
+
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ Specifying <literal>US-ASCII</literal> as the character set
+ in a connection to a MySQL 4.1 or newer server does not map
+ correctly. (Bug #24840)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
</section>
<section id="cj-news-3-1-14">
Modified: trunk/refman-common/news-connector-net.xml
===================================================================
--- trunk/refman-common/news-connector-net.xml 2007-02-22 11:14:33 UTC (rev 5022)
+++ trunk/refman-common/news-connector-net.xml 2007-02-22 14:36:41 UTC (rev 5023)
Changed blocks: 4, Lines Added: 161, Lines Deleted: 27; 7326 bytes
@@ -24,6 +24,35 @@
<listitem>
<para>
+ <literal>BINARY</literal> and <literal>VARBINARY</literal>
+ columns would be returned as a string, not binary, datatype.
+ (Bug #25605)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Connector/NET would not compile properly when used with Mono
+ 1.2. (Bug #24263)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Opening a connection would be slow due to hostname lookup.
+ (Bug #26152).
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Connector/NET would fail to install under Windows Vista. (Bug
+ #26430)
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
Incorrect values/formats would be applied when the
<literal>OldSyntax</literal> connection string option was
used. (Bug #25950)
@@ -149,7 +178,7 @@
<listitem>
<para>
Improved speed and performance by re-architecting certain
- sectionsof the code.
+ sections of the code.
</para>
</listitem>
@@ -277,25 +306,54 @@
<title>Changes in MySQL Connector/NET Version 5.0.2 (06 November 2006)</title>
<para>
- <emphasis role="bold">Important change:</emphasis> Due to a number
- of issues with the use of server-side prepared statements,
- Connector/NET 5.0.2 has disabled their use by default. The
- disabling of server-side prepared statements does not affect the
- operation of the connector in any way.
+ Functionality added or changed:
</para>
- <para>
- To enable server-side prepared statements you must add the
- following configuration property to your connector string
- properties:
- </para>
+ <itemizedlist>
+ <listitem>
+ <para>
+ <emphasis role="bold">Important change:</emphasis> Due to a
+ number of issues with the use of server-side prepared
+ statements, Connector/NET 5.0.2 has disabled their use by
+ default. The disabling of server-side prepared statements does
+ not affect the operation of the connector in any way.
+ </para>
+
+ <para>
+ To enable server-side prepared statements you must add the
+ following configuration property to your connector string
+ properties:
+ </para>
+
<programlisting>ignore prepare=false</programlisting>
- <para>
- The default value of this property is true.
- </para>
+ <para>
+ The default value of this property is true.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ Implemented a stored procedure cache. By default, the
+ connector caches the metadata for the last 25 procedures that
+ are seen. You can change the numbver of procedures that are
+ cacheds by using the <literal>procedure cache</literal>
+ connection string.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An <literal>Ignore Prepare</literal> option has been added to
+ the connection string options. If enabled, prepared statements
+ will be disabled application-wide. The default for this option
+ is true.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
Bugs fixed:
</para>
@@ -638,30 +696,106 @@
</section>
-->
- <section id="connector-net-news-1.0.9">
+ <section id="connector-net-news-1.0.10">
- <title>Changes in MySQL Connector/NET Version 1.0.9 (Not yet released)</title>
+ <title>Changes in MySQL Connector/NET Version 1.0.10 (Not yet released)</title>
<para>
- <emphasis role="bold">Important change:</emphasis> Due to a number
- of issues with the use of server-side prepared statements,
- Connector/NET 5.0.2 has disabled their use by default. The
- disabling of server-side prepared statements does not affect the
- operation of the connector in any way.
+ Bugs fixed:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <literal>BINARY</literal> and <literal>VARBINARY</literal>
+ columns would be returned as a string, not binary, datatype.
+ (Bug #25605)
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
+ </section>
+
+ <section id="connector-net-news-1.0.9">
+
+ <title>Changes in MySQL Connector/NET Version 1.0.9 (02 February 2007</title>
+
<para>
- To enable server-side prepared statements you must add the
- following configuration property to your connector string
- properties:
+ Functionality added or changed:
</para>
+ <itemizedlist>
+
+ <listitem>
+ <para>
+ <emphasis role="bold">Important change:</emphasis> Due to a
+ number of issues with the use of server-side prepared
+ statements, Connector/NET 5.0.2 has disabled their use by
+ default. The disabling of server-side prepared statements does
+ not affect the operation of the connector in any way.
+ </para>
+
+ <para>
+ To enable server-side prepared statements you must add the
+ following configuration property to your connector string
+ properties:
+ </para>
+
<programlisting>ignore prepare=false</programlisting>
- <para>
- The default value of this property is true.
- </para>
+ <para>
+ The default value of this property is true.
+ </para>
+ </listitem>
+ <listitem>
+ <para>
+ <emphasis role="bold">Important change:</emphasis> Binaries
+ for .NET 1.0 are no longer supplied with this release. If you
+ need support for .NET 1.0, you must build from source.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Implemented a stored procedure cache. By default, the
+ connector caches the metadata for the last 25 procedures that
+ are seen. You can change the numbver of procedures that are
+ cacheds by using the <literal>procedure cache</literal>
+ connection string.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ An <literal>Ignore Prepare</literal> option has been added to
+ the connection string options. If enabled, prepared statements
+ will be disabled application-wide. The default for this option
+ is true.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ The ICSharpCode ZipLib is no longer used by the Connector, and
+ is no longer distributed with it.
+ </para>
+ </listitem>
+
+ <listitem>
+ <para>
+ Improved <literal>CommandBuilder.DeriveParameters</literal> to
+ first try and use the procedure cache before querying for the
+ stored procedure metadata. Return parameters created with
+ <literal>DeriveParameters</literal> now have the name
+ <literal>RETURN_VALUE</literal>.
+ </para>
+ </listitem>
+
+ </itemizedlist>
+
<para>
Bugs fixed:
</para>
Modified: trunk/refman-common/news-myodbc.xml
===================================================================
--- trunk/refman-common/news-myodbc.xml 2007-02-22 11:14:33 UTC (rev 5022)
+++ trunk/refman-common/news-myodbc.xml 2007-02-22 14:36:41 UTC (rev 5023)
Changed blocks: 2, Lines Added: 7, Lines Deleted: 0; 804 bytes
@@ -826,6 +826,7 @@
</section>
+
<section id="myodbc-news-3-51-13">
<title>Changes in Connector/ODBC 3.51.13 (Not yet released)</title>
@@ -865,6 +866,12 @@
<itemizedlist>
+<listitem><para>On 64-bit systems, some types would be incorrectly returned.
+ (Bug #26024)</para></listitem>
+
+<listitem><para>Using the <literal>SQL_ATTR_CONNECTION_TIMEOUT</literal>
+ attributed did not update the timeout. (Bug #19823)</para></listitem>
+
<listitem>
<para>
Using <literal>DataAdapter</literal>, Connector/ODBC may
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r5023 - trunk/refman-common | mcbrown | 22 Feb |
