Author: tbedford
Date: 2009-02-26 18:21:12 +0100 (Thu, 26 Feb 2009)
New Revision: 13953
Log:
Added entry for bug #43071
Modified:
trunk/dynamic-docs/changelog/connector-j.xml
Modified: trunk/dynamic-docs/changelog/connector-j.xml
===================================================================
--- trunk/dynamic-docs/changelog/connector-j.xml 2009-02-26 17:16:43 UTC (rev 13952)
+++ trunk/dynamic-docs/changelog/connector-j.xml 2009-02-26 17:21:12 UTC (rev 13953)
Changed blocks: 24, Lines Added: 87, Lines Deleted: 74; 13166 bytes
@@ -5,6 +5,29 @@
<logentry entrytype="bug">
<bugs>
+ <fixes bugid="43071"/>
+ </bugs>
+
+ <versions>
+ <version ver="5.1.8"/>
+ </versions>
+
+ <message>
+
+ <para>
+ When the MySQL Server was upgraded from 4.0 to 5.0, the
+ Connector/J application then failed to connect to the server.
+ This was because authentication failed when the application ran
+ from EBCDIC platforms such as z/OS.
+ </para>
+
+ </message>
+
+ </logentry>
+
+ <logentry entrytype="bug">
+
+ <bugs>
<fixes bugid="42309"/>
</bugs>
@@ -2403,10 +2426,10 @@
<message>
<para>
- More intelligent initial packet sizes for the "shared"
- packets are used (512 bytes, rather than 16K), and initial
- packets used during handshake are now sized appropriately as to
- not require reallocation.
+ More intelligent initial packet sizes for the "shared" packets
+ are used (512 bytes, rather than 16K), and initial packets used
+ during handshake are now sized appropriately as to not require
+ reallocation.
</para>
</message>
@@ -3150,8 +3173,8 @@
<message>
<para>
- Driver now supports <literal>{call sp}</literal> (without
- "()" if procedure has no arguments).
+ Driver now supports <literal>{call sp}</literal> (without "()"
+ if procedure has no arguments).
</para>
</message>
@@ -3354,13 +3377,12 @@
<note>
<para>
If <literal>useNanosForElapsedTime</literal> is set to
- <literal>true</literal>, and this property is set to
- "0" (or left default), then elapsed times will still
- be measured in nanoseconds (if possible), but the slow query
- threshold will be converted from milliseconds to nanoseconds,
- and thus have an upper bound of approximately 2000
- milliseconds (as that threshold is represented as an integer,
- not a long).
+ <literal>true</literal>, and this property is set to "0" (or
+ left default), then elapsed times will still be measured in
+ nanoseconds (if possible), but the slow query threshold will
+ be converted from milliseconds to nanoseconds, and thus have
+ an upper bound of approximately 2000 milliseconds (as that
+ threshold is represented as an integer, not a long).
</para>
</note>
@@ -5598,26 +5620,24 @@
<message>
<para>
- Added experimental support for statement
- "interceptors" via the
+ Added experimental support for statement "interceptors" via the
<literal>com.mysql.jdbc.StatementInterceptor</literal>
interface, examples are in
<filename>com/mysql/jdbc/interceptors</filename>.
</para>
<para>
- Implement this interface to be placed "in between"
- query execution, so that you can influence it. (currently
+ Implement this interface to be placed "in between" query
+ execution, so that you can influence it. (currently
experimental).
</para>
<para>
- <literal>StatementInterceptors</literal> are
- "chainable" when configured by the user, the results
- returned by the "current" interceptor will be passed
- on to the next on in the chain, from left-to-right order, as
- specified by the user in the JDBC configuration property
- <literal>statementInterceptors</literal>.
+ <literal>StatementInterceptors</literal> are "chainable" when
+ configured by the user, the results returned by the "current"
+ interceptor will be passed on to the next on in the chain, from
+ left-to-right order, as specified by the user in the JDBC
+ configuration property <literal>statementInterceptors</literal>.
</para>
</message>
@@ -7265,10 +7285,9 @@
<literal>rewriteBatchedStatements</literal> to
<literal>true</literal> will now cause the driver to rewrite
batched prepared statements with more than 3 parameter sets in a
- batch into multi-statements (separated by ";") if they
- are not plain (that is, without
- <literal role="stmt">SELECT</literal> or <literal>ON DUPLICATE
- KEY UPDATE</literal> clauses)
+ batch into multi-statements (separated by ";") if they are not
+ plain (that is, without <literal role="stmt">SELECT</literal> or
+ <literal>ON DUPLICATE KEY UPDATE</literal> clauses)
<literal role="stmt">INSERT</literal> or
<literal role="stmt">REPLACE</literal> statements.
</para>
@@ -7457,8 +7476,7 @@
<message>
<para>
- Map "latin1" on MySQL server to CP1252 for MySQL >
- 4.1.0.
+ Map "latin1" on MySQL server to CP1252 for MySQL > 4.1.0.
</para>
</message>
@@ -8269,8 +8287,8 @@
<message>
<para>
- Give better error message when "streaming" result
- sets, and the connection gets clobbered because of exceeding
+ Give better error message when "streaming" result sets, and the
+ connection gets clobbered because of exceeding
<literal role="sysvar">net_write_timeout</literal> on the
server.
</para>
@@ -8737,8 +8755,8 @@
<para>
Added support for Apache Commons logging, use
- "com.mysql.jdbc.log.CommonsLogger" as the value for
- the "logger" configuration property.
+ "com.mysql.jdbc.log.CommonsLogger" as the value for the "logger"
+ configuration property.
</para>
</message>
@@ -8758,9 +8776,9 @@
<message>
<para>
- Specifying <literal>""</literal> means
- <quote>current</quote> catalog, even though this isn't quite
- JDBC spec compliant, it's there for legacy users.
+ Specifying <literal>""</literal> means <quote>current</quote>
+ catalog, even though this isn't quite JDBC spec compliant, it's
+ there for legacy users.
</para>
</message>
@@ -13777,9 +13795,9 @@
<para>
If you relied on autodetection before, you will need to add
- "logger=com.mysql.jdbc.log.Log4JLogger" to your JDBC
- URL to enable Log4J usage, or alternatively use the new
- "CommonsLogger" class to take care of this.
+ "logger=com.mysql.jdbc.log.Log4JLogger" to your JDBC URL to
+ enable Log4J usage, or alternatively use the new "CommonsLogger"
+ class to take care of this.
</para>
</message>
@@ -14055,9 +14073,9 @@
<para>
New feature — driver will automatically adjust session
variable <literal role="sysvar">net_write_timeout</literal> when
- it determines it has been asked for a "streaming"
- result, and resets it to the previous value when the result set
- has been consumed. (configuration property is named
+ it determines it has been asked for a "streaming" result, and
+ resets it to the previous value when the result set has been
+ consumed. (configuration property is named
<literal>netTimeoutForStreamingResults</literal> value and has a
unit of seconds, the value <literal>0</literal> means the driver
will not try and adjust this value).
@@ -14631,9 +14649,9 @@
if the feature is disabled at the client side. This is to
prevent a malicious server or man-in-the-middle from asking the
client for data that the client is not expecting. Thanks to Jan
- Kneschke for discovering the exploit and Andrey
- "Poohie" Hristov, Konstantin Osipov and Sergei
- Golubchik for discussions about implications and possible fixes.
+ Kneschke for discovering the exploit and Andrey "Poohie"
+ Hristov, Konstantin Osipov and Sergei Golubchik for discussions
+ about implications and possible fixes.
</para>
</message>
@@ -15083,9 +15101,9 @@
<para>
The data (and how it's stored) for <literal>ResultSet</literal>
rows are now behind an interface which allows us (in some cases)
- to allocate less memory per row, in that for
- "streaming" result sets, we re-use the packet used to
- read rows, since only one row at a time is ever active.
+ to allocate less memory per row, in that for "streaming" result
+ sets, we re-use the packet used to read rows, since only one row
+ at a time is ever active.
</para>
</message>
@@ -16155,10 +16173,10 @@
<message>
<para>
- LogFactory now prepends "com.mysql.jdbc.log" to log
- class name if it can't be found as-specified. This allows you to
- use "short names" for the built-in log factories, for
- example "logger=CommonsLogger" instead of
+ LogFactory now prepends "com.mysql.jdbc.log" to log class name
+ if it can't be found as-specified. This allows you to use "short
+ names" for the built-in log factories, for example
+ "logger=CommonsLogger" instead of
"logger=com.mysql.jdbc.log.CommonsLogger".
</para>
@@ -16473,9 +16491,8 @@
Re-worked stored procedure parameter parser to be more robust.
Driver no longer requires <literal>BEGIN</literal> in stored
procedure definition, but does have requirement that if a stored
- function begins with a label directly after the
- "returns" clause, that the label is not a quoted
- identifier.
+ function begins with a label directly after the "returns"
+ clause, that the label is not a quoted identifier.
</para>
</message>
@@ -16805,8 +16822,7 @@
<para>
Fixed bug when calling stored functions, where parameters
weren't numbered correctly (first parameter is now the return
- value, subsequent parameters if specified start at index
- "2").
+ value, subsequent parameters if specified start at index "2").
</para>
</message>
@@ -17633,9 +17649,9 @@
<para>
A connection error would occur when connecting to a MySQL server
with certain character sets. Some collations/character sets
- reported as "unknown" (specifically
- <literal>cias</literal> variants of existing character sets),
- and inability to override the detected server character set.
+ reported as "unknown" (specifically <literal>cias</literal>
+ variants of existing character sets), and inability to override
+ the detected server character set.
</para>
</message>
@@ -17892,8 +17908,8 @@
<para>
Row navigation now causes any streams/readers open on the result
set to be closed, as in some cases we're reading directly from a
- shared network packet and it will be overwritten by the
- "next" row.
+ shared network packet and it will be overwritten by the "next"
+ row.
</para>
</message>
@@ -17957,8 +17973,8 @@
<para>
<literal>CallableStatements</literal> with
- <literal>OUT/INOUT</literal> parameters that are
- "binary" (<literal role="type">BLOB</literal>,
+ <literal>OUT/INOUT</literal> parameters that are "binary"
+ (<literal role="type">BLOB</literal>,
<literal role="type">BIT</literal>,
<literal>(VAR)BINARY</literal>, <literal>JAVA_OBJECT</literal>)
have extra 7 bytes.
@@ -18318,9 +18334,8 @@
<para>
If the connection <literal>useTimezone</literal> is set to
<literal>true</literal>, then also respect time zone conversions
- in escape-processed string literals (for example,
- <literal>"{ts ...}"</literal> and <literal>"{t
- ...}"</literal>).
+ in escape-processed string literals (for example, <literal>"{ts
+ ...}"</literal> and <literal>"{t ...}"</literal>).
</para>
</message>
@@ -18912,8 +18927,8 @@
<para>
DBMD.getColumns() does not return expected COLUMN_SIZE for the
SET type, now returns length of largest possible set
- disregarding whitespace or the "," delimitters to be
- consistent with the ODBC driver.
+ disregarding whitespace or the "," delimitters to be consistent
+ with the ODBC driver.
</para>
</message>
@@ -20341,9 +20356,8 @@
<para>
Added unit tests for <literal>XADatasource</literal>, as well as
- friendlier exceptions for XA failures compared to the
- "stock" <literal>XAException</literal> (which has no
- messages).
+ friendlier exceptions for XA failures compared to the "stock"
+ <literal>XAException</literal> (which has no messages).
</para>
</message>
@@ -20365,8 +20379,7 @@
<para>
Connection checker for JBoss didn't use same method parameters
- via reflection, causing connections to always seem
- "bad".
+ via reflection, causing connections to always seem "bad".
</para>
</message>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r13953 - trunk/dynamic-docs/changelog | anthony.bedford | 26 Feb |
