Author: paul
Date: 2006-03-21 19:25:50 +0100 (Tue, 21 Mar 2006)
New Revision: 1639
Log:
r4040@kite-hub: paul | 2006-03-21 12:25:02 -0600
Add markup.
Modified:
trunk/
trunk/refman-common/news-connector-j.xml
Property changes on: trunk
___________________________________________________________________
Name: svk:merge
- b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8815
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4013
+ b5ec3a16-e900-0410-9ad2-d183a3acac99:/mysqldoc-local/mysqldoc/trunk:8815
bf112a9c-6c03-0410-a055-ad865cd57414:/mysqldoc-local/mysqldoc/trunk:4040
Modified: trunk/refman-common/news-connector-j.xml
===================================================================
--- trunk/refman-common/news-connector-j.xml 2006-03-20 21:04:35 UTC (rev 1638)
+++ trunk/refman-common/news-connector-j.xml 2006-03-21 18:25:50 UTC (rev 1639)
@@ -2015,20 +2015,24 @@
<listitem>
<para>
Fix comparisons made between string constants and dynamic
- strings that are either toUpperCase()d or toLowerCase()d to
- use Locale.ENGLISH, as some locales 'override' case rules for
- English. Also use StringUtils.indexOfIgnoreCase() instead of
- .toUpperCase().indexOf(), avoids creating a very short-lived
- transient String instance.
+ strings that are converted with either
+ <literal>toUpperCase()</literal> or
+ <literal>toLowerCase()</literal> to use
+ <literal>Locale.ENGLISH</literal>, as some locales
+ <quote>override</quote> case rules for English. Also use
+ <literal>StringUtils.indexOfIgnoreCase()</literal> instead of
+ <literal>.toUpperCase().indexOf()</literal>, avoids creating a
+ very short-lived transient <literal>String</literal> instance.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#5235 - Server-side prepared statements did not honor
- 'zeroDateTimeBehavior' property, and would cause class-cast
- exceptions when using ResultSet.getObject(), as the all-zero
- string was always returned.
+ Server-side prepared statements did not honor
+ <literal>zeroDateTimeBehavior</literal> property, and would
+ cause class-cast exceptions when using
+ <literal>ResultSet.getObject()</literal>, as the all-zero
+ string was always returned. (Bug #5235)
</para>
</listitem>
@@ -2037,79 +2041,85 @@
Fixed batched updates with server prepared statements weren't
looking if the types had changed for a given batched set of
parameters compared to the previous set, causing the server to
- return the error 'Wrong arguments to mysql_stmt_execute()'.
+ return the error <quote>Wrong arguments to
+ mysql_stmt_execute()</quote>.
</para>
</listitem>
<listitem>
<para>
Handle case when string representation of timestamp contains
- trailing '.' with no numbers following it.
+ trailing ‘<literal>.</literal>’ with no numbers
+ following it.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#5706 - Inefficient detection of pre-existing string
- instances in ResultSet.getNativeString().
+ Inefficient detection of pre-existing string instances in
+ <literal>ResultSet.getNativeString()</literal>. (Bug #5706)
</para>
</listitem>
<listitem>
<para>
- Don't throw exceptions for Connection.releaseSavepoint().
+ Don't throw exceptions for
+ <literal>Connection.releaseSavepoint()</literal>.
</para>
</listitem>
<listitem>
<para>
- Use a per-session Calendar instance by default when decoding
- dates from ServerPreparedStatements (set to old, less
+ Use a per-session <literal>Calendar</literal> instance by
+ default when decoding dates from
+ <literal>ServerPreparedStatements</literal> (set to old, less
performant behavior by setting property
- 'dynamicCalendars=true').
+ <literal>dynamicCalendars=true</literal>).
</para>
</listitem>
<listitem>
<para>
Added experimental configuration property
- 'dontUnpackBinaryResults', which delays unpacking binary
- result set values until they're asked for, and only creates
- object instances for non-numerical values (it is set to
- 'false' by default). For some usecase/jvm combinations, this
- is friendlier on the garbage collector.
+ <literal>dontUnpackBinaryResults</literal>, which delays
+ unpacking binary result set values until they're asked for,
+ and only creates object instances for non-numerical values (it
+ is set to <literal>false</literal> by default). For some
+ usecase/jvm combinations, this is friendlier on the garbage
+ collector.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#5729 - UNSIGNED BIGINT unpacked incorrectly from
- server-side prepared statement result sets.
+ <literal>UNSIGNED BIGINT</literal> unpacked incorrectly from
+ server-side prepared statement result sets. (Bug #5729)
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#6225 - ServerSidePreparedStatement allocating
- short-lived objects un-necessarily.
+ <literal>ServerSidePreparedStatement</literal> allocating
+ short-lived objects unnecessarily. (Bug #6225)
</para>
</listitem>
<listitem>
<para>
- Removed un-wanted new Throwable() in ResultSet constructor due
- to bad merge (caused a new object instance that was never used
- for every result set created) - Found while profiling for
- BUG#6359.
+ Removed unwanted new <literal>Throwable()</literal> in
+ <literal>ResultSet</literal> constructor due to bad merge
+ (caused a new object instance that was never used for every
+ result set created). Found while profiling for Bug #6359.
</para>
</listitem>
<listitem>
<para>
- Fixed too-early creation of StringBuffer in
- EscapeProcessor.escapeSQL(), also return String when escaping
- not needed (to avoid unnecssary object allocations). Found
- while profiling for BUG#6359.
+ Fixed too-early creation of <literal>StringBuffer</literal> in
+ <literal>EscapeProcessor.escapeSQL()</literal>, also return
+ <literal>String</literal> when escaping not needed (to avoid
+ unnecessary object allocations). Found while profiling for Bug
+ #6359.
</para>
</listitem>
@@ -2122,66 +2132,74 @@
<listitem>
<para>
- Fixed BUG#6537, SUM() on Decimal with server-side prepared
- statement ignores scale if zero-padding is needed (this ends
- up being due to conversion to DOUBLE by server, which when
- converted to a string to parse into BigDecimal, loses all
- 'padding' zeros).
+ <literal>SUM()</literal> on <literal>DECIMAL</literal> with
+ server-side prepared statement ignores scale if zero-padding
+ is needed (this ends up being due to conversion to
+ <literal>DOUBLE</literal> by server, which when converted to a
+ string to parse into <literal>BigDecimal</literal>, loses all
+ <quote>padding</quote> zeros). (Bug #6537)
</para>
</listitem>
<listitem>
<para>
- Use DatabaseMetaData.getIdentifierQuoteString() when building
- DBMD queries.
+ Use
+ <literal>DatabaseMetaData.getIdentifierQuoteString()</literal>
+ when building DBMD queries.
</para>
</listitem>
<listitem>
<para>
- Use 1MB packet for sending file for LOAD DATA LOCAL INFILE if
- that is < 'max_allowed_packet' on server.
+ Use 1MB packet for sending file for <literal>LOAD DATA LOCAL
+ INFILE</literal> if that is <
+ <literal>max_allowed_packet</literal> on server.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#6399, ResultSetMetaData.getColumnDisplaySize()
- returns incorrect values for multi-byte charsets.
+ <literal>ResultSetMetaData.getColumnDisplaySize()</literal>
+ returns incorrect values for multi-byte charsets. (Bug #6399)
</para>
</listitem>
<listitem>
<para>
- Make auto-deserialization of java.lang.Objects stored in BLOBs
- configurable via 'autoDeserialize' property (defaults to
- 'false').
+ Make auto-deserialization of
+ <literal>java.lang.Objects</literal> stored in
+ <literal>BLOB</literal> columns configurable via
+ <literal>autoDeserialize</literal> property (defaults to
+ <literal>false</literal>).
</para>
</listitem>
<listitem>
<para>
- Re-work Field.isOpaqueBinary() to detect 'CHAR(n) CHARACTER
- SET BINARY' to support fixed-length binary fields for
- ResultSet.getObject().
+ Re-work <literal>Field.isOpaqueBinary()</literal> to detect
+ <literal>CHAR(<replaceable>n</replaceable>) CHARACTER SET
+ BINARY</literal> to support fixed-length binary fields for
+ <literal>ResultSet.getObject()</literal>.
</para>
</listitem>
<listitem>
<para>
Use our own implementation of buffered input streams to get
- around blocking behavior of java.io.BufferedInputStream.
- Disable this with 'useReadAheadInput=false'.
+ around blocking behavior of
+ <literal>java.io.BufferedInputStream</literal>. Disable this
+ with <literal>useReadAheadInput=false</literal>.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#6348, failing to connect to the server when one of
- the addresses for the given host name is IPV6 (which the
- server does not yet bind on). The driver now loops through
- _all_ IP addresses for a given host, and stops on the first
- one that accepts() a socket.connect().
+ Failing to connect to the server when one of the addresses for
+ the given host name is IPV6 (which the server does not yet
+ bind on). The driver now loops through
+ <emphasis>all</emphasis> IP addresses for a given host, and
+ stops on the first one that <literal>accepts()</literal> a
+ <literal>socket.connect()</literal>. (Bug #6348)
</para>
</listitem>
@@ -2197,139 +2215,153 @@
<listitem>
<para>
- Fixed BUG#4510 - connector/j 3.1.3 beta does not handle
- integers correctly (caused by changes to support unsigned
- reads in Buffer.readInt() -> Buffer.readShort()).
+ Connector/J 3.1.3 beta does not handle integers correctly
+ (caused by changes to support unsigned reads in
+ <literal>Buffer.readInt()</literal> ->
+ <literal>Buffer.readShort()</literal>). (Bug #4510)
</para>
</listitem>
<listitem>
<para>
- Added support in DatabaseMetaData.getTables() and
- getTableTypes() for VIEWs which are now available in MySQL
- server version 5.0.x.
+ Added support in
+ <literal>DatabaseMetaData.getTables()</literal> and
+ <literal>getTableTypes()</literal> for views, which are now
+ available in MySQL server 5.0.x.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#4642 -- ServerPreparedStatement.execute*() sometimes
- threw ArrayIndexOutOfBoundsException when unpacking field
- metadata.
+ <literal>ServerPreparedStatement.execute*()</literal>
+ sometimes threw
+ <literal>ArrayIndexOutOfBoundsException</literal> when
+ unpacking field metadata. (Bug #4642)
</para>
</listitem>
<listitem>
<para>
- Optimized integer number parsing, enable 'old' slower integer
- parsing using JDK classes via 'useFastIntParsing=false'
- property.
+ Optimized integer number parsing, enable <quote>old</quote>
+ slower integer parsing using JDK classes via
+ <literal>useFastIntParsing=false</literal> property.
</para>
</listitem>
<listitem>
<para>
- Added 'useOnlyServerErrorMessages' property, which causes
- message text in exceptions generated by the server to only
- contain the text sent by the server (as opposed to the
- SQLState's 'standard' description, followed by the server's
- error message). This property is set to 'true' by default.
+ Added <literal>useOnlyServerErrorMessages</literal> property,
+ which causes message text in exceptions generated by the
+ server to only contain the text sent by the server (as opposed
+ to the SQLState's <quote>standard</quote> description,
+ followed by the server's error message). This property is set
+ to <literal>true</literal> by default.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#4689 - ResultSet.wasNull() does not work for
- primatives if a previous null was returned.
+ <literal>ResultSet.wasNull()</literal> does not work for
+ primatives if a previous <literal>null</literal> was returned.
+ (Bug #4689)
</para>
</listitem>
<listitem>
<para>
- Track packet sequence numbers if enablePacketDebug=true, and
- throw an exception if packets received out-of-order.
+ Track packet sequence numbers if
+ <literal>enablePacketDebug=true</literal>, and throw an
+ exception if packets received out-of-order.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#4482, ResultSet.getObject() returns wrong type for
- strings when using prepared statements.
+ <literal>ResultSet.getObject()</literal> returns wrong type
+ for strings when using prepared statements. (Bug #4482)
</para>
</listitem>
<listitem>
<para>
- Calling MysqlPooledConnection.close() twice (even though an
- application error), caused NPE. Fixed.
+ Calling <literal>MysqlPooledConnection.close()</literal> twice
+ (even though an application error), caused NPE. Fixed.
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#5012 -- ServerPreparedStatements dealing with return
- of DECIMAL type don't work.
+ <literal>ServerPreparedStatements</literal> dealing with
+ return of <literal>DECIMAL</literal> type don't work. (Bug
+ #5012)
</para>
</listitem>
<listitem>
<para>
- Fixed BUG#5032 -- ResultSet.getObject() doesn't return type
- Boolean for pseudo-bit types from prepared statements on 4.1.x
- (shortcut for avoiding extra type conversion when using
- binary-encoded result sets obscurred test in getObject() for
- 'pseudo' bit type)
+ <literal>ResultSet.getObject()</literal> doesn't return type
+ <literal>Boolean</literal> for pseudo-bit types from prepared
+ statements on 4.1.x (shortcut for avoiding extra type
+ conversion when using binary-encoded result sets obscured test
+ in <literal>getObject()</literal> for <quote>pseudo</quote>
+ bit type). (Bug #5032)
</para>
</listitem>
<listitem>
<para>
- You can now use URLs in 'LOAD DATA LOCAL INFILE' statements,
- and the driver will use Java's built-in handlers for
- retreiving the data and sending it to the server. This feature
- is not enabled by default, you must set the
- 'allowUrlInLocalInfile' connection property to 'true'.
+ You can now use URLs in <literal>LOAD DATA LOCAL
+ INFILE</literal> statements, and the driver will use Java's
+ built-in handlers for retreiving the data and sending it to
+ the server. This feature is not enabled by default, you must
+ set the <literal>allowUrlInLocalInfile</literal> connection
+ property to <literal>true</literal>.
</para>
</listitem>
<listitem>
<para>
The driver is more strict about truncation of numerics on
- ResultSet.get*(), and will throw an SQLException when
- truncation is detected. You can disable this by setting
- 'jdbcCompliantTruncation' to false (it is enabled by default,
- as this functionality is required for JDBC compliance).
+ <literal>ResultSet.get*()</literal>, and will throw an
+ <literal>SQLException</literal> when truncation is detected.
+ You can disable this by setting
+ <literal>jdbcCompliantTruncation</literal> to
+ <literal>false</literal> (it is enabled by default, as this
+ functionality is required for JDBC compliance).
</para>
</listitem>
<listitem>
<para>
Added three ways to deal with all-zero datetimes when reading
- them from a ResultSet, 'exception' (the default), which throws
- an SQLException with an SQLState of 'S1009', 'convertToNull',
- which returns NULL instead of the date, and 'round', which
- rounds the date to the nearest closest value which is
- '0001-01-01'.
+ them from a <literal>ResultSet</literal>:
+ <literal>exception</literal> (the default), which throws an
+ <literal>SQLException</literal> with an SQLState of
+ <literal>S1009</literal>; <literal>convertToNull</literal>,
+ which returns <literal>NULL</literal> instead of the date; and
+ <literal>round</literal>, which rounds the date to the nearest
+ closest value which is <literal>'0001-01-01'</literal>.
</para>
</listitem>
<listitem>
<para>
- Fixed ServerPreparedStatement to read prepared statement
- metadata off the wire, even though it's currently a
- placeholder instead of using MysqlIO.clearInputStream() which
- didn't work at various times because data wasn't available to
- read from the server yet. This fixes sporadic errors users
- were having with ServerPreparedStatements throwing
- ArrayIndexOutOfBoundExceptions.
+ Fixed <literal>ServerPreparedStatement</literal> to read
+ prepared statement metadata off the wire, even though it's
+ currently a placeholder instead of using
+ <literal>MysqlIO.clearInputStream()</literal> which didn't
+ work at various times because data wasn't available to read
+ from the server yet. This fixes sporadic errors users were
+ having with <literal>ServerPreparedStatements</literal>
+ throwing <literal>ArrayIndexOutOfBoundExceptions</literal>.
</para>
</listitem>
<listitem>
<para>
- Use com.mysql.jdbc.Message's classloader when loading resource
- bundle, should fix sporadic issues when the caller's
- classloader can't locate the resource bundle.
+ Use <literal>com.mysql.jdbc.Message</literal>'s classloader
+ when loading resource bundle, should fix sporadic issues when
+ the caller's classloader can't locate the resource bundle.
</para>
</listitem>
@@ -6297,7 +6329,7 @@
<listitem>
<para>
- Fixed escape processor to deal with un-matched { and } (thanks
+ Fixed escape processor to deal with unmatched { and } (thanks
to Craig Coles)
</para>
</listitem>
@@ -6389,7 +6421,7 @@
<listitem>
<para>
Fixes to PreparedStatement to send binary set by setXXXStream
- to be sent un-touched to the MySQL server.
+ to be sent untouched to the MySQL server.
</para>
</listitem>
| Thread |
|---|
| • svn commit - mysqldoc@docsrva: r1639 - in trunk: . refman-common | paul | 21 Mar |
