Author: paul
Date: 2006-07-11 04:38:26 +0200 (Tue, 11 Jul 2006)
New Revision: 2694
Log:
r12084@frost: paul | 2006-07-10 21:32:56 -0500
Add missing tag.
Modified:
trunk/
trunk/refman-common/news-connector-j.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11257
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:11967
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
+ 4767c598-dc10-0410-bea0-d01b485662eb:/mysqldoc-local/mysqldoc/trunk:11257
b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:12084
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:8441
Modified: trunk/refman-common/news-connector-j.xml
===================================================================
--- trunk/refman-common/news-connector-j.xml 2006-07-11 02:21:17 UTC (rev 2693)
+++ trunk/refman-common/news-connector-j.xml 2006-07-11 02:38:26 UTC (rev 2694)
@@ -10,6 +10,7 @@
<section id="cj-news">
<title>&title-cj-news;</title>
+
<section id="cj-news-5-0-1">
<title>&title-cj-news-5-0-1;</title>
@@ -18,71 +19,82 @@
<listitem>
<para>
- Fixed can't use XAConnection for local transactions when
- no global transaction is in progress. (fixes Bug#17401)
- </para>
+ Fixed can't use XAConnection for local transactions when no
+ global transaction is in progress. (fixes Bug#17401)
+ </para>
</listitem>
<listitem>
<para>
- Fixed driver fails on non-ASCII platforms. The driver
- was assuming that the platform character set would be a superset
- of MySQL's "latin1" when doing the handshake for authentication,
- and when reading error messages. We now use Cp1252 for all strings
- sent to the server during the handshake phase, and a hard-coded mapping
- of the "language" server variable to the character set that
- is used for error messages. (Fixes Bug#18086)
+ Fixed driver fails on non-ASCII platforms. The driver was
+ assuming that the platform character set would be a superset
+ of MySQL's "latin1" when doing the handshake for
+ authentication, and when reading error messages. We now use
+ Cp1252 for all strings sent to the server during the handshake
+ phase, and a hard-coded mapping of the "language" server
+ variable to the character set that is used for error messages.
+ (Fixes Bug#18086)
</para>
</listitem>
<listitem>
<para>
- Fixed <literal>ConnectionProperties</literal> (and thus some
- subclasses) are not serializable, even though some J2EE containers
- expect them to be. (Fixes Bug#19169)
+ Fixed <literal>ConnectionProperties</literal> (and thus some
+ subclasses) are not serializable, even though some J2EE
+ containers expect them to be. (Fixes Bug#19169)
</para>
</listitem>
<listitem>
- <para>
- Fixed <literal>MysqlValidConnectionChecker</literal> for JBoss doesn't
- work with <literal>MySQLXADataSources</literal>. (Fixes Bug#20242)
+ <para>
+ Fixed <literal>MysqlValidConnectionChecker</literal> for JBoss
+ doesn't work with <literal>MySQLXADataSources</literal>.
+ (Fixes Bug#20242)
</para>
</listitem>
<listitem>
- <para>
- Better caching of character set converters (per-connection)
- to remove a bottleneck for multibyte character sets.
+ <para>
+ Better caching of character set converters (per-connection) to
+ remove a bottleneck for multibyte character sets.
</para>
</listitem>
<listitem>
- <para>
- Added connection/datasource property "pinGlobalTxToPhysicalConnection"
- (defaults to "false"). When set to "true", when using <literal>XAConnections</literal>, the
- driver ensures that operations on a given XID are always routed to the
- same physical connection. This allows the XAConnection to support
- "XA START ... JOIN" after "XA END" has been called, and is also a
- workaround for transaction managers that don't maintain thread affinity
- for a global transaction (most either always maintain thread affinity,
- or have it as a configuration option).
+ <para>
+ Added connection/datasource property
+ "pinGlobalTxToPhysicalConnection" (defaults to "false"). When
+ set to "true", when using <literal>XAConnections</literal>,
+ the driver ensures that operations on a given XID are always
+ routed to the same physical connection. This allows the
+ XAConnection to support "XA START ... JOIN" after "XA END" has
+ been called, and is also a workaround for transaction managers
+ that don't maintain thread affinity for a global transaction
+ (most either always maintain thread affinity, or have it as a
+ configuration option).
</para>
</listitem>
<listitem>
- <para>
- <literal>MysqlXaConnection.recover(int flags)</literal> now allows combinations of
- <literal>XAResource.TMSTARTRSCAN</literal> and <literal>TMENDRSCAN</literal>. To simulate the "scanning"
- nature of the interface, we return all prepared XIDs for <literal>TMSTARTRSCAN</literal>,
- and no new XIDs for calls with <literal>TMNOFLAGS</literal>, or <literal>TMENDRSCAN</literal> when not in
- combination with <literal>TMSTARTRSCAN</literal>. This change was made for API compliance,
- as well as integration with IBM WebSphere's transaction manager.
+ <para>
+ <literal>MysqlXaConnection.recover(int flags)</literal> now
+ allows combinations of
+ <literal>XAResource.TMSTARTRSCAN</literal> and
+ <literal>TMENDRSCAN</literal>. To simulate the "scanning"
+ nature of the interface, we return all prepared XIDs for
+ <literal>TMSTARTRSCAN</literal>, and no new XIDs for calls
+ with <literal>TMNOFLAGS</literal>, or
+ <literal>TMENDRSCAN</literal> when not in combination with
+ <literal>TMSTARTRSCAN</literal>. This change was made for API
+ compliance, as well as integration with IBM WebSphere's
+ transaction manager.
</para>
</listitem>
+ </itemizedlist>
+
</section>
-
+
<section id="cj-news-5-0-0">
<title>&title-cj-news-5-0-0;</title>
@@ -281,55 +293,61 @@
<title>&title-cj-news-3-1-14;</title>
<itemizedlist>
+
<listitem>
<para>
- Fixed updatable result set throws ClassCastException
- when there is row data and moveToInsertRow() is called. (Fixes Bug#20479)
+ Fixed updatable result set throws ClassCastException when
+ there is row data and moveToInsertRow() is called. (Fixes
+ Bug#20479)
</para>
</listitem>
<listitem>
- <para>
- Fixed Updatable result set that contains
- a BIT column fails when server-side prepared statements are used. (Fixes Bug#20485)
+ <para>
+ Fixed Updatable result set that contains a BIT column fails
+ when server-side prepared statements are used. (Fixes
+ Bug#20485)
</para>
</listitem>
<listitem>
- <para>
- Fixed memory leak with profileSQL=true. (Fixes Bug#16987)
+ <para>
+ Fixed memory leak with profileSQL=true. (Fixes Bug#16987)
</para>
</listitem>
<listitem>
- <para>
- - - Connection fails to localhost when using
- timeout and IPv6 is configured. (Fixes Bug#19726)
+ <para>
+ - - Connection fails to localhost when using timeout and IPv6
+ is configured. (Fixes Bug#19726)
</para>
</listitem>
<listitem>
- <para>
- Fixed NullPointerException in MysqlDataSourceFactory
- due to Reference containing RefAddrs with null content. (Fixes Bug#16791)
+ <para>
+ Fixed NullPointerException in MysqlDataSourceFactory due to
+ Reference containing RefAddrs with null content. (Fixes
+ Bug#16791)
</para>
</listitem>
<listitem>
- <para>
- Fixed ResultSet.getShort() for UNSIGNED TINYINT
- returns incorrect values when using server-side prepared statements. (Fixes Bug#20306)
- </para>
+ <para>
+ Fixed ResultSet.getShort() for UNSIGNED TINYINT returns
+ incorrect values when using server-side prepared statements.
+ (Fixes Bug#20306)
+ </para>
</listitem>
-
+
<listitem>
<para>
- Fixed can't pool server-side prepared statements, exception
- raised when re-using them. (Fixes Bug#20687 -
+ Fixed can't pool server-side prepared statements, exception
+ raised when re-using them. (Fixes Bug#20687 -
</para>
</listitem>
-
+
</itemizedlist>
+
</section>
<section id="cj-news-3-1-13">
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r2694 - in trunk: . refman-common | paul | 11 Jul |
