Table of Contents
This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 6.0, which is currently MySQL 6.0.5. Starting with MySQL 5.0, we began offering a new version of the Manual for each new series of MySQL releases (5.0, 5.1, and so on). For information about changes in previous release series of the MySQL database software, see the corresponding version of this Manual. For information about legacy versions of the MySQL software through the 4.1 series, see MySQL 3.23, 4.0, 4.1 Reference Manual.
We update this section as we add new features in the 6.0 series, so that everybody can follow the development process.
Note that we tend to update the manual at the same time we make changes to MySQL. If you find a recent version of MySQL listed here that you can't find on our download page (http://dev.mysql.com/downloads/), it means that the version has not yet been released.
The date mentioned with a release version is the date of the last BitKeeper ChangeSet on which the release was based, not the date when the packages were made available. The binaries are usually made available a few days after the date of the tagged ChangeSet, because building and testing all packages takes some time.
The manual included in the source and binary distributions may not be fully accurate when it comes to the release changelog entries, because the integration of the manual happens at build time. For the most up-to-date release changelog, please refer to the online version instead.
An overview of which features were added in MySQL 6.0 can be found here: Section 1.5.1, “What's New in MySQL 6.0”.
For a full list of changes, please refer to the changelog sections for each individual 6.0.x release.
Functionality added or changed:
Incompatible Change:
In MySQL 5.1.6, when log tables were implemented, the default
log destination for the general query and slow query log was
TABLE
. This default has been changed to
FILE
, which is compatible with MySQL 5.0, but
incompatible with earlier releases of MySQL 5.1 from 5.1.6 to
5.1.20. If you are upgrading from MySQL 5.0 to this release, no
logging option changes should be necessary. However, if you are
upgrading from 5.1.6 through 5.1.20 to this release and were
using TABLE
logging, use the
--log-output=TABLE
option explicitly to
preserve your server's table-logging behavior.
In MySQL 5.1.x, this bug was addressed twice because it turned out that the default was set in two places, only one of which was fixed the first time. (Bug#29993)
The C API contained several undocumented functions that have
been removed:
mysql_disable_reads_from_master()
,
mysql_disable_rpl_parse()
,
mysql_enable_reads_from_master()
,
mysql_enable_rpl_parse()
,
mysql_master_query()
,
mysql_master_send_query()
,
mysql_reads_from_master_enabled()
,
mysql_rpl_parse_enabled()
,
mysql_rpl_probe()
,
mysql_rpl_query_type()
,
mysql_set_master()
,
mysql_slave_query()
, and
mysql_slave_send_query()
.
(Bug#31952)
The LAST_EXECUTED
column of the
INFORMATION_SCHEMA.EVENTS
table now indicates
when the event started executing rather than when it finished
executing. As a result, the ENDS
column is
never less than LAST_EXECUTED
.
(Bug#29830)
The mysql_odbc_escape_string()
C API
function has been removed. It has multi-byte character escaping
issues, doesn't honor the
NO_BACKSLASH_ESCAPES
SQL mode and is not
needed anymore by Connector/ODBC as of 3.51.17.
(Bug#29592)
Added the SHA2()
function, which
calculates the SHA-2 family of hash functions (SHA-224, SHA-256,
SHA-384, and SHA-512). (Contributed by Bill Karwin)
(Bug#13174)
The Instance Manager (mysqlmanager) has been discontinued and is no longer provided in MySQL releases.
Bugs fixed:
Incompatible Change:
Inserting a row with a NULL
value for a
DATETIME
column results in a
CSV
file that the storage engine cannot read.
All CSV
tables now need to be defined with
each column marked as NOT NULL
. An error is
raised if you try to create a CSV
table with
columns that are not defined with NOT NULL
.
(Bug#31473, Bug#32817)
Important Change: MySQL Cluster:
AUTO_INCREMENT
columns had the following
problems when used in NDB
tables:
The AUTO_INCREMENT
counter was not
updated correctly when such a column was updated.
AUTO_INCREMENT
values were not
prefetched beyond statement boundaries.
AUTO_INCREMENT
values were not handled
correctly with INSERT IGNORE
statements.
After being set,
ndb_autoincrement_prefetch_sz
showed a
value of 1, regardless of the value it had actually been
set to.
As part of this fix, the behavior of
ndb_autoincrement_prefetch_sz
has changed.
Setting this to less than 32 no longer has any effect on
prefetching within statements (where IDs are now always obtained
in batches of 32 or more), but only between statements. The
default value for this variable has also changed, and is now
1
.
(Bug#25176, Bug#31956, Bug#32055)
MySQL Cluster:
An improperly reset internal signal was observed as a hang when
using events in the NDB
API but could result
in various errors.
(Bug#33206)
MySQL Cluster: Incorrectly handled parameters could lead to a crash in the Transaction Coordinator during a node failure, causing other data nodes to fail. (Bug#33168)
MySQL Cluster: When using micro-GCPs, if a node failed while preparing for a global checkpoint, the master node would use the wrong GCI. (Bug#32922)
MySQL Cluster:
Under some conditions, performing an ALTER
TABLE
on an NDBCLUSTER
table failed
with a Table is full error, even when
only 25% of DataMemory
was in use and the
result should have been a table using less memory (for example,
changing a VARCHAR(100)
column to
VARCHAR(80)
).
(Bug#32670)
MySQL Cluster: A memory leak occurred if a subscription start request was received by the subscription manager before the node making the request was fully connected to the cluster. (Bug#32652)
MySQL Cluster: A local checkpoint could sometimes be started before the previous LCP was restorable from a global checkpoint. (Bug#32519)
MySQL Cluster: High numbers of API nodes on a slow or congested network could cause connection negotiation to time out prematurely, leading to the following issues:
Excessive retries
Excessive CPU usage
Partially connected API nodes
MySQL Cluster:
When a mysqld acting as a cluster SQL node
starts the NDBCLUSTER
storage engine, there
is a delay during which some necessary data structures cannot be
initialized until after it has connected to the cluster, and all
MySQL Cluster tables should be opened as read-only. This worked
correctly when the NDB
binlog thread was
running, but when it was not running, Cluster tables were not
opened as read-only even when the data structures had not yet
been set up.
(Bug#32275)
MySQL Cluster: The failure of a master node could lead to subsequent failures in local checkpointing. (Bug#32160)
MySQL Cluster: In a cluster running in diskless mode and with arbitration disabled, the failure of a data node during an insert operation caused other data node to fail. (Bug#31980)
MySQL Cluster: Log event requests to ndb_mgmd could time out, causing it to fail. (Bug#29621)
MySQL Cluster:
The error message for NDB
error code 275
(Out of transaction records for complete
phase) was missing.
(Bug#29139)
MySQL Cluster: There was a short interval during the startup process prior to the beginning of heartbeat detection such that, were an API or management node to reboot or a network failure to occur, data nodes could not detect this, with the result that there could be a lingering connection. (Bug#28445)
MySQL Cluster: A restart of the cluster failed when more than 1 REDO phase was in use. (Bug#22696)
MySQL Cluster:
When inserting a row into an NDB
table with a
duplicate value for a non-primary unique key, the error issued
would reference the wrong key.
(Bug#21072)
Partitioning: It was possible to partition a table to which a foreign key referred. (Bug#32948)
Partitioning:
A query of the form SELECT
against a
partitioned col1
FROM
table
GROUP BY (SELECT
col2
FROM
table
LIMIT 1);table
having a
SET
column crashed the server.
(Bug#32772)
Partitioning:
SHOW CREATE TABLE
misreported the value of
AUTO_INCREMENT
for partitioned tables using
either of the InnoDB
or
ARCHIVE
storage engines.
(Bug#32247)
Partitioning:
Selecting from INFORMATION_SCHEMA.PARTITIONS
while partition management statements (for example,
ALTER TABLE ... ADD PARTITION
) were executing
caused the server to crash.
(Bug#32178)
Partitioning:
ORDER BY ... DESC
did not always work
correctly when selecting from partitioned tables.
(Bug#31890)
See also Bug#31001
Partitioning:
ALTER TABLE ... COALESCE PARTITION
on a table
partitioned by [LINEAR] HASH
or
[LINEAR] KEY
caused the server to crash.
(Bug#30822)
Partitioning:
LIKE
queries on tables partitioned by
KEY
could return incomplete results. The
problem was observed with the Falcon
storage
engine, but could affect third-party storage engines as well.
(Bug#30480)
Partitioning: It was not possible to insert the greatest possible value for a given data type into a partitioned table. For example, consider a table defined as shown here:
CREATE TABLE t (c BIGINT UNSIGNED) PARTITION BY RANGE(c) ( PARTITION p0 VALUES LESS THAN MAXVALUE );
The largest possible value for a BIGINT
UNSIGNED
column is 18446744073709551615, but the
statement INSERT INTO t VALUES
(18446744073709551615);
would fail, even though the
same statement succeeded were t
not a
partitioned table.
In other words, MAXVALUE
was treated as being
equal to the greatest possible value, rather than as a least
upper bound.
(Bug#29258)
Cluster Replication:
Memory was mistakenly freed for NdbBlob
objects when adding an index while replicating the cluster,
which could cause mysqld to crash.
(Bug#33142)
See also Bug#18106
Cluster Replication: Under certain conditions, the slave stopped processing relay logs. This resulted in the logs never being cleared and the slave eventually running out of disk space. (Bug#31958)
Cluster Replication:
When the master mysqld crashed or was
restarted, no LOST_EVENTS
entry was made in
the binlog.
(Bug#31484)
See also Bug#21494
The fix for Bug#11230 and Bug#26215 introduced a significant input-parsing slowdown for the mysql client. This has been corrected. (Bug#33057)
SHOW EVENTS
and selecting from the
INFORMATION_SCHEMA.EVENTS
table failed if the
current database was INFORMATION_SCHEMA
.
(Bug#32775)
Use of the cp932
character set with
CAST()
in an ORDER
BY
clause could cause a server crash.
(Bug#32726)
For FLUSH TABLES WITH READ LOCK
, the server
failed to properly detect write-locked tables when running with
low-priority updates, resulting in a crash or deadlock.
(Bug#32528)
Sending several KILL QUERY
statements to
target a connection running SELECT SLEEP()
could freeze the server.
(Bug#32436)
ssl-cipher
values in option files were not
being read by libmysqlclient
.
(Bug#32429)
If a global read lock acquired with FLUSH TABLES WITH
READ LOCK
was in effect, executing ALTER
TABLE
could cause a server crash.
(Bug#32395)
Assigning a 65,536-byte string to a TEXT
column (which can hold a maximum of 65,535 bytes) resulted in
truncation without a warning. Now a truncation warning is
generated.
(Bug#32282)
Various test program cleanups were made: 1)
mytest and libmysqltest
were removed. 2) bug25714 displays an error
message when invoked with incorrect arguments or the
--help
option. 3)
mysql_client_test exits cleanly with a proper
error status.
(Bug#32221)
The default grant tables on Windows contained information for
host production.mysql.com
, which should not
be there.
(Bug#32219)
For comparisons of the form date_col OP
datetime_const
(where
OP
is
=
,
<
,
>
,
<=
,
or
>=
),
the comparison is done using DATETIME
values,
per the fix for Bug#27590. However that fix caused any index on
date_col
not to be used and
compromised performance. Now the index is used again.
(Bug#32198)
DATETIME
arguments specified in numeric form
were treated by DATE_ADD()
as
DATE
values.
(Bug#32180)
When configure was run with
--with-libevent
, libevent
was not linked statically with mysqld,
preventing mysqld from being run with a
debugger.
(Bug#32156)
Killing a statement could lead to a race condition in the server. (Bug#32148)
With lower_case_table_names
set,
CREATE TABLE LIKE
was treated differently by
libmysqld
than by the non-embedded server.
(Bug#32063)
Within a subquery, UNION
was handled
differently than at the top level, which could result in
incorrect results or a server crash.
(Bug#32036, Bug#32051)
Changing the SQL mode to cause dates with “zero”
parts to be considered invalid (such as
'1000-00-00'
) could result in indexed and
non-indexed searches returning different results for a column
that contained such dates.
(Bug#31928)
The server used unnecessarily large amounts of memory when user
variables were used as an argument to
CONCAT()
or
CONCAT_WS()
.
(Bug#31898)
Using ORDER BY
leads to the wrong result when
using the ARCHIVE
on a table with a
BLOB
when the table cache is full. The table
may also be reported as crashed after the query has completed,
even though the table data was intact.
(Bug#31833)
ucs2
does not work as a client character set,
but attempts to use it as such were not rejected. Now
character_set_client
cannot be set to
ucs2
. This also affects statements such as
SET NAMES
and SET CHARACTER
SET
.
(Bug#31615)
For a table that had been opened with HANDLER
and marked for reopening after being closed with FLUSH
TABLES
, DROP TABLE
did not properly
discard the handler.
(Bug#31397)
The server crashed in the parser when running out of memory. Memory handling in the parser has been improved to gracefully return an error when out-of-memory conditions occur in the parser. (Bug#31153)
Improper calculation of CASE
expression results could lead to value truncation.
(Bug#30782)
When casting a string value to an integer, cases where the input
string contained a decimal point and was long enough to overrun
the unsigned long long
type were not handled
correctly. The position of the decimal point was not taken into
account which resulted in miscalculated numbers and incorrect
truncation to appropriate SQL data type limits.
(Bug#30453)
SHOW VARIABLES
did not correctly display the
value of the thread_handling
system variable.
(Bug#28785)
Some queries using the
NAME_CONST()
function failed to
return either a result or an error to the client, causing it to
hang. This was due to the fact that there was no check to insure
that both arguments to this function were constant expressions.
(Bug#27545, Bug#32559)
With the read_only
system variable enabled,
CREATE DATABASE
and DROP
DATABASE
were allowed to users who did not have the
SUPER
privilege.
(Bug#27440)
Symbolic links on Windows could fail to work. (Bug#26811)
mysqld sometimes miscalculated the number of
digits required when storing a floating-point number in a
CHAR
column. This caused the value to be
truncated, or (when using a debug build) caused the server to
crash.
(Bug#26788)
See also Bug#12860
CREATE TABLE LIKE
did not work when the
source table was an INFORMATION_SCHEMA
table.
(Bug#25629)
If the expected precision of an arithmetic expression exceeded the maximum precision supported by MySQL, the precision of the result was reduced by an unpredictable or arbitrary amount, rather than to the maximum precision. In some cases, exceeding the maximum supported precision could also lead to a crash of the server. (Bug#24907)
A CREATE TRIGGER
statement could cause a
deadlock or server crash if it referred to a table for which a
table lock had been acquired with LOCK
TABLES
.
(Bug#23713)
The parser treated the
INTERVAL()
function incorrectly,
leading to situations where syntax errors could result depending
on which side of an arithmetic operator the function appeared.
(Bug#22312)
It was possible to execute CREATE TABLE t1 ... SELECT
... FROM t2
with the CREATE
privilege for t1
and
SELECT
privilege for t2
,
even in the absence of the INSERT
privilege
for t1
.
(Bug#20901)
Issuing an SQL KILL
of the active connection
caused an error on Mac OS X.
(Bug#19723)
The -lmtmalloc
library was removed from the
output of mysql_config on Solaris, as it
caused problems when building DBD::mysql
(and
possibly other applications) on that platform that tried to use
dlopen() to access the client library.
(Bug#18322)
Functionality added or changed:
Important Change: Partitioning: Security Fix:
It was possible, by creating a partitioned table using the
DATA DIRECTORY
and INDEX
DIRECTORY
options to gain privileges on other tables
having the same name as the partitioned table. As a result of
this fix, any table-level DATA DIRECTORY
or
INDEX DIRECTORY
options are now ignored for
partitioned tables.
(Bug#32091, CVE-2007-5970)
Incompatible Change: The Unicode implementation has been extended to provide support for supplementary characters that lie outside the Basic Multilingual Plane (BMP). Noteworthy features:
utf16
and utf32
character sets have been added. These correspond to the
UTF-16 and UTF-32 encodings of the Unicode character set,
and they both support supplementary characters.
The utf8
character set from previous
versions of MySQL has been renamed to
utf8mb3
, to reflect that its encoding
uses a maximum of three bytes for multi-byte characters.
(Old tables that previously used utf8
will be reported as using utf8mb3
after
an in-place upgrade to MySQL 6.0, but otherwise work as
before.)
The new utf8
character set in MySQL 6.0
is similar to utf8mb3
, but its encoding
allows up to four bytes per character to enable support for
supplementary characters.
The ucs2
character set is essentially
unchanged except for the inclusion of some newer BMP
characters.
In most respects, upgrading from MySQL 5.1 to 6.0 should present few problems with regard to Unicode usage, although there are some potential areas of incompatibility. Some examples:
For the variable-length character data types
(VARCHAR
and the TEXT
types), the maximum length in characters for
utf8
columns is less in MySQL 6.0 than
previously.
For all character data types (CHAR
,
VARCHAR
, and the TEXT
types), the maximum number of characters for
utf8
columns that can be indexed is less
in MySQL 6.0 than previously.
Consequently, if you want to upgrade tables from the old
utf8
(now utf8mb3
) to the
current utf8
, it may be necessary to change
some column or index definitions.
For additional details about the new Unicode character sets and potential incompatibilities, see Section 8.1.8, “Unicode Support”, and Section 8.1.9, “Upgrading from Previous to Current Unicode Support”.
If you use events, a known issue is that if you upgrade from MySQL 5.1 to 6.0.4, the event scheduler will not work, even after you run mysql_upgrade. (This is an issue only for an upgrade, not for a new installation of MySQL 6.0.4.) To work around this upgrading problem, use these instructions:
In MySQL 5.1, before upgrading, create a dump file
containing your mysql.event
table:
shell> mysqldump -uroot -p mysql event > event.sql
Stop the server, upgrade to MySQL 6.0, and start the server.
Recreate the mysql.event
table using the
dump file:
shell> mysql -uroot -p mysql < event.sql
Run mysql_upgrade to upgrade the other
system tables in the mysql
database:
shell> mysql_upgrade -uroot -p
Restart the server. The event scheduler should run normally.
Incompatible Change: Because of a change in the format of the Falcon pages stored within Falcon database files, Falcon databases created in MySQL 6.0.4 (or later) are not compatible with previous releases, and existing Falcon databases are incompatible with MySQL 6.0.4 (and later versions. You should dump Falcon databases using mysqldump before upgrading, and then reload them after the upgrade. For more information, see Section 4.5.4, “mysqldump — A Database Backup Program”.
Partitioning: Error messages for partitioning syntax errors have been made more descriptive. (Bug#29368)
Replication:
Replication of the following now switches to row-based logging
in MIXED
mode, and generates a warning in
STATEMENT
mode:
CURRENT_USER
See Section 5.2.4.3, “Mixed Binary Logging (MBL) Format”, for more information. (Bug#12092, Bug#28086, Bug#30244)
Cluster Replication: A replication heartbeat mechanism has been added to facilitate monitoring. This provides an alternative to checking log files, making it possible to detect in real time when a slave has failed.
Configuration of heartbeats is done via a new
MASTER_HEARTBEAT_PERIOD =
clause for the
interval
CHANGE MASTER TO
statement (see
Section 11.6.2.1, “CHANGE MASTER TO
Syntax”); monitoring can be done by
checking the values of the status variables
Slave_heartbeat_period
and
Slave_received_heartbeats
(see
Section 5.1.5, “Status Variables”).
The addition of replication heartbeats addresses a number of issues:
Relay logs were rotated every
slave_net_timeout
seconds even if no
statements were being replicated.
SHOW SLAVE STATUS
displayed an
incorrect value for
seconds_behind_master
following a
FLUSH LOGS
statement.
Replication master-slave connections used
slave_net_timeout
for connection
timeouts.
The --event-scheduler
option without a value
disabled the event scheduler. Now it enables the event
scheduler.
(Bug#31332)
mysqldump produces a -- Dump
completed on
comment
at the end of the dump if DATE
--comments
is given.
The date causes dump files for identical data take at different
times to appear to be different. The new options
--dump-date
and
--skip-dump-date
control whether the date is
added to the comment. --skip-dump-date
suppresses date printing. The default is
--dump-date
(include the date in the comment).
(Bug#31077)
MySQL now can be compiled with gcc 4.2.x.
There was a problem involving a conflict with the
min()
and max()
macros
in my_global.h
.
(Bug#28184)
It is now possible to set long_query_time
in
microseconds or to 0. Setting this value to 0 causes all queries
to be recorded in the slow query log.
Currently, fractional values can be used only when logging to files. We plan to provide this functionality for logging to tables when time-related data types are enhanced to support microsecond resolution. (Bug#25412)
INFORMATION_SCHEMA
implementation changes
were made that optimize certain types of queries for
INFORMATION_SCHEMA
tables so that they
execute more quickly.
Section 6.2.17, “INFORMATION_SCHEMA
Optimization”, provides
guidelines on how to take advantage of these optimizations by
writing queries that minimize the need for the server to access
the filesystem to obtain the information contained in
INFORMATION_SCHEMA
tables. By writing queries
that enable the server to avoid directory scans or opening table
files, you will obtain better performance.
(Bug#19588)
When the server detects MyISAM
table
corruption, it now writes additional information to the error
log, such as the name and line number of the source file, and
the list of threads accessing the table. Example: Got
an error from thread_id=1, mi_dynrec.c:368
. This is
useful information to include in bug reports.
Two options relating to slow query logging have been added for
mysqld.
--log-slow-slave-statements
causes slow
statements executed by a replication slave to be written to the
slow query log; min_examined_row_limit
can be
used to cause queries which examine fewer than the stated number
of rows not to be logged.
Bugs fixed:
Security Fix:
Using RENAME TABLE
against a table with
explicit DATA DIRECTORY
and INDEX
DIRECTORY
options can be used to overwrite system
table information by replacing the symbolic link points. the
file to which the symlink points.
MySQL will now return an error when the file to which the symlink points already exists. (Bug#32111, CVE-2007-5969)
Security Fix:
ALTER VIEW
retained the original
DEFINER
value, even when altered by another
user, which could allow that user to gain the access rights of
the view. Now ALTER VIEW
is allowed only to
the original definer or users with the SUPER
privilege.
(Bug#29908)
Security Fix:
When using a FEDERATED
table, the local
server can be forced to crash if the remote server returns a
result with fewer columns than expected.
(Bug#29801)
Important Change: Incompatible Change:
A number of problems existed in the implementation of
MERGE
tables that could cause problems. The
problems are summarized below:
Bug#26379 - Combination of FLUSH TABLE
and REPAIR TABLE
corrupts a
MERGE
table. This was caused in a number
of situations:
A thread trying to lock a MERGE
table
performs busy waiting while REPAIR
TABLE
or a similar table administration task
is ongoing on one or more of its MyISAM tables.
A thread trying to lock a MERGE
table
performs busy waiting until all threads that did
REPAIR TABLE
or similar table
administration tasks on one or more of its MyISAM tables
in LOCK TABLES segments do UNLOCK TABLES. The difference
against problem #1 is that the busy waiting takes place
after the administration task. It is terminated by
UNLOCK TABLES
only.
Two FLUSH TABLES
within a
LOCK TABLES
segment can invalidate
the lock. This does not require a
MERGE
table. The first FLUSH
TABLES
can be replaced by any statement that
requires other threads to reopen the table. In 5.0 and
5.1 a single FLUSH TABLES
can provoke
the problem.
Bug#26867 - Simultaneously executing LOCK
TABLES
and REPAIR TABLE
on a
MERGE
table would result in memory/cpu
hogging.
Trying DML on a MERGE
table, which has a
child locked and repaired by another thread, made an
infinite loop in the server.
Bug#26377 - Deadlock with MERGE
and
FLUSH TABLE
Locking a MERGE table and its children in parent-child order and flushing the child deadlocked the server.
Bug#25038 - Waiting TRUNCATE
Truncating a MERGE child, while the MERGE table was in use, let the truncate fail instead of waiting for the table to become free.
Bug#25700 - MERGE
base tables get
corrupted by OPTIMIZE/ANALYZE/REPAIR
TABLE
Repairing a child of an open MERGE
table
corrupted the child. It was necessary to
FLUSH
the child first.
Bug#30275 - MERGE
tables: FLUSH
TABLES
or UNLOCK TABLES
causes
server to crash.
Flushing and optimizing locked MERGE
children crashed the server.
Bug#19627 - temporary merge table locking
Use of a temporary MERGE
table with
non-temporary children could corrupt the children.
Temporary tables are never locked. Creation of tables with
non-temporary children of a temporary
MERGE
table is now prohibited.
Bug#27660 - Falcon: MERGE
table possible
It was possible to create a MERGE
table
with non-MyISAM children.
Bug#30273 - MERGE
tables: Can't lock
file (errno: 155)
This was a Windows-only bug. Table administration statements sometimes failed with "Can't lock file (errno: 155)".
The fix introduces the following changes in behavior:
This patch changes the behavior of temporary
MERGE
tables. Temporary
MERGE
must have temporary children. The
old behavior was wrong. A temporary table is not locked.
Hence even non-temporary children were not locked. See Bug#19627.
You cannot change the union list of a non-temporary
MERGE
table when LOCK TABLES is in
effect. The following does not work:
CREATE TABLE m1 ... ENGINE=MRG_MYISAM ...; LOCK TABLES t1 WRITE, t2 WRITE, m1 WRITE; ALTER TABLE m1 ... UNION=(t1,t2) ...;
However, you can do this with a temporary
MERGE
table.
You cannot create a MERGE
table with
CREATE ... SELECT
, neither as a temporary
MERGE
table, nor as a non-temporary
MERGE
table. For example:
CREATE TABLE m1 ... ENGINE=MRG_MYISAM ... SELECT ...;
Gives error message: table is not BASE
TABLE
.
(Bug#26377, Bug#26379, Bug#26867, Bug#25038, Bug#25700, Bug#30275, Bug#19627, Bug#27660, Bug#30273)
Incompatible Change:
SET PASSWORD
statements now cause an implicit
commit, and thus are prohibited within stored functions and
triggers.
(Bug#30904)
Incompatible Change:
The mysql_install_db
script could fail to
locate some components (including resolveip)
during execution if the --basedir
option was
specified on the command-line or within the
my.cnf
file. This was due to a conflict
when comparing the compiled-in values and the supplied values.
The --source-install
command-line option to
the script has been removed and replaced with the
--srcdir
option.
mysql_install_db now locates components
either using the compiled-in options, the
--basedir
option or --srcdir
option.
(Bug#30759)
Incompatible Change: It was possible for option files to be read twice at program startup, if some of the standard option file locations turned out to be the same directory. Now duplicates are removed from the list of files to be read.
Also, users could not override system-wide settings using
~/.my.cnf
because
was read last. The latter file now is read earlier so that
SYSCONFDIR
/my.cnf~/.my.cnf
can override system-wide
settings.
(Bug#20748)
Partitioning: Important Note:
An apostrophe or single quote character
('
) used in the DATA
DIRECTORY
, INDEX DIRECTORY
, or
COMMENT
for a PARTITION
clause caused the server to crash. When used as part of a
CREATE TABLE
statement, the crash was
immediate. When used in an ALTER TABLE
statement, the crash did not occur until trying to perform a
SELECT
or DML statement on the table. In
either case, the server could not be completely restarted until
the .FRM
file corresponding to the newly
created or altered table was deleted.
Upgrading to the current (or later) release solves this
problem only for tables that are newly created or altered.
Tables created or altered in previous versions of the server
to include '
characters in
PARTITION
options must still be removed by
deleting the corresponding .FRM
files and
re-creating them afterwards.
Partitioning: MySQL Cluster:
EXPLAIN PARTITIONS
reported partition usage
by queries on NDB
tables according to the
standard MySQL hash function than the hash function used in the
NDB
storage engine.
(Bug#29550)
Replication: MySQL Cluster:
Row-based replication from or to a big-endian machine where the
table used the NDB
storage engine failed, if
the same table on the other machine was either
non-NDB
or the other machine was
little-endian.
(Bug#29549, Bug#30790)
MySQL Cluster:
An insert or update with combined range and equality constraints
failed when run against an NDB
table with the
error Got unknown error from NDB. An
example of such a statement would be UPDATE t1 SET b =
5 WHERE a IN (7,8) OR a >= 10;
.
(Bug#31874)
MySQL Cluster:
An error with an if
statement in
sql/ha_ndbcluster.cc
could potentially lead
to an infinite loop in case of failure when working with
AUTO_INCREMENT
columns in
NDB
tables.
(Bug#31810)
MySQL Cluster:
The NDB
storage engine code was not safe for
strict-alias optimization in gcc 4.2.1.
(Bug#31761)
MySQL Cluster: Following an upgrade, ndb_mgmd would fail with an ArbitrationError. (Bug#31690)
MySQL Cluster: It was possible in some cases for a node group to be “lost” due to missed local checkpoints following a system restart. (Bug#31525)
MySQL Cluster:
A query against a table with TEXT
or
BLOB
columns that would return more than a
certain amount of data failed with Got error 4350
'Transaction already aborted' from NDBCLUSTER.
(Bug#31482)
This regression was introduced by Bug#29102
MySQL Cluster:
NDB
tables having names containing
non-alphanumeric characters (such as “
$
”) were not discovered correctly.
(Bug#31470)
MySQL Cluster: A node failure during a local checkpoint could lead to a subsequent failure of the cluster during a system restart. (Bug#31257)
MySQL Cluster: In some cases, the cluster managment server logged entries multiple times following a restart of mgmd. (Bug#29565)
MySQL Cluster:
ndb_mgm --help
did not
display any information about the -a
option.
(Bug#29509)
MySQL Cluster: An interpreted program of sufficient size and complexity could cause all cluster data nodes to shut down due to buffer overruns. (Bug#29390)
MySQL Cluster:
Performing DELETE
operations after a data
node had been shut down could lead to inconsistent data
following a restart of the node.
(Bug#26450)
MySQL Cluster:
UPDATE IGNORE
could sometimes fail on
NDB
tables due to the use of unitialized data
when checking for duplicate keys to be ignored.
(Bug#25817)
MySQL Cluster: The cluster log was formatted inconsistently and contained extraneous newline characters. (Bug#25064)
MySQL Cluster: (Replication): Inconsistencies could occur between the master and the slave when replicating Disk Data tables. (Bug#19259, Bug#19227)
Partitioning:
Repeated updates of a table that was partitioned by
KEY
on a TIMESTAMP
column
eventually crashed the server.
(Bug#32067)
Partitioning:
Selecting from a table partitioned by KEY
on
a VARCHAR
column whose size was greater than
65530 caused the server to crash.
(Bug#31705)
Partitioning:
INSERT DELAYED
into a partitioned table
crashed the server.
(Bug#31201)
Partitioning:
Using ALTER TABLE
to partition an existing
table having an AUTO_INCREMENT
column could
crash the server.
(Bug#30878)
This regression was introduced by Bug#27405
Partitioning: Falcon cannot drop a table for which there is a pending transaction, but the error message for such attempts was misleading. (Bug#22972)
Replication:
When dropping a database containing a stored procedure while
using row-cased replication, the delete of the stored procedure
from the mysql.proc
table was recorded in the
binary log following the DROP DATABASE
statement. To correct this issue, DROP
DATABASE
now uses statement-based replication.
(Bug#32435)
Replication: It was possible for the name of the relay log file to exceed the amount of memory reserved for it, possibly leading to a crash of the server. (Bug#31836)
See also Bug#28597
Replication: Corruption of log events caused the server to crash on 64-bit Linux systems having 4 GB of memory or more. (Bug#31793)
Replication: Trying to replicate an update of a row that was missing on the slave led to a failure on the slave. (Bug#31702)
Replication: Table names were displayed as binary “garbage” characters in slave error messages. The issue was observed on 64-bit Windows but may have effected other platforms. (Bug#30854)
Replication: One thread could read uninitialized memory from the stack of another thread. This issue was only known to occur in a mysqld process acting as both a master and a slave. (Bug#30752)
Replication:
It was possible to set SQL_SLAVE_SKIP_COUNTER
such that the slave would jump into the middle of an event
group, including possibly a transaction.
(Bug#28618)
See also Bug#12691
Replication: Due a previous change in how the default name and location of the binlog file were determined, replication failed following some upgrades. (Bug#28597)
See also Bug#31836
This regression was introduced by Bug#20166
Replication:
Stored procedures having BIT
parameters were
not replicated correctly.
(Bug#26199)
Replication:
Issuing SHOW SLAVE STATUS
as
mysqld was shutting down could cause a crash.
(Bug#26000)
Replication: If a temporary error occured inside an event group on an event that was not the first event of the group, the slave could get caught in an endless loop because the retry counter was reset whenever an event was executed successfully. (Bug#24860)
Replication:
An UPDATE
statement using a stored function
that modified a non-transactional table was not logged if it
failed. This caused the copy of the non-transactional table on
the master have a row that the copy on the slave did not.
(Bug#23333)
See also Bug#12713
Replication:
A replication slave sometimes failed to reconnect because it was
unable to run SHOW SLAVE HOSTS
. It was not
necessary to run this statement on slaves (since the master
should track connection IDs), and the execution of this
statement by slaves was removed.
(Bug#21132)
Replication: A replication slave sometimes stopped for changes that were idempotent (that is, such changes should have been considered “safe”), even though it should have simply noted that the change was already done, and continued operation. (Bug#19958)
Cluster Replication: A node failure during replication could lead to buckets out of order; now active subscribers are checked for, rather than empty buckets. (Bug#31701)
Cluster Replication: In some cases, not all tables were properly initialized before the binlog thread was started. (Bug#31618)
Using Falcon
when accessing multiple versions
of the same record, certain records could fail to be retrieved
from the record cache, causing an assertion failure.
(Bug#32862)
Creating an index on a Falcon
table with a
column using UTF32 that has been converted to UTF8 would cause a
server crash.
(Bug#32833)
Using ALTER TABLE
on a
Falcon
table it would be possible to create
two tables with the same name but different case.
(Bug#32830)
Converting a table from InnoDB
to
Falcon
, where the Falcon table with the same
name (but different case) would cause a server crash.
(Bug#32829)
Repeatedly creating and dropping Falcon
tablespaces would fail because a dropped tablespace would not be
dropped before the new tablespace file was created.
(Bug#32621)
The INTERVAL()
function
incorrectly handled NULL
values in the value
list.
(Bug#32560)
Use of a NULL
-returning GROUP
BY
expression in conjunction with WITH
ROLLUP
could cause a server crash.
(Bug#32558)
ORDER BY UpdateXML(...)
caused the server to
crash in queries where
UpdateXML()
returned
NULL
.
(Bug#32557)
Falcon
used a fixed index key size which
would be too small to cope with some Falcon page sizes, leading
to a crash. Falcon now supports variable length index keys
according to the supported page sizes. See
falcon_page_size.
(Bug#32554)
The rules for valid column names were being applied differently for base tables and views. (Bug#32496)
Falcon
options to set the limits of memory
usage would not be honoured. This could lead to crashes and
assertions during normal usage, instead of generating a suitable
warning.
(Bug#32413)
Falcon
would incorrectly return the supported
repeatable-read level when queried by the Online Backup system,
preventing the ability to create a consistent snapshot backup.
(Bug#32301)
Some uses of user variables in a query could result in a server crash. (Bug#32260)
Under certain conditions, the presence of a GROUP
BY
clause could cause an ORDER BY
clause to be ignored.
(Bug#32202)
Altering a Falcon
table to support an auto
increment column on a column with existing data and null values
would incorrectly update the table and return an incorrect count
of the altered rows.
(Bug#32194)
InnoDB
does not support
SPATIAL
indexes, but could crash when asked
to handle one. Now an error is returned.
(Bug#32125)
The server crashed on optimizations involving a join of
INT
and MEDIUMINT
columns
and a system variable in the WHERE
clause.
(Bug#32103)
mysql-test-run.pl used the
--user
option when starting
mysqld, which produces warnings if the
current user is not root
. Now
--user
is added only for
root
.
(Bug#32078)
Inserting, updating and deleting a large number of
BLOB
records in a Falcon table would take
significant amount of time and may prevent shutdown.
(Bug#32062)
On 64-bit platforms, assignments of values to enumeration-valued storage engine-specific system variables were not validated and could result in unexpected values. (Bug#32034)
A DELETE
statement with a subquery in the
WHERE
clause would sometimes ignore an error
during subquery evaluation and proceed with the delete
operation.
(Bug#32030)
Using dates in the range '0000-00-01'
to
'0000-00-99'
range in the
WHERE
clause could result in an incorrect
result set. (These dates are not in the supported range for
DATE
, but different results for a given query
could occur depending on position of records containing the
dates within a table.)
(Bug#32021)
User-defined functions are not loaded if the server is started
with the --skip-grant-tables
option, but the
server did not properly handle this case and issued an
Out of memory error message instead.
(Bug#32020)
If a user-defined function was used in a
SELECT
statement, and an error occurred
during UDF initialization, the error did not terminate execution
of the SELECT
, but rather was converted to a
warning.
(Bug#32007)
In debug builds, testing the result of an IN
subquery against NULL
caused an assertion
failure.
(Bug#31884)
SHOW CREATE TRIGGER
caused a server crash.
(Bug#31866)
The server crashed after insertion of a negative value into an
AUTO_INCREMENT
column of an
InnoDB
table.
(Bug#31860)
For libmysqld
applications, handling of
mysql_change_user()
calls left
some pointers improperly updated, leading to server crashes.
(Bug#31850)
Comparison results for BETWEEN
were different from those for operators like
<
and
>
for DATETIME
-like values with trailing extra
characters such as '2007-10-01 00:00:00
GMT-6'
. BETWEEN
treated the values as DATETIME
, whereas the
other operators performed a binary-string comparison. Now they
all uniformly use a DATETIME
comparison, but
generate warnings for values with trailing garbage.
(Bug#31800)
With ONLY_FULL_GROUP_BY
SQL mode enabled,
queries such as SELECT a FROM t1 HAVING
COUNT(*)>2
were not being rejected as they should
have been.
(Bug#31794)
The server could crash during filesort
for
ORDER BY
based on expressions with
INET_NTOA()
or
OCT()
if those functions
returned NULL
.
(Bug#31758)
For a fatal error during filesort in
find_all_keys()
, the error was returned
without the necessary handler uninitialization, causing an
assertion failure. Fixed by uninitializing the handler before
returning the error.
(Bug#31742)
The examined-rows count was not incremented for
const
queries.
(Bug#31700)
Falcon
tables would fail during replication
if ROW-based replication was specified.
(Bug#31671)
The mysql_change_user()
C API
function was subject to buffer overflow.
(Bug#31669)
For SELECT ... INTO OUTFILE
, if the
ENCLOSED BY
string is empty and the
FIELDS TERMINATED BY
string started with a
special character (one of n
,
t
, r
,
b
, 0
,
Z
, or N
), every occurrence
of the character within field values would be duplicated.
(Bug#31663)
SHOW COLUMNS
and DESCRIBE
displayed null
as the column type for a view
with no valid definer. This caused mysqldump
to produce a non-reloadable dump file for the view.
(Bug#31662)
The mysqlbug script did not include the
correct values of CFLAGS
and
CXXFLAGS
that were used to configure the
distribution.
(Bug#31644)
For queries for which loose index scan is applicable, the optimizer could choose the wrong execution plan for correlated subqueries. (Bug#31639)
Queries that include a comparison of an
INFORMATION_SCHEMA
table column to
NULL
caused a server crash.
(Bug#31633)
EXPLAIN EXTENDED
for
SELECT
from
INFORMATION_SCHEMA
tables caused an assertion
failure.
(Bug#31630)
A buffer used when setting variables was not dimensioned to
accommodate the trailing '\0'
byte, so a
single-byte buffer overrun was possible.
(Bug#31588)
For semi-join processing, pullout of functionally dependent tables was not handled transitively. (Bug#31563)
HAVING
could treat lettercase of table
aliases incorrectly if lower_case_table_names
was enabled.
(Bug#31562)
Spurious duplicate-key errors could occur for multiple-row
inserts into an InnoDB
table that activate a
trigger.
(Bug#31540)
When inserting dates into a DATETIME
column
with a Falcon
, the values would automatically
be converted with values between 70 and 99 converted to
1970-1999, and values from 00 to 69 converted to 2000 to 2069.
These dates are now correctly handled.
(Bug#31490)
The length of the result from
IFNULL()
could be calculated
incorrectly because the sign of the result was not taken into
account.
(Bug#31471)
Queries that used the ref
access method or
index-based subquery execution over indexes that have
DECIMAL
columns could fail with an error
Column
.
(Bug#31450)col_name
cannot be
null
InnoDB
now tracks locking and use of tables
by MySQL only after a table has been successfully locked on
behalf of a transaction. Previously, the locked flag was set and
the table in-use counter was updated before checking whether the
lock on the table succeeded. A subsequent failure in obtaining a
lock on the table led to an inconsistent state as the table was
neither locked nor in use.
(Bug#31444)
SELECT 1 REGEX NULL
caused an assertion
failure for debug servers.
(Bug#31440)
INFORMATION_SCHEMA.TABLES
was returning
incorrect information.
(Bug#31381)
DROP USER
caused an increase in memory usage.
(Bug#31347)
TABLESPACE
names within
Falcon
did not support characters outside the
alpha-numeric ASCII character set.
(Bug#31311)
For InnoDB
tables with READ
COMMITTED
isolation level, UPDATE
statements skipped rows locked by another transaction, rather
than waiting for the locks to be released.
(Bug#31310)
For an almost-full MyISAM
table, an insert
that failed could leave the table in a corrupt state.
(Bug#31305)
When dropping Falcon tablespaces the associated tablespace file would not be deleted. (Bug#31296)
myisamchk --unpack could corrupt a table that when unpacked has static (fixed-length) row format. (Bug#31277)
Building a 64-bit binary with support for the
Falcon
storage engine using
gcc on Solaris could fail. See
Section 2.9, “MySQL Installation Using a Source Distribution”, for more information.
(Bug#31268, Bug#33126)
When a TIMESTAMP
with a non-zero time part
was converted to a DATE
value, no warning was
generated. This caused index lookups to assume that this is a
valid conversion and was returning rows that match a comparison
between a TIMESTAMP
value and a
DATE
keypart. Now a warning is generated so
that TIMESTAMP
with a non-zero time part will
not match DATE
values.
(Bug#31221)
If MAKETIME()
returned
NULL
when used in an ORDER
BY
that was evaluated using
filesort
, a server crash could result.
(Bug#31160)
LAST_INSERT_ID()
execution could
be handled improperly in subqueries.
(Bug#31157)
An assertion designed to detect a bug in the
ROLLUP
implementation would incorrectly be
triggered when used in a subquery context with non-cacheable
statements.
(Bug#31156)
When creating a TABLESPACE
that uses the same
name as an existing TABLESPACE
, Falcon would
return Unknown error -103
. MySQL will now
return an error stating that the specified tablespace already
exists.
(Bug#31114)
mysqldump failed to handle databases
containing a ‘-
’ character in the
name.
(Bug#31113)
Starting the server using --read-only
and with
the Event Scheduler enabled caused it to crash.
This issue occurred only when the server had been built with certain nonstandard combinations of configure options.
Dropping a tablespace and specifying an engine type that does not support tablespaces would report a warning. The response has now been updated to report an error. (Bug#31110)
GROUP BY NULL WITH ROLLUP
could cause a
server crash.
(Bug#31095)
A rule to prefer filesort
over an indexed
ORDER BY
when accessing all rows of a table
was being used even if a LIMIT
clause was
present.
(Bug#31094)
REGEXP
operations could cause
a server crash for character sets such as
ucs2
. Now the arguments are converted to
utf8
if possible, to allow correct results to
be produced if the resulting strings contain only 8-bit
characters.
(Bug#31081)
Expressions of the form WHERE
, where the same
column was named both times, could cause a server crash in the
optimizer.
(Bug#31075)col
NOT IN
(col
, ...)
Falcon would fail to compile on FreeBSD. This limitation has now been fixed. (Bug#31045)
Using ORDER BY
with
ARCHIVE
tables caused a server crash.
(Bug#31036)
The MOD()
function and the
%
operator crashed the server for a divisor
less than 1 with a very long fractional part.
(Bug#31019)
Using falcon_serial_log_dir
to set the location
of the Falcon serial log would have no effect.
(Bug#31005)
The LooseScan subquery optimization strategy could produce duplicate rows in query results. (Bug#30993)
A character set introducer followed by a hexadecimal or bit-value literal did not check its argument and could return an ill-formed result for invalid input. (Bug#30986)
CHAR(
did not check its
argument and could return an ill-formed result for invalid
input.
(Bug#30982)str
USING
charset
)
The result from
CHAR(
) did not add a leading 0x00 byte for input
strings with an odd number of bytes.
(Bug#30981)str
USING
ucs2
A cluster restart could sometimes fail due to an issue with table IDs. (Bug#30975)
The GeomFromText()
function
could cause a server crash if the first argument was
NULL
or the empty string.
(Bug#30955)
When invoked with constant arguments,
STR_TO_DATE()
could use a cached
value for the format string and return incorrect results.
(Bug#30942)
GROUP_CONCAT()
returned
','
rather than an empty string when the
argument column contained only empty strings.
(Bug#30897)
A server crash could occur if a stored function that contained a
DROP TEMPORARY TABLE
statement was invoked by
a CREATE TEMPORARY TABLE
statement that
created a table of the same name.
(Bug#30882)
Calling NAME_CONST()
with
non-constant arguments triggered an assertion failure.
Non-constant arguments are now disallowed.
(Bug#30832)
Running ALTER TABLE ... OPTIMIZE PARTITION
on
a Falcon
table, a 'divide by zero' error
would be reported during a server crash.
(Bug#30826)
For a spatial column with a regular
(non-SPATIAL
) index, queries failed if the
optimizer tried to use the index.
(Bug#30825)
INFORMATION_SCHEMA.SCHEMATA
was returning
incorrect information.
(Bug#30795)
On Windows, the pthread_mutex_trylock()
implementation was incorrect. One symptom was that invalidating
the query cache could cause a server crash.
(Bug#30768)
Under some circumstances, CREATE TABLE ...
SELECT
could crash the server or incorrectly report
that the table row size was too large.
(Bug#30736)
Using the MIN()
or
MAX()
function to select one
part of a multi-part key could cause a crash when the function
result was NULL
.
(Bug#30715)
INFORMATION_SCHEMA.VIEWS.VIEW_DEFINITION
was
incorrect for views that were defined to select from other
INFORMATION_SCHEMA
tables.
(Bug#30689)
Issuing an ALTER SERVER
statement to update
the settings for a FEDERATED
server would
cause the mysqld to crash.
(Bug#30671)
The optimizer could ignore ORDER BY
in cases
when the result set is ordered by filesort
,
resulting in rows being returned in incorrect order.
(Bug#30666)
A different execution plan was displayed for
EXPLAIN
than would actually have been used
for the SELECT
because the test of sort keys
for ORDER BY
did not consider keys mentioned
in IGNORE KEYS FOR ORDER BY
.
(Bug#30665)
MyISAM
tables could not exceed 4294967295
(2^32 - 1) rows on Windows.
(Bug#30638)
mysql-test-run.pl could not run
mysqld with root
privileges.
(Bug#30630)
Using GROUP BY
on an expression of the form
caused a server
crash due to incorrect calculation of number of decimals.
(Bug#30587)timestamp_col
DIV
number
The options available to the CHECK TABLE
statement were also allowed in OPTIMIZE TABLE
and ANALYZE TABLE
statements, but caused
corruption during their execution. These options were never
supported for the these statements, and an error is now raised
if you try to apply these options to these statements.
(Bug#30495)
When expanding a *
in a
USING
or NATURAL
join, the
check for table access for both tables in the join was done
using only the grant information of the first table.
(Bug#30468)
A table-access check was performed improperly by
libmysqld
, causing a crash.
(Bug#30329)
Some valid euc-kr
characters having the
second byte in the ranges [0x41..0x5A]
and
[0x61..0x7A]
were rejected.
(Bug#30315)
When loading a dynamic plugin on FreeBSD, the plugin would fail to load. This was due to a build error where the required symbols would be not exported correctly. (Bug#30296)
Setting certain values on a table using a spatial index could cause the server to crash. (Bug#30286)
Some INFORMATION_SCHEMA
tables are intended
for internal use, but could be accessed by using
SHOW
statements.
(Bug#30079)
On some 64-bit systems, inserting the largest negative value
into a BIGINT
column resulted in incorrect
data.
(Bug#30069)
mysqlslap did not properly handle multiple result sets from stored procedures. (Bug#29985)
Running the sqlbench test suite against
Falcon
would cause a crash.
(Bug#29870)
When accessing the statistics in
INFORMATION_SCHEMA.FALCON_DATABASE_IO
, the
information would related only to the Falcon database, not user
tablespaces. The output has been updated to report on all
tablespaces, and the column title has been changed to reflect
the fact that the statistics are now reported by tablespace, not
database.
(Bug#29823)
Whitespace characters other than spaces within XML tags, such as
linefeeds or tabs, caused LOAD XML INFILE
to
skip rows.
(Bug#29752)
configure did not find nss
on some Linux platforms.
(Bug#29658)
Compilation failed on systems where a native
log2()
implementation was unavailable.
(Bug#29640)
Use of the latin2_czech_cs
collation caused a
server crash.
(Bug#29459)
Using two simultaneous connections it was possible to create a
deadlock situation between two different active transactions on
the same Falcon
table. There is no way to
prevent this, but a new parameter,
falcon_lock_timeout
can set the timeout for
deadlocked transactions. The default timeout is 0 (timeouts are
disabled).
(Bug#29452)
The mysql client program now ignores Unicode byte order mark (BOM) characters at the beginning of input files. Previously, it read them and sent them to the server, resulting in a syntax error.
Presence of a BOM does not cause mysql to
change its default character set. To do that, invoke
mysql with an option such as
--default-character-set=utf8
.
(Bug#29323)
Insert information into the same table from multiple threads
could cause duplicate key errors. This was related to the
changes made to allow compatibility with the InnoDB
repeatable-read isolation level. The option,
falcon_innodb_compatibility
, has been renamed
to falcon_consistent_read
, but with the
opposite effect. The default is for this option to be on. When
set to off, the behaviour of Falcon is similar to that in
InnoDB.
(Bug#29151)
For transactional tables, an error during a multiple-table
DELETE
statement did not roll back the
statement.
(Bug#29136)
The log
and
log_slow_queries
system variables were
displayed by SHOW VARIABLES
but could not be
accessed in expressions as @@log
and
@@log_slow_queries
. Also, attempting to set
them with SET
produced an incorrect
Unknown system variable
message. Now these
variables are treated as synonyms for
general_log
and
slow_query_log
, which means that they can be
accessed in expressions and their values can be changed with
SET
.
(Bug#29131)
When loading large data sets using LOAD DATA
INFILE
into a Falcon
table, the
server could crash.
(Bug#29081)
SHOW VARIABLES
did not display the
relay_log
,
relay_log_index
, or
relay_log_info_file
system variables.
(Bug#28893)
Index hints specified in view definitions were ignored when using the view to select from the base table. (Bug#28702)
Views do not have indexes, so index hints do not apply. Use of index hints when selecting from a view is now disallowed. (Bug#28701)
After changing the SQL mode to a restrictive value that would make already-inserted dates in a column be considered invalid, searches returned different results depending on whether the column was indexed. (Bug#28687)
The result from CHAR()
was
incorrectly assumed in some contexts to return a single-byte
result.
(Bug#28550)
Using a temporary table within Falcon that is created in a directory where the path contains a mixture of upper and lower letters would fail. (Bug#28541)
Under heavy load when updating Falcon
tables,
a race condition could occur that would ultimately result in a
crash.
(Bug#28519)
The result of a comparison between VARBINARY
and BINARY
columns differed depending on
whether the VARBINARY
column was indexed.
(Bug#28076)
The metadata in some MYSQL_FIELD
members
could be incorrect when a temporary table was used to evaluate a
query.
(Bug#27990)
It was possible to create a view having a column whose name consisted of an empty string or space characters only. (Bug#27695)
See also Bug#31202
ALTER TABLE
did
not cause the table to be rebuilt.
(Bug#27610)tbl_name
ROW_FORMAT=format_type
Searching a Falcon
table that uses
DATETIME
columns with an index could return
incorrect results.
(Bug#27426)
Removing a partition on a Falcon
table when
there are two tables with the same name, but different case,
would cause a crash during normal shutdown.
(Bug#27425)
Mixing differently cased tables between
MyISAM
and Falcon
tables
would cause a crash.
(Bug#27424)
The ExtractValue()
and
UpdateXML()
functions performed
extremely slowly for large amounts of XML data (greater than 64
KB). These functions now execute approximately 2000 times faster
than previously.
(Bug#27287)
On WIndows, writes to the debug log were using
freopen()
instead of
fflush()
, resulting in slower performance.
(Bug#27099)
Connections from one mysqld server to another
failed on Mac OS X, affecting replication and
FEDERATED
tables.
(Bug#26664)
See also Bug#29083
LOAD DATA INFILE
ran very slowly when reading
large files into partitioned tables.
(Bug#26527)
Threads that were calculating the estimated number of records
for a range scan did not respond to the KILL
statement. That is, if a range
join type is
possible (even if not selected by the optimizer as a join type
of choice and thus not shown by EXPLAIN
), the
query in the statistics
state (shown by the
SHOW PROCESSLIST
) did not respond to the
KILL
statement.
(Bug#25421)
For mysql --show-warnings, warnings were in some cases not displayed. (Bug#25146)
Using CREATE UNIQUE INDEX
on a
Falcon
table where rows contain duplicate
values could result in pending transactions to the table being
deleted.
(Bug#22842)
Creating a Falcon
table with an
auto-increment column that is not indexed as the first column in
a multi-column index would auto0increment. This behavior was
different to the behavior in both MyISAM
and
InnoDB
. Falcon now rejects such tables during
creation in the same way InnoDB does.
(Bug#22564)
For storage engines that do not redefine
handler::index_next_same()
and are capable
of indexes, statements that include a WHERE
clause might select incorrect data.
(Bug#22351)
Creating a new table or dropping a database on a newly created
database or tablespace where the Falcon
engine was used would raise an error.
(Bug#22199)
Using TRUNCATE
on a Falcon
table did not reset the auto-increment counters and used an
inefficient method of deleting existing data.
(Bug#22173)
Creating a DATE
outside the normal range
within a Falcon
table would result in a zero
DATE
value being returned, even though
normally invalid values would be stored correctly in other
storage engines.
(Bug#22168)
Selecting information from a Falcon
table
using a DOUBLE
column with an index would
produce incorrect results.
(Bug#22125)
The readline
library has been updated to
version 5.2. This addresses issues in the
mysql client where history and editing within
the client would fail to work as expected.
(Bug#18431)
Performing a full text search on a table could cause a crash on a 64-bit platforms with certain characteristics. Searches that were known to cause a crash with certain datasets included numerical values and strings where the match string included data enclosed in single or double quotes. (Bug#11392)
mysql stripped comments from statements sent
to the server. Now the --comments
or
--skip-comments
option can be used to control
whether to retain or strip comments. The default is
--skip-comments
.
(Bug#11230, Bug#26215)
Executing DISABLE KEYS
and ENABLE
KEYS
on a non-empty table would cause the size of the
index file for the table to grow considerable. This was because
the DISABLE KEYS
operation would only mark
the existing index, without deleting the index blocks. The
ENABLE KEYS
operation would re-create the
index, adding new blocks, while the previous index blocks would
remain. Existing indexes are now dropped and recreated when the
ENABLE KEYS
statement is executed.
(Bug#4692)
Functionality added or changed:
Incompatible Change:
Aliases for wildcards (as in SELECT t.* AS 'alias' FROM
t
) are no longer accepted and result in an error.
Previously, such aliases were ignored silently.
(Bug#27249)
Sinhala collations utf8_sinhala_ci
and
ucs2_sinhala_ci
were added for the
utf8
and ucs2
character
sets.
(Bug#26474)
If the value of the --log-warnings
option is
greater than 1, the server now writes access-denied errors to
the error log (for example, if a client username or password is
incorrect).
(Bug#25822)
Added the PARAMETERS
table to
INFORMATION_SCHEMA
. The
PARAMETERS
table provides information about
stored function and procedure parameters, and about return
values for stored functions.
Bugs fixed:
Incompatible Change:
DROP TABLE
now is allowed only if you have
acquired a WRITE
lock with LOCK
TABLES
, or if you hold no locks, or if the table is a
TEMPORARY
table.
Previously, if other tables were locked, you could drop a table with a read lock or no lock, which could lead to deadlocks between clients. The new stricter behavior means that some usage scenarios will fail when previously they did not. (Bug#25858)
Incompatible Change:
GRANT
and REVOKE
statements now cause an implicit commit, and thus are prohibited
within stored functions and triggers.
(Bug#21975, Bug#21422, Bug#17244)
MySQL Cluster:
Adding a new TINYTEXT
column to an
NDB
table which used COLUMN_FORMAT =
DYNAMIC
, and when binary logging was enabled, caused
all cluster mysqld processes to crash.
(Bug#30213)
MySQL Cluster:
After adding a new column of one of the TEXT
or BLOB
types to an NDB
table which used COLUMN_FORMAT = DYNAMIC
, it
was no longer possible to access or drop the table using SQL.
(Bug#30205)
The server crashed on optimization of queries that compared an
indexed DECIMAL
column with a string value.
(Bug#32262)
The server crashed on optimizations that used the range
checked for each record
access method.
(Bug#32229)
When comparing a BLOB
value that was null,
memory corruption could occur casuing the server to crash.
(Bug#32191)
Deleting a large number of records could sometimes take a significant amount of time. (Bug#27946)
Several buffer-size system variables were either being handled incorrectly for large values (for settings larger than 4GB, they were truncated to values less than 4GB without a warning), or were limited unnecessarily to 4GB even on 64-bit systems. The following changes were made:
For key_buffer_size
, values larger than
4GB are allowed on 64-bit platforms.
For join_buffer_size
,
sort_buffer_size
, and
myisam_sort_buffer_size
, values larger
than 4GB are allowed on 64-bit platforms (except Windows,
for which large values are truncated to 4GB with a warning).
In addition, settings for read_buffer_size
and read_rnd_buffer_size
are limited to 2GB
on all platforms. Larger values are truncated to 2GB with a
warning.
(Bug#5731, Bug#29419, Bug#29446)
Functionality added or changed:
Mac OS X (Intel) support has been added. To build on Mac OS X
from the repository sources you must have the most recent
versions of bison
,
automake
, autoconf
and
libtool
installed.
There are known issues with the Falcon on Mac OS X build. (Bug#30564)
The Falcon record cache parameters have been altered. The
falcon_max_record_memory
and
falcon_min_record_memory
are no longer
supported.
Instead, the falcon_record_memory_max
,
falcon_record_scavenge_threshold
,
falcon_record_scavenge_floor
and
falcon_inital_allocation
parameters are now
used to control the caching of records in memory within Falcon.
See Section 12.6.2, “Configuration Parameters”.
(Bug#30083)
64-bit Windows support.
Support for tablespaces.
New performance settings, falcon_log_windows
,
falcon_index_chill_threshold
, and
falcon_record_chill_threshold
.
The option falcon_disable_fsync
has been added.
If set to true, then the periodic fsync operation is disabled.
The option falcon_initial_allocation
has been
added to control the initial size of a Falcon tablespace on
disk.
Bugs fixed:
An assertion could be thrown during high number of concurrent
updates of BLOB
fields.
(Bug#30463)
When loading large data sets into a Falcon table mysqld could crash. An Out of memory error will now be raised in this situation. (Bug#30251, Bug#30074)
Falcon would incorrectly allow creation of two tables with the same name but different case sensitivity, without raising an error, but treat the two tables as the same during further queries. . (Bug#30210)
Updating a large table without an index would lock all the records during a transaction and unlock the records individually. (Bug#30124)
Creating a tablespace with a unique name but using the same datafile as an existing tablespace results in the re-initialization of the tablespace and the loss of the data contained in it. Falcon will now report an error if you the datafile already exists. (Bug#29511)
Using SELECT
on a table that uses two
INT
columns with a single index would fail to
return rows that queried both columns and complex comparison
operators.
(Bug#29319)
Falcon could occasionally report a problem with a duplicate key
error during INSERT
when inserting the same
data into a unique column on two or more connections
simultaneously.
(Bug#29240)
Inserting into a table with a unique index simultaneously on two connections in a way that would cause a deadlock would cause MySQL to hang. The deadlock situation is now identified and an error will be raised. (Bug#29206)
Wide DECIMAL
columns would show rounding
errors during SELECT
.
(Bug#29201)
Some Falcon variables were marked as status variables. (Bug#29169)
Accessing an INFORMATION_SCHEMA
table
generated by Falcon, when Falcon has not been enabled would
cause mysqld to crash.
(Bug#29014)
For debug builds, the server crashed when inserting a negated
DECIMAL
value of maximum precision (65
digits), such as for INSERT INTO ... SELECT -col_val
...
(Bug#28810)
Accessing data within DECIMAL
columns wider
than 18 digits would cause a crash.
(Bug#28725)
mysqld would crash after a high number of
ALTER TABLE
, INSERT
and
UPDATE
statements.
(Bug#28515, Bug#22154)
Unique indexes on VARCHAR
columns are not
identified correctly.
(Bug#28500)
Under certain situations the Falcon tables and log could become corrupt and prevent recovery from a crashed version of the files. (Bug#28351)
The value for
FALCON_SYSTEM_MEMORY_SUMMARY.TOTAL_SPACE
in
INFORMATION_SCHEMA
would be reported
incorrectly.
(Bug#28197)
Searching for rows within a table with some non-western
character sets would fail to return the right results if the
SELECT
relied on an index.
(Bug#27697)
Inserting large numbers of identical columns into a table,
followed by a SELECT
or
UPDATE
could cause a hang or crash.
(Bug#27277)
Loading certain data sets through a direct import could cause index problems and crash. (Bug#26930)
DECIMAL
columns with large widths did not
work, either during INSERT
or
SELECT
. .
(Bug#26607)
DELETE
statements could cause a crash when
many simultaneous threads are running.
(Bug#26475)
Falcon would fail to build under Mac OS X/Intel. A preliminary patch is available to allow building under Mac OS X/Intel only (PowerPC support is not yet available). Note that Mac OS X/Intel is still an unsupported platform. (Bug#26466)
Queries could fail with a Can't find record in
...
error.
(Bug#26328)
Under certain situations, shutting down MySQL using mysqladmin could cause Falcon to corrupt the database tables and fail to restart properly. (Bug#26296)
Searches for accented characters in a UTF8 table fail if an index exists for the column. (Bug#26057)
Searches using LIKE
on a UTF8 table fail if
the search relies an indexed column.
(Bug#24921)
Searches for data on a partial index for a column using the UTF8 character set would fail. (Bug#24858)
Searches for data using exotic collation/character sets fail if the search relies on an indexed column. (Bug#23689)
Inserting rows to a table with a unique index where the unique index value is identical on two separate connections would block the second transaction. (Bug#22847)
Renaming a database would raise error ERROR 1030
(HY000): Got error 157 from storage engine
.
(Bug#22182)
Large inserts to a table within a single transaction trigger high memory usage and may ultimately crash. (Bug#22169)
Renaming tables to or from Falcon tablespaces would raise an error. (Bug#22155)
This was an internal release only, and no binaries were published.
Functionality added or changed:
SELECT ... FOR UPDATE
is now supported.
Uncommitted record scavenging has been implemented.
Performance diagnostics are available through
INFORMATION_SCHEMA
.
Bugs fixed:
Using SELECT ... FOR UPDATE
and
ROLLBACK
could cause
mysqld
to hang indefinitely.
(Bug#28165)
Concurrent updates on two different connections could lead to an assertion failure. (Bug#28090)
Updating a row within a table that has a unique compound index to a non-unique value would not raise an error. (Bug#27997)
Rolling back an inserted row while accessing the same on a different connection would cause a crash. (Bug#27993)
Creating a table with a 19 digit DECIMAL
column would cause incorrect data to be stored. This is due to
current limitation in Falcon where you cannot create a table
with a column with greater than 18 digits precision (i.e.
DECIMAL(18,9)
). Creating a column with larger
than this specification will fail and raise an error.
(Bug#27962)
Executing INSERT INTO ... SELECT FROM
could
cause a crash on large data sets.
(Bug#27951)
Inserting data into the same table on two different connections with autocommit disabled would cause a crash. (Bug#27895)
Creating a Falcon table immediately after creating a new database could cause a crash. (Bug#27768)
Executing SELECT ... FOR UPDATE
in a second
connection on a newly created and populated table could cause a
crash.
(Bug#27767)
Continually updating a BLOB
column would
cause MySQL server to crash.
(Bug#27719)
Using a trigger on an UPDATE
to a Falcon
table when autocommit is disabled would cause MySQL server to
crash.
(Bug#27574)
Interrupting a stored procedure during execution could cause a crash. (Bug#27539)
Opening the same database with Falcon tables on a different connection could cause a crash. (Bug#27428)
Using ROLLBACK
after a
DELETE
does not restore the deleted row.
(Bug#27357)
Two simultaneous SELECT ... FOR UPDATE
statements with READ-COMMITTED
isolation
level would result in the wrong error message being returned.
(Bug#26871)
Row insertions to a table with long VARCHAR
columns and large compound indexes would cause MySQL to crash.
(Bug#26850)
Falcon could consume large amounts of memory during a high
number of continuous INSERT
statements.
(Bug#26843)
Updating a partitioned table in two sessions simultaneously would cause MySQL to crash. (Bug#26828)
Locking between sessions when using SELECT ... FOR
UPDATE
would not work.
(Bug#26826)
Tables with UNIQUE
key constraints would not
be enforced.
(Bug#26803)
When updating a table with a unique key constraint the constraint would not be enforced. (Bug#26802)
Searching for records in a table with a
DECIMAL(6,6)
column would fail to find the
value.
(Bug#26469)
Rows with a numeric column may fail to find records with zero values. (Bug#26468)
Retrieving rows from a table that used an index would sometimes fail to return the row. (Bug#26452)
Continue handlers in stored procedures could cause a crash. (Bug#26433)
Tables with a long multi-column index may fail to find a record
for UPDATE
.
(Bug#26420)
Updating BLOB
columns could result in a
crash.
(Bug#26324)
Deleting a large quantity of rows in a single table may result
in ERROR 1020
.
(Bug#26055)
A DROP TABLE
statement on a table created
using CREATE TABLE ... SELECT ...
crashed the
server.
(Bug#25564)
Random updates of LONG VARCHAR
columns would
fail.
(Bug#23818)
Running SELECT
after a changing the table
contents does not result in a new data set.
(Bug#22181)
Using ALTER
with interleaving transactions
triggers mysqld
to crash.
(Bug#22165)
An overview of which features were added in MySQL 5.2 can be found here: Section 1.5.1, “What's New in MySQL 6.0”.
For a full list of changes, please refer to the changelog sections for each individual 5.2.x release.
This is a new Alpha development release, fixing recently discovered bugs.
This Alpha release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Network (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
The INFORMATION_SCHEMA.COLUMNS
table now has
STORAGE
and FORMAT
columns. For NDB
tables,
STORAGE
indicates whether a column is stored
on disk or memory, and FORMAT
indicates the
column storage format (FIXED
,
DYNAMIC
, or DEFAULT
).
The INFORMATION_SCHEMA.STATISTICS
table now
has an INDEX_COMMENT
column to indicate any
comment string provided for the column. The SHOW
INDEX
statement now displays an
Index_comment
column that provides the same
information.
It is now possible to control whether fixed-width or
variable-width storage is used for a given column of an
NDB
table by means of the
COLUMN_FORMAT
specifier as part of the
column's definition in a CREATE TABLE
or
ALTER TABLE
statement.
It is also possible to control whether a given column of an
NDB
table is stored in memory or on disk,
using the STORAGE
specifier as part of the
column's definition in a CREATE TABLE
or
ALTER TABLE
statement.
For permitted values and other information about
COLUMN_FORMAT
and STORAGE
,
see Section 11.1.10, “CREATE TABLE
Syntax”.
The LOAD XML INFILE
statement was added. This
statement makes it possible to read data directly from XML files
into database tables. For more information, see
Section 11.2.6, “LOAD XML
Syntax”.
Bugs fixed:
Use of the latin2_czech_cs
collation caused a
server crash.
(Bug#29459)
This is a new Alpha development release, fixing recently discovered bugs.
This Alpha release, as any other pre-production release, should not be installed on production level systems or systems with critical data. It is good practice to back up your data before installing any new version of software. Although MySQL has worked very hard to ensure a high level of quality, protect your data by making a backup as you would for any software beta release. Please refer to our bug database at http://bugs.mysql.com/ for more details about the individual bugs fixed in this version.
This section documents all changes and bug fixes that have been applied since the last official MySQL release. If you would like to receive more fine-grained and personalized update alerts about fixes that are relevant to the version and features you use, please consider subscribing to MySQL Network (a commercial MySQL offering). For more details please see http://www.mysql.com/products/enterprise/advisors.html.
Functionality added or changed:
The syntax for the LOCK TABLES
statement has
been extended to support transactional table locks that do not
commit transactions automatically. Following LOCK
TABLES ... IN SHARE MODE
or LOCK TABLES ...
IN EXCLUSIVE MODE
, you can access tables not mentioned
in the LOCK TABLES
statement. You can now
also issue these extended LOCK TABLES
statements many times in succession, adding additional tables to
the locked set, and without unlocking any tables that were
locked previously. When using LOCK TABLES
with IN SHARE MODE
or IN EXCLUSIVE
MODE
, tables are not unlocked until the transaction is
committed.
The behavior of LOCK TABLES
when not using
IN SHARE MODE
or IN EXCLUSIVE
MODE
remains unchanged.
A new SQL function,
WEIGHT_STRING()
, returns the
weight string for an input string. The weight string represents
the sorting and comparison value of the input string.
The maximum length of table comments was extended from 60 to 2048 characters. The maximum length of column comments was extended from 255 to 1024 characters. Index definitions now can include a comment of up to 1024 characters.
Parser performance was improved for identifier scanning and conversion of ASCII string literals.
Bugs fixed:
Bugs fixed:
MySQL would fail with an assertion on startup. (Bug#25835)
Functionality added or changed:
Performance improvements: thread bottlenecks have been reduced when a larger number of parallel auto-commit threads executed a trivial query in a hard loop.
Bugs fixed:
Falcon compound primary key problem. (Bug#25828)
Assertion when killing a CREATE TABLE ...
SELECT
statement.
(Bug#25565)
A DROP TABLE
statement on a table created
using CREATE TABLE ... SELECT ...
crashed the
server.
(Bug#25564)
Crash if create index on nullable utf8
column.
(Bug#25555)
Between fails with Unicode field. (Bug#24511)
Functionality added or changed:
A full implementation of SQLForeignKeys based on the information available from INFORMATION_SCHEMA in 5.0 and later versions of the server has been implemented.
Bugs fixed:
SQLGetInfo()
reported characters for
SQL_SPECIAL_CHARACTERS
that were not encoded
correctly.
(Bug#33130)
Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug#31165)
Reading a TEXT
column that had been used to
store UTF8 data would result in the wrong information being
returned during a query.
(Bug#28617)
SQLForeignKeys
would return an empty string
for the schema columns instead of NULL
.
(Bug#19923)
Evaluating a simple numeric expression when using the OLEDB for ODBC provider and ADO would return an error, instead of the result. (Bug#10128)
Adding or updating a row using SQLSetPos()
on a result set with aliased columns would fail.
(Bug#6157)
MySQL Connector/ODBC 5.1.1-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the first beta (feature-complete) release of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)
Keep in mind that this is a beta release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data.
Includes changes from Connector/ODBC 3.51.21 and 3.51.22.
Built using MySQL 5.0.52.
Platform specific notes:
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
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.
The installer for 64-bit Windows installs both the 32-bit and 64-bit driver. Please note that Microsoft does not yet supply a 64-bit bridge from ADO to ODBC.
Functionality added or changed:
Incompatible Change: Replaced myodbc3i (now myodbc-installer) with Connector/ODBC 5.0 version.
Incompatible Change: Removed monitor (myodbc3m) and dsn-editor (myodbc3c).
Incompatible Change:
Disallow SET NAMES
in initial statement and
in executed statements.
A wrapper for the
SQLGetPrivateProfileStringW()
function,
which is required for Unicode support, has been created. This
function is missing from the unixODBC driver manager.
(Bug#32685)
Added MSI installer for Windows 64-bit. (Bug#31510)
Implemented support for SQLCancel()
.
(Bug#15601)
Removed non-threadsafe configuration of the driver. The driver is now always built against the threadsafe version of libmysql.
Implemented native Windows setup library
Replaced the internal library which handles creation and loading of DSN information. The new library, which was originally a part of Connector/ODBC 5.0, supports Unicode option values.
The Windows installer now places files in a subdirectory of the
Program Files
directory instead of the
Windows system directory.
Bugs fixed:
The SET NAMES
statement has been disabled
because it causes problems in the ODBC driver when determining
the current client character set.
(Bug#32596)
SQLDescribeColW
returned UTF-8 column as
SQL_VARCHAR
instead of
SQL_WVARCHAR
.
(Bug#32161)
ADO was unable to open record set using dynamic cursor. (Bug#32014)
ADO applications would not open a RecordSet
that contained a DECIMAL
field.
(Bug#31720)
Memory usage would increase considerably. (Bug#31115)
SQLSetPos
with SQL_DELETE
advances dynamic cursor incorrectly.
(Bug#29765)
Using an ODBC prepared statement with bound columns would produce an empty result set when called immediately after inserting a row into a table. (Bug#29239)
ADO Not possible to update a client side cursor. (Bug#27961)
Recordset Update()
fails when using
adUseClient
cursor.
(Bug#26985)
Connector/ODBC would fail to connect to the server if the password contained certain characters, including the semicolon and other punctuation marks. (Bug#16178)
Fixed SQL_ATTR_PARAM_BIND_OFFSET
, and fixed
row offsets to work with updatable cursors.
SQLSetConnectAttr()
did not clear previous
errors, possibly confusing SQLError()
.
SQLError()
incorrectly cleared the error
information, making it unavailable from subsequent calls to
SQLGetDiagRec()
.
NULL pointers passed to SQLGetInfo()
could
result in a crash.
SQL_ODBC_SQL_CONFORMANCE
was not handled by
SQLGetInfo()
.
SQLCopyDesc()
did not correctly copy all
records.
Diagnostics were not correctly cleared on connection and environment handles.
This release is the first of the new 5.1 series and is suitable for use with any MySQL server version since MySQL 4.1, including MySQL 5.0, 5.1, and 6.0. (It will not work with 4.0 or earlier releases.)
Keep in mind that this is a alpha release, and as with any other pre-production release, caution should be taken when installing on production level systems or systems with critical data. Not all of the features planned for the final Connector/ODBC 5.1 release are implemented.
Functionality is based on Connector/ODBC 3.51.20.
Platform specific notes:
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
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.
There are no installer packages for Microsoft Windows x64 Edition.
Functionality added or changed:
Added support for Unicode functions
(SQLConnectW
, etc).
Added descriptor support (SQLGetDescField
,
SQLGetDescRec
, etc).
Added support for SQL_C_WCHAR
.
Development on Connector/ODBC 5.0.x has ceased. New features and functionality will be incorporated into Connector/ODBC 5.1. See Section 25.1.2.1, “Connector/ODBC Roadmap”.
Bugs fixed:
Functionality added or changed:
Added support for ODBC v2 statement options using attributes.
Driver now builds and is partially tested under Linux with the iODBC driver manager.
Bugs fixed:
Connection string parsing for DSN-less connections could fail to identify some parameters. (Bug#25316)
Updates of MEMO
or TEXT
columns from within Microsoft Access would fail.
(Bug#25263)
Transaction support has been added and tested. (Bug#25045)
Internal function, my_setpos_delete_ignore()
could cause a crash.
(Bug#22796)
Fixed occasional mis-handling of the
SQL_NUMERIC_C
type.
Fixed the binding of certain integer types.
Connector/ODBC 5.0.10 is the sixth BETA release.
Functionality added or changed:
Significant performance improvement when retrieving large text
fields in pieces using SQLGetData()
with a
buffer smaller than the whole data. Mainly used in Access when
fetching very large text fields.
(Bug#24876)
Added initial unicode support in data and metadata. (Bug#24837)
Added initial support for removing braces when calling stored procedures and retrieving result sets from procedure calls. (Bug#24485)
Added loose handling of retrieving some diagnostic data. (Bug#15782)
Added wide-string type info for
SQLGetTypeInfo()
.
Bugs fixed:
Connector/ODBC 5.0.9 is the fifth BETA release.
This is an implementation and testing release, and is not designed for use within a production environment.
Functionality added or changed:
Added support for column binding as SQL_NUMBERIC_STRUCT.
Added recognition of SQL_C_SHORT
and
SQL_C_TINYINT
as C types.
Bugs fixed:
Fixed wildcard handling of and listing of catalogs and tables in
SQLTables
.
Added limit of display size when requested via
SQLColAttribute
/SQL_DESC_DISPLAY_SIZE
.
Fixed buffer length return for SQLDriverConnect.
ODBC v2 behaviour in driver now supports ODBC v3 date/time types (since DriverManager maps them).
Catch use of SQL_ATTR_PARAMSET_SIZE
and
report error until we fully support.
Fixed statistics to fail if it couldn't be completed.
Corrected retrieval multiple field types bit and blob/text.
Fixed SQLGetData to clear the NULL indicator correctly during multiple calls.
Connector/ODBC 5.0.8 is the fourth BETA release.
This is an implementation and testing release, and is not designed for use within a production environment.
Functionality added or changed:
Also made SQL_DESC_NAME
only fill in the name
if there was a data pointer given, otherwise just the length.
Fixed display size to be length if max length isn’t available.
Made distinction between
CHAR
/BINARY
(and VAR
versions).
Wildcards now support escaped chars and underscore matching (needed to link tables with underscores in access).
Bugs fixed:
Fixed binding using SQL_C_LONG
.
Fixed using wrong pointer for
SQL_MAX_DRIVER_CONNECTIONS
in
SQLGetInfo
.
Set default return to SQL_SUCCESS
if nothing
is done for SQLSpecialColumns
.
Fixed MDiagnostic to use correct v2/v3 error codes.
Allow SQLDescribeCol to be called to retrieve the length of the column name, but not the name itself.
Length now used when handling bind parameter (needed in
particular for SQL_WCHAR
) - this enables
updating char data in MS Access.
Updated retrieval of descriptor fields to use the right pointer types.
Fixed hanlding of numeric pointers in SQLColAttribute.
Fixed type returned for MYSQL_TYPE_LONG
to
SQL_INTEGER
instead of
SQL_TINYINT
.
Fix size return from SQLDescribeCol
.
Fixed string length to chars, not bytes, returned by SQLGetDiagRec.
Connector/ODBC 5.0.7 is the third BETA release.
This is an implementation and testing release, and is not designed for use within a production environment.
Functionality added or changed:
Added support for SQLStatistics
to
MYODBCShell
.
Improved trace/log.
Bugs fixed:
SQLBindParameter now handles SQL_C_DEFAULT
.
Corrected incorrect column index within
SQLStatistics
. Many more tables can now be
linked into MS Access.
Fixed SQLDescribeCol
returning column name
length in bytes rather than chars.
Connector/ODBC 5.0.6 is the second BETA release.
This is an implementation and testing release, and is not designed for use within a production environment.
Features, limitations and notes on this release
Connector/ODBC supports both User
and
System
DSNs.
Installation is provided in the form of a standard Microsoft System Installer (MSI).
You no longer have to have Connector/ODBC 3.51 installed before installing this version.
Bugs fixed:
You no longer have to have Connector/ODBC 3.51 installed before installing this version.
Connector/ODBC supports both User
and
System
DSNs.
Installation is provided in the form of a standard Microsoft System Installer (MSI).
Connector/ODBC 5.0.5 is the first BETA release.
This is an implementation and testing release, and is not designed for use within a production environment.
You no longer have to have Connector/ODBC 3.51 installed before installing this version.
Bugs fixed:
You no longer have to have Connector/ODBC 3.51 installed before installing this version.
This is an implementation and testing release, and is not designed for use within a production environment.
Features, limitations and notes on this release:
The following ODBC API functions have been added in this release:
SQLBindParameter
SQLBindCol
Connector/ODBC 5.0.2 was an internal implementation and testing release.
Features, limitations and notes on this release:
Connector/ODBC 5.0 is Unicode aware.
Connector/ODBC is currently limited to basic applications. ADO applications and Microsoft Office are not supported.
Connector/ODBC must be used with a Driver Manager.
The following ODBC API functions are implemented:
SQLAllocHandle
SQLCloseCursor
SQLColAttribute
SQLColumns
SQLConnect
SQLCopyDesc
SQLDisconnect
SQLExecDirect
SQLExecute
SQLFetch
SQLFreeHandle
SQLFreeStmt
SQLGetConnectAttr
SQLGetData
SQLGetDescField
SQLGetDescRec
SQLGetDiagField
SQLGetDiagRec
SQLGetEnvAttr
SQLGetFunctions
SQLGetStmtAttr
SQLGetTypeInfo
SQLNumResultCols
SQLPrepare
SQLRowcount
SQLTables
The following ODBC API function are implemented, but not yet support all the available attributes/options:
SQLSetConnectAttr
SQLSetDescField
SQLSetDescRec
SQLSetEnvAttr
SQLSetStmtAttr
Platform specific notes:
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
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.
There are no installer packages for Microsoft Windows x64 Edition.
Bugs fixed:
Connector/ODBC would incorrectly return
SQL_SUCCESS
when checking for distributed
transaction support.
(Bug#32727)
When using unixODBC or directly linked applications where the
thread level is set to less than 3 (within
odbcinst.ini
), a thread synchronization
issue would lead to an application crash. This was because
SQLAllocStmt()
and
SQLFreeStmt()
did not synchronize access to
the list of statements associated with a connection.
(Bug#32587)
Cleaning up environment handles in multithread environments could result in a five (or more) second delay. (Bug#32366)
Renaming an existing DSN entry would create a new entry with the new name without deleting the old entry. (Bug#31165)
Setting the default database using the
DefaultDatabase
property of an ADO
Connection
object would fail with the error
Provider does not support this property
. The
SQLGetInfo()
returned the wrong value for
SQL_DATABASE_NAME
when no database was
selected.
(Bug#3780)
Functionality added or changed:
The workaround for this bug was removed due to the fixes in MySQL Server 5.0.48 and 5.1.21.
This regression was introduced by Bug#10491
Bugs fixed:
The English
locale would be used when
formatting floating point values. The C
locale is now used for these values.
(Bug#32294)
When accessing information about supported operations, the
driver would return incorrect information about the support for
UNION
.
(Bug#32253)
Unsigned integer values greater than the maximum value of a signed integer would be handled incorrectly. (Bug#32171)
The wrong result was returned by SQLGetData()
when the data was an empty string and a zero-sized buffer was
specified.
(Bug#30958)
Added the FLAG_COLUMN_SIZE_S32
option to
limit the reported column size to a signed 32-bit integer. This
option is automatically enabled for ADO applications to provide
a work around for a bug in ADO.
(Bug#13776)
Bugs fixed:
When using a rowset/cursor and add a new row with a number of
fields, subsequent rows with fewer fields will include the
original fields from the previous row in the final
INSERT
statement.
(Bug#31246)
Uninitiated memory could be used when C/ODBC internally calls
SQLGetFunctions()
.
(Bug#31055)
The wrong SQL_DESC_LITERAL_PREFIX
would be
returned for date/time types.
(Bug#31009)
The wrong COLUMN_SIZE
would be returned by
SQLGetTypeInfo
for the TIME columns
(SQL_TYPE_TIME
).
(Bug#30939)
Clicking outside the character set selection box when configuring a new DSN could cause the wrong character set to be selected. (Bug#30568)
Not specifying a user in the DSN dialog would raise a warning even though the parameter is optional. (Bug#30499)
SQLSetParam()
caused memory allocation errors
due to driver manager's mapping of deprecated functions (buffer
length -1).
(Bug#29871)
When using ADO, a column marked as
AUTO_INCREMENT
could incorrectly report that
the column allowed NULL
values. This was dur
to an issue with NULLABLE
and
IS_NULLABLE
return values from the call to
SQLColumns()
.
(Bug#26108)
Connector/ODBC would return the wrong the error code when the
server disconnects the active connection because the configured
wait_timeout
has expired. Previously it would
return HY000
. Connector/ODBC now correctly
returns an SQLSTATE
of
08S01
.
(Bug#3456)
Bugs fixed:
Using FLAG_NO_PROMPT
doesn't suppress the
dialogs normally handled by SQLDriverConnect
.
(Bug#30840)
The specified length of the username and authentication
parameters to SQLConnect()
were not being
honored.
(Bug#30774)
The wrong column size was returned for binary data. (Bug#30547)
SQLGetData()
will now always return
SQL_NO_DATA_FOUND
on second call when no data
left, even if requested size is 0.
(Bug#30520)
SQLGetConnectAttr()
did not reflect the
connection state correctly.
(Bug#14639)
Removed checkbox in setup dialog for
FLAG_FIELD_LENGTH
(identified as
Don't Optimize Column Width
within the GUI
dialog), which was removed from the driver in 3.51.18.
Connector/ODBC 3.51.19 fixes a specific issue with the 3.51.18 release. For a list of changes in the 3.51.18 release, see Section C.3.20, “Changes in MySQL Connector/ODBC 3.51.18 (08 August 2007)”.
Functionality added or changed:
Because of Bug#10491 in the server, character string results
were sometimes incorrectly identified as
SQL_VARBINARY
. Until this server bug is
corrected, the driver will identify all variable-length strings
as SQL_VARCHAR
.
Platform specific notes:
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
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.
Binary packages for Sun Solaris are now available as
PKG
packages.
Binary packages as disk images with installers are now available for Mac OS X.
A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.
Functionality added or changed:
When connecting to a specific database when using a DSN, the
system tables from the mysql
database are no
longer also available. Previously, tables from the mysql
database (catalog) were listed as SYSTEM
TABLES
by SQLTables()
even when a
different catalog was being queried.
(Bug#28662)
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 Connector/ODBC driver. The installer also fixes the situation where the necessary drivers would bge installed local to the user, not globally. (Bug#15326, Bug#10444)
Connector/ODBC now supports batched statements. In order to
enable cached statement support you must switch enable the
batched statement option
(FLAG_MULTI_STATEMENTS
, 67108864, or
Allow multiple statements within a GUI
configuration). Be aware that batched statements create an
increased chance of SQL injection attacks and you must ensure
that your application protects against this scenario.
(Bug#7445)
The SQL_ATTR_ROW_BIND_OFFSET_PTR
is now
supported for row bind offsets.
(Bug#6741)
The TRACE
and TRACEFILE
DSN options have been removed. Use the ODBC driver manager trace
options instead.
Bugs fixed:
When using a table with multiple TIMESTAMP
columns, the final TIMESTAMP
column within
the table definition would not be updateable. Note that there is
still a limitation in MySQL server regarding multiple
TIMESTAMP
columns . (Bug#9927)
(Bug#30081)
Fixed an issue where the myodbc3i would
update the the user ODBC configuration file
(~/Library/ODBC/odbcinst.ini
) instead of
the system /Library/ODBC/odbcinst.ini
. This
was caused because myodbc3i was not honouring
the s
and u
modifiers for
the -d
command line option.
(Bug#29964)
Getting table metadata (through the
SQLColumns()
would fail, returning a bad
table definition to calling applications.
(Bug#29888)
DATETIME
column types would return
FALSE
in place of
SQL_SUCCESS
when requesting the column type
information.
(Bug#28657)
The SQL_COLUMN_TYPE
,
SQL_COLUMN_DISPLAY
and
SQL_COLUMN_PRECISION
values would be returned
incorrectly by SQLColumns()
,
SQLDescribeCol()
and
SQLColAttribute()
when accessing character
columns, especially those generated through
concat()
. The lengths returned should now
conform to the ODBC specification. The
FLAG_FIELD_LENGTH
option no longer has any
affect on the results returned.
(Bug#27862)
Obtaining the length of a column when using a character set for
the connection of utf8
would result in the
length being returned incorrectly.
(Bug#19345)
The SQLColumns()
function could return
incorrect information about TIMESTAMP
columns, indicating that the field was not nullable.
(Bug#14414)
The SQLColumns()
function could return
incorrect information about AUTO_INCREMENT
columns, indicating that the field was not nullable.
(Bug#14407)
A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.
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.
BIT(n)
columns are now treated as
SQL_BIT
data where n = 1
and binary data where n > 1
.
The wrong value from SQL_DESC_LITERAL_SUFFIX
was returned for binary fields.
The SQL_DATETIME_SUB
column in SQLColumns()
was not correctly set for date and time types.
The value for SQL_DESC_FIXED_PREC_SCALE
was
not returned correctly for values in MySQL 5.0 and later.
The wrong value for SQL_DESC_TYPE
was
returned for date and time types.
SQLConnect()
and
SQLDriverConnect()
were rewritten to
eliminate duplicate code and ensure all options were supported
using both connection methods.
SQLDriverConnect()
now only requires the
setup library to be present when the call requires it.
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
Binary packages as disk images with installers are now available for Mac OS X.
Binary packages for Sun Solaris are now available as
PKG
packages.
The wrong value for DECIMAL_DIGITS
in
SQLColumns()
was reported for
FLOAT
and DOUBLE
fields,
as well as the wrong value for the scale parameter to
SQLDescribeCol()
, and the
SQL_DESC_SCALE
attribute from
SQLColAttribute()
.
The SQL_DATA_TYPE
column in
SQLColumns()
results did not report the
correct value for date and time types.
Platform specific notes:
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
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.
Binary packages for Sun Solaris are now available as
PKG
packages.
Binary packages as disk images with installers are now available for Mac OS X.
A binary package without an installer is available for Microsoft Windows x64 Edition. There are no installer packages for Microsoft Windows x64 Edition.
Functionality added or changed:
It is now possible to specify a different character set as part
of the DSN or connection string. This must be used instead of
the SET NAMES
statement. You can also
configure the character set value from the GUI configuration.
(Bug#9498, Bug#6667)
Fixed calling convention ptr and wrong free in myodbc3i, and fixed the null terminating (was only one, not two) when writing DSN to string.
Dis-allow NULL ptr for null indicator when calling SQLGetData() if value is null. Now returns SQL_ERROR w/state 22002.
The setup library has been split into its own RPM package, to allow installing the driver itself with no GUI dependencies.
Bugs fixed:
myodbc3i
did not correctly format driver
info, which could cause the installation to fail.
(Bug#29709)
Connector/ODBC crashed with Crystal Reports due to a rproblem
with SQLProcedures()
.
(Bug#28316)
Fixed a problem where the GUI would crash when configuring or removing a System or User DSN. (Bug#27315)
Fixed error handling of out-of-memory and bad connections in catalog functions. This might raise errors in code paths that had ignored them in the past. (Bug#26934)
For a stored procedure that returns multiple result sets, Connector/ODBC returned only the first result set. (Bug#16817)
Calling SQLGetDiagField
with
RecNumber 0, DiagIdentifier NOT 0
returned
SQL_ERROR
, preventing access to diagnostic
header fields.
(Bug#16224)
Added a new DSN option
(FLAG_ZERO_DATE_TO_MIN
) to retrieve
XXXX-00-00
dates as the minimum allowed ODBC
date (XXXX-01-01
). Added another option
(FLAG_MIN_DATE_TO_ZERO
) to mirror this but
for bound parameters. FLAG_MIN_DATE_TO_ZERO
only changes 0000-01-01
to
0000-00-00
.
(Bug#13766)
If there was more than one unique key on a table, the correct
fields were not used in handling SQLSetPos()
.
(Bug#10563)
When inserting a large BLOB
field,
Connector/ODBC would crash due to a memory allocation error.
(Bug#10562)
The driver was using
mysql_odbc_escape_string()
, which does not
handle the NO_BACKSLASH_ESCAPES
SQL mode. Now
it uses
mysql_real_escape_string()
,
which does.
(Bug#9498)
SQLColumns()
did not handle many of its
parameters correctly, which could lead to incorrect results. The
table name argument was not handled as a pattern value, and most
arguments were not escaped correctly when they contained
non-alphanumeric characters.
(Bug#8860)
There are no binary packages for Microsoft Windows x64 Edition.
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.
Correctly return error if SQLBindCol
is
called with an invalid column.
Fixed possible crash if SQLBindCol()
was not
called before SQLSetPos()
.
The Mac OS X binary packages are only provided as tarballs, there is no installer.
The binary packages for Sun Solaris are only provided as tarballs, not the PKG format.
The HP-UX 11.23 IA64 binary package does not include the GUI bits because of problems building Qt on that platform.
Functionality added or changed:
Connector/ODBC now supports using SSL for communication. This is not yet exposed in the setup GUI, but must be enabled through configuration files or the DSN. (Bug#12918)
Bugs fixed:
Calls to SQLNativeSql() could cause stack corruption due to an incorrect pointer cast. (Bug#28758)
Using curors on results sets with multi-column keys could select the wrong value. (Bug#28255)
SQLForeignKeys
does not escape
_
and %
in the table name
arguments.
(Bug#27723)
When using stored procedures, making a SELECT
or second stored procedure call after an initial stored
procedure call, the second statement will fail.
(Bug#27544)
SQLTables() did not distinguish tables from views. (Bug#23031)
Data in TEXT
columns would fail to be read
correctly.
(Bug#16917)
Specifying strings as parameters using the
adBSTR
or adVarWChar
types, (SQL_WVARCHAR
and
SQL_WLONGVARCHAR
) would be incorrectly
quoted.
(Bug#16235)
SQL_WVARCHAR and SQL_WLONGVARCHAR parameters were not properly quoted and escaped. (Bug#16235)
Using BETWEEN
with date values, the wrong
results could be returned.
(Bug#15773)
When using the Don't Cache Results
(option
value 1048576
) with Microsoft Access, the
connection will fail using DAO/VisualBasic.
(Bug#4657)
Return values from SQLTables()
may be
truncated. (Bugs #22797)
Bugs fixed:
Connector/ODBC would incorrectly claim to support
SQLProcedureColumns
(by returning true when
queried about SQLPROCEDURECOLUMNS
with
SQLGetFunctions
), but this functionality is
not supported.
(Bug#27591)
An incorrect transaction isolation level may not be returned when accessing the connection attributes. (Bug#27589)
Adding a new DSN with the myodbc3i
utility
under AIX would fail.
(Bug#27220)
When inserting data using bulk statements (through
SQLBulkOperations
), the indicators for all
rows within the insert would not updated correctly.
(Bug#24306)
Using SQLProcedures
does not return the
database name within the returned resultset.
(Bug#23033)
The SQLTransact()
function did not support an
empty connection handle.
(Bug#21588)
Using SQLDriverConnect
instead of
SQLConnect
could cause later operations to
fail.
(Bug#7912)
When using blobs and parameter replacement in a statement with
WHERE CURSOR OF
, the SQL is truncated.
(Bug#5853)
Connector/ODBC would return too many foreign key results when accessing tables with similar names. (Bug#4518)
Functionality added or changed:
Use of SQL_ATTR_CONNECTION_TIMEOUT
on the
server has now been disabled. If you attempt to set this
attribute on your connection the
SQL_SUCCESS_WITH_INFO
will be returned, with
an error number/string of HYC00: Optional feature not
supported
.
(Bug#19823)
Added auto is null option to Connector/ODBC option parameters. (Bug#10910)
Added auto-reconnect option to Connector/ODBC option parameters.
Added support for the HENV
handlers in
SQLEndTran()
.
Bugs fixed:
On 64-bit systems, some types would be incorrectly returned. (Bug#26024)
When retrieving TIME
columns, C/ODBC would
incorrectly interpret the type of the string and could interpret
it as a DATE
type instead.
(Bug#25846)
Connector/ODBC may insert the wrong parameter values when using prepared statements under 64-bit Linux. (Bug#22446)
Using Connector/ODBC, with SQLBindCol
and
binding the length to the return value from
SQL_LEN_DATA_AT_EXEC
fails with a memory
allocation error.
(Bug#20547)
Using DataAdapter
, Connector/ODBC may
continually consume memory when reading the same records within
a loop (Windows Server 2003 SP1/SP2 only).
(Bug#20459)
When retrieving data from columns that have been compressed
using COMPRESS()
, the retrieved data would be
truncated to 8KB.
(Bug#20208)
The ODBC driver name and version number were incorrectly reported by the driver. (Bug#19740)
A string format exception would be raised when using iODBC, Connector/ODBC and the embedded MySQL server. (Bug#16535)
The SQLDriverConnect()
ODBC method did not
work with recent Connector/ODBC releases.
(Bug#12393)
Connector/ODBC 3.51.13 was an internal implementation and testing release.
Functionality added or changed:
N/A
Bugs fixed:
Bugs fixed:
mysql_list_dbcolumns()
and
insert_fields()
were retrieving all rows from
a table. Fixed the queries generated by these functions to
return no rows.
(Bug#8198)
SQLGetTypoInfo()
returned
tinyblob
for SQL_VARBINARY
and nothing for SQL_BINARY
. Fixed to return
varbinary
for
SQL_VARBINARY
, binary
for
SQL_BINARY
, and longblob
for SQL_LONGVARBINARY
.
(Bug#8138)
Functionality added or changed:
Added support for DbDataAdapter
UpdateBatchSize
. Batching is fully supported
including collapsing inserts down into the multi-value form if
possible.
DDEX provider now works under Visual Studio 2008 beta 2.
Added ClearPool and ClearAllPools features.
Bugs fixed:
Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)
Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)
Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)
Commands executed from within the state change handeler would
fail with a NULL
exception.
(Bug#30964)
When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)
Using compression in the MySQL connection with Connector/NET would be slower than using native (uncompressed) communication. (Bug#27865)
The MySqlDbType.Datetime
has been replaced
with MySqlDbType.DateTime
. The old format has
been obsoleted.
(Bug#26344)
Bugs fixed:
Setting the size of a string parameter after the value could cause an exception. (Bug#32094)
Creation of parameter objects with non-input direction using a constructor would fail. This was cause by some old legacy code preventing their use. (Bug#32093)
A date string could be returned incorrectly by
MySqlDataTime.ToString()
when the date
returned by MySQL was 0000-00-00 00:00:00
.
(Bug#32010)
A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug#31930)
Installing over a failed uninstall of a previous version could
result in multiple clients being registered in the
machine.config
. This would prevent certain
aspects of the MySQL connection within Visual Studio to work
properly.
(Bug#31731)
Connector/NET would incorrectly report success when enlisting in a distributed transaction, although distributed transactions are not supported. (Bug#31703)
Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)
Trying to use a connection that was not open could return an ambiguous and misleading error message. (Bug#31262)
Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)
Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)
Commands executed from within the state change handeler would
fail with a NULL
exception.
(Bug#30964)
Extracting data through XML functions within a query returns the
data as System.Byte[]
. This was due to
Connector/NET incorrectly identifying BLOB
fields as binary, rather than text.
(Bug#30233)
When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)
Column types with only 1-bit (such as BOOLEAN
and TINYINT(1)
were not returned as boolean
fields.
(Bug#27959)
When accessing certain statements, the command would timeout
before the command completed. Because this cannot always be
controlled through the individual command timeout options, a
default command timeout
has been added to the
connection string options.
(Bug#27958)
The server error code was not updated in the
Data[]
hash, which prevented
DbProviderFactory
users from accessing the
server error code.
(Bug#27436)
The MySqlDbType.Datetime
has been replaced
with MySqlDbType.DateTime
. The old format has
been obsoleted.
(Bug#26344)
Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)
This is a new Beta development release, fixing recently discovered bugs.
Bugs fixed:
An incorrect ConstraintException
could be
raised on an INSERT
when adding rows to a
table with a multiple-column unique key index.
(Bug#30204)
A DATE
field would be updated with a
date/time value, causing a
MySqlDataAdapter.Update()
exception.
(Bug#30077)
The Saudi Hijri calendar was not supported. (Bug#29931)
Calling SHOW CREATE PROCEDURE
for routines
with a hyphen in the catalog name produced a syntax error.
(Bug#29526)
Connecting to a MySQL server earlier than version 4.1 would
raise a NullException
.
(Bug#29476)
The availability of a MySQL server would not be reset when using
pooled connections (pooling=true
). This would
lead to the server being reported as unavailable, even if the
server become available while the application was still running.
(Bug#29409)
A FormatException
error would be raised if a
parameter had not been found, instead of
Resources.ParameterMustBeDefined
.
(Bug#29312)
An exception would be thrown when using the Manage Role functionality within the web administrator to assign a role to a user. (Bug#29236)
Using the membership/role providers when
validationKey
or
decryptionKey
parameters are set to
AutoGenerate
, an exception would be raised
when accessing the corresponding values.
(Bug#29235)
Certain operations would not check the
UsageAdvisor
setting, causing log messages
from the Usage Advisor even when it was disabled.
(Bug#29124)
Using the same connection string multiple times would result in
Database=
appearing multiple times in the resulting string.
(Bug#29123)dbname
Visual Studio Plugin: Adding a new query
based on a stored procedure that uses the
SELECT
statement would terminate the
query/TableAdapter wizard.
(Bug#29098)
Using TransactionScope
would cause an
InvalidOperationException
.
(Bug#28709)
This is a new Beta development release, fixing recently discovered bugs.
Bugs fixed:
Log messages would be truncated to 300 bytes. (Bug#28706)
Creating a user would fail due to the application name being set incorrectly. (Bug#28648)
Visual Studio Plugin: Adding a new query
based on a stored procedure that used a
UPDATE
, INSERT
or
DELETE
statement would terminate the
query/TableAdapter wizard.
(Bug#28536)
Visual Studio Plugin: Query Builder would
fail to show TINYTEXT
columns, and any
columns listed after a TINYTEXT
column
correctly.
(Bug#28437)
Accessing the results from a large query when using data compression in the connection would fail to return all the data. (Bug#28204)
Visual Studio Plugin: Update commands would not be generated correctly when using the TableAdapter wizard. (Bug#26347)
Bugs fixed:
Running the statement SHOW PROCESSLIST
would
return columns as byte arrays instead of native columns.
(Bug#28448)
Installation of the Connector/NET on Windows would fail if VisualStudio had not already been installed. (Bug#28260)
Connector/NET would look for the wrong table when executing
User.IsRole().
(Bug#28251)
Building a connection string within a tight loop would show slow peformance. (Bug#28167)
The UNSIGNED
flag for parameters in a stored
procedure would be ignored when using
MySqlCommandBuilder
to obtain the parameter
information.
(Bug#27679)
Using MySQLDataAdapter.FillSchema()
on a
stored procedure would raise an exception: Invalid
attempt to access a field before calling Read()
.
(Bug#27668)
DATETIME
fields from versions of MySQL
bgefore 4.1 would be incorrectly parsed, resulting in a
exception.
(Bug#23342)
Fixed password property on
MySqlConnectionStringBuilder
to use
PasswordPropertyText
attribute. This causes
dots to show instead of actual password text.
Functionality added or changed:
Now compiles for .NET CF 2.0.
Rewrote stored procedure parsing code using a new SQL tokenizer. Really nasty procedures including nested comments are now supported.
GetSchema will now report objects relative to the currently selected database. What this means is that passing in null as a database restriction will report objects on the currently selected database only.
Added Membership and Role provider contributed by Sean Wright (thanks!).
Bugs fixed:
Setting the size of a string parameter after the value could cause an exception. (Bug#32094)
Creation of parameter objects with non-input direction using a constructor would fail. This was cause by some old legacy code preventing their use. (Bug#32093)
A date string could be returned incorrectly by
MySqlDataTime.ToString()
when the date
returned by MySQL was 0000-00-00 00:00:00
.
(Bug#32010)
A syntax error in a set of batch statements could leave the data adapter in a state that appears hung. (Bug#31930)
Installing over a failed uninstall of a previous version could
result in multiple clients being registered in the
machine.config
. This would prevent certain
aspects of the MySQL connection within Visual Studio to work
properly.
(Bug#31731)
Data cached from the connection string could return invalid information because the internal routines were not using case-sensitive semantics. This lead to updated connection string options not being recognized if they were of a different case than the existing cached values. (Bug#31433)
Column name metadata was not using the character set as deifned within the connection string being used. (Bug#31185)
Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)
Commands executed from within the state change handeler would
fail with a NULL
exception.
(Bug#30964)
When running a stored procedure multiple times on the same connection, the memory usage could increase indefinitely. (Bug#30116)
The server error code was not updated in the
Data[]
hash, which prevented
DbProviderFactory
users from accessing the
server error code.
(Bug#27436)
Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)
This version introduces a new installer technology.
Bugs fixed:
Extracting data through XML functions within a query returns the
data as System.Byte[]
. This was due to
Connector/NET incorrectly identifying BLOB
fields as binary, rather than text.
(Bug#30233)
An incorrect ConstraintException
could be
raised on an INSERT
when adding rows to a
table with a multiple-column unique key index.
(Bug#30204)
A DATE
field would be updated with a
date/time value, causing a
MySqlDataAdapter.Update()
exception.
(Bug#30077)
Fixed bug where Connector/Net was hand building some date time patterns rather than using the patterns provided under CultureInfo. This caused problems with some calendars that do not support the same ranges as Gregorian.. (Bug#29931)
Calling SHOW CREATE PROCEDURE
for routines
with a hyphen in the catalog name produced a syntax error.
(Bug#29526)
The availability of a MySQL server would not be reset when using
pooled connections (pooling=true
). This would
lead to the server being reported as unavailable, even if the
server become available while the application was still running.
(Bug#29409)
A FormatException
error would be raised if a
parameter had not been found, instead of
Resources.ParameterMustBeDefined
.
(Bug#29312)
Certain operations would not check the
UsageAdvisor
setting, causing log messages
from the Usage Advisor even when it was disabled.
(Bug#29124)
Using the same connection string multiple times would result in
Database=
appearing multiple times in the resulting string.
(Bug#29123)dbname
Log messages would be truncated to 300 bytes. (Bug#28706)
Accessing the results from a large query when using data compression in the connection will fail to return all the data. (Bug#28204)
Fixed problem where
MySqlConnection.BeginTransaction
checked the
drivers status var before checking if the connection was open.
The result was that the driver could report an invalid condition
on a previously opened connection.
Fixed problem where we were not closing prepared statement handles when commands are disposed. This could lead to using up all prepared statement handles on the server.
Fixed the database schema collection so that it works on servers
that are not properly respecting the
lower_case_table_names
setting.
Fixed problem where any attempt to not read all the records returned from a select where each row of the select is greater than 1024 bytes would hang the driver.
Fixed problem where a command timing out just after it actually finished would cause an exception to be thrown on the command timeout thread which would then be seen as an unhandled exception.
Fixed some serious issues with command timeout and cancel that could present as exceptions about thread ownership. The issue was that not all queries cancel the same. Some produce resultsets while others don't. ExecuteReader had to be changed to check for this.
Bugs fixed:
Running the statement SHOW PROCESSLIST
would
return columns as byte arrays instead of native columns.
(Bug#28448)
Building a connection string within a tight loop would show slow peformance. (Bug#28167)
Using logging (with the logging=true
parameter to the connection string) would not generate a log
file.
(Bug#27765)
The UNSIGNED
flag for parameters in a stored
procedure would be ignored when using
MySqlCommandBuilder
to obtain the parameter
information.
(Bug#27679)
Using MySQLDataAdapter.FillSchema()
on a
stored procedure would raise an exception: Invalid
attempt to access a field before calling Read()
.
(Bug#27668)
If you close an open connection with an active transaction, the transaction is not automatically rolled back. (Bug#27289)
When cloning an open
MySqlClient.MySqlConnection
with the
Persist Security Info=False
option set, the
cloned connection is not usable because the security information
has not been cloned.
(Bug#27269)
Enlisting a null transaction would affect the current connection object, such that further enlistment operations to the transaction are not possible. (Bug#26754)
Attempting to change the the Connection
Protocol
property within a
PropertyGrid
control would raise an
exception.
(Bug#26472)
The characterset
property would not be
identified during a connection (also affected Visual Studion
Plugin).
(Bug#26147, Bug#27240)
The CreateFormat
column of the
DataTypes
collection did not contain a format
specification for creating a new column type.
(Bug#25947)
DATETIME
fields from versions of MySQL
bgefore 4.1 would be incorrectly parsed, resulting in a
exception.
(Bug#23342)
Bugs fixed:
Publisher listed in "Add/Remove Programs" is not consistent with other MySQL products. (Bug#27253)
DESCRIBE ....
SQL statement returns byte
arrays rather than data on MySQL versions older than 4.1.15.
(Bug#27221)
cmd.Parameters.RemoveAt("Id")
will
cause an error if the last item is requested.
(Bug#27187)
MySqlParameterCollection
and parameters added
with Insert
method can not be retrieved later
using ParameterName
.
(Bug#27135)
Exception thrown when using large values in
UInt64
parameters.
(Bug#27093)
MySQL Visual Studio Plugin 1.1.2 does not work with Connector/Net 5.0.5. (Bug#26960)
Functionality added or changed:
Reverted behavior that required parameter names to start with
the parameter marker. We apologize for this back and forth but
we mistakenly changed the behavior to not match what
SqlClient
supports. We now support using
either syntax for adding parameters however we also respond
exactly like SqlClient
in that if you ask for
the index of a parameter using a syntax different from when you
added the parameter, the result will be -1.
Assembly now properly appears in the Visual Studio 2005 Add/Remove Reference dialog.
Fixed problem that prevented use of
SchemaOnly
or SingleRow
command behaviors with stored procedures or prepared statements.
Added MySqlParameterCollection.AddWithValue
and marked the Add(name, value)
method as
obsolete.
Return parameters created with DeriveParameters now have the
name RETURN_VALUE
.
Fixed problem with parameter name hashing where the hashes were not getting updated when parameters were removed from the collection.
Fixed problem with calling stored functions when a return parameter was not given.
Added Use Procedure Bodies
connection string
option to allow calling procedures without using procedure
metadata.
Bugs fixed:
MySqlConnection.GetSchema
fails with
NullReferenceException
for Foreign Keys.
(Bug#26660)
Connector/NET would fail to install under Windows Vista. (Bug#26430)
Opening a connection would be slow due to hostname lookup. (Bug#26152)
Incorrect values/formats would be applied when the
OldSyntax
connection string option was used.
(Bug#25950)
Registry would be incorrectly populated with installation locations. (Bug#25928)
Times with negative values would be returned incorrectly. (Bug#25912)
Returned data types of a DataTypes
collection
do not contain the right correctl CLR Datatype.
(Bug#25907)
GetSchema
and DataTypes
would throw an exception due to an incorrect table name.
(Bug#25906)
MySqlConnection
throws an exception when
connecting to MySQL v4.1.7.
(Bug#25726)
SELECT
did not work correctly when using a
WHERE
clause containing a UTF-8 string.
(Bug#25651)
When closing and then re-opening a connection to a database, the character set specification is lost. (Bug#25614)
Filling a table schema through a stored procedure triggers a runtime error. (Bug#25609)
BINARY
and VARBINARY
columns would be returned as a string, not binary, datatype.
(Bug#25605)
A critical ConnectionPool
error would result
in repeated System.NullReferenceException
.
(Bug#25603)
The UpdateRowSource.FirstReturnedRecord
method does not work.
(Bug#25569)
When connecting to a MySQL Server earlier than version 4.1, the connection would hang when reading data. (Bug#25458)
Using ExecuteScalar()
with more than one
query, where one query fails, will hang the connection.
(Bug#25443)
When a MySqlConversionException
is raised on
a remote object, the client application would receive a
SerializationException
instead.
(Bug#24957)
When connecting to a server, the return code from the connection could be zero, even though the hostname was incorrect. (Bug#24802)
High CPU utilization would be experienced when there is no idle
connection waiting when using pooled connections through
MySqlPool.GetConnection
.
(Bug#24373)
Connector/NET would not compile properly when used with Mono 1.2. (Bug#24263)
Applications would crash when calling with
CommandType
set to
StoredProcedure
.
This is a new Beta development release, fixing recently discovered bugs.
Functionality added or changed:
Usage Advisor has been implemented. The Usage Advisor checks your queries and will report if you are using the connection inefficiently.
PerfMon hooks have been added to monitor the stored procedure cache hits and misses.
The MySqlCommand
object now supports
asynchronous query methods. This is implemented useg the
BeginExecuteNonQuery
and
EndExecuteNonQuery
methods.
Metadata from storaed procedures and stored function execution are cached.
The CommandBuilder.DeriveParameters
function
has been updated to the procedure cache.
The ViewColumns
GetSchema
collection has been updated.
Improved speed and performance by re-architecting certain sections of the code.
Support for the embedded server and client library have been removed from this release. Support will be added back to a later release.
The ShapZipLib library has been replaced with the deflate support provided within .NET 2.0.
SSL support has been updated.
Bugs fixed:
Additional text added to error message (Bug#25178)
An exception would be raised, or the process would hang, if
SELECT
privileges on a database were not
granted and a stored procedure was used.
(Bug#25033)
When adding parameter objects to a command object, if the
parameter direction is set to ReturnValue
before the parameter is added to the command object then when
the command is executed it throws an error.
(Bug#25013)
Using Driver.IsTooOld()
would return the
wrong value.
(Bug#24661)
When using a DbNull.Value
as the value for a
parameter value, and then later setting a specific value type,
the command would fail with an exception because the wrong type
was implied from the DbNull.Value
.
(Bug#24565)
Stored procedure executions are not thread safe. (Bug#23905)
Deleting a connection to a disconnected server when using the Visual Studio Plugin would cause an assertion failure. (Bug#23687)
Nested transactions (which are unsupported)do not raise an error or warning. (Bug#22400)
Functionality added or changed:
An Ignore Prepare
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.
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 procedure cache
connection string.
Important change: 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.
To enable server-side prepared statements you must add the following configuration property to your connector string properties:
ignore prepare=false
The default value of this property is true.
Bugs fixed:
One system where IPv6 was enabled, Connector/NET would incorrectly resolve hostnames. (Bug#23758)
Column names with accented characters were not parsed properly causing malformed column names in result sets. (Bug#23657)
An exception would be thrown when calling
GetSchemaTable
and fields
was null.
(Bug#23538)
A System.FormatException
exception would be
raised when invoking a stored procedure with an
ENUM
input parameter.
(Bug#23268)
During installation, an antivirus error message would be raised (indicating a malicious script problem). (Bug#23245)
Creating a connection through the Server Explorer when using the Visual Studio Plugin would fail. The installer for the Visual Studio Plugin has been updated to ensure that Connector/NET 5.0.2 must be installed. (Bug#23071)
Using Windows Vista (RC2) as a non-privileged user would raise a
Registry key 'Global' access denied
.
(Bug#22882)
Within Mono, using the PreparedStatement
interface could result in an error due to a
BitArray
copying error.
(Bug#18186)
Connector/NET did not work as a data source for the
SqlDataSource
object used by ASP.NET 2.0.
(Bug#16126)
Bugs fixed:
Connector/NET on a Tukish operating system, may fail to execute certain SQL statements correctly. (Bug#22452)
Starting a transaction on a connection created by
MySql.Data.MySqlClient.MySqlClientFactory
,
using BeginTransaction
without specifying an
isolation level, causes the SQL statement to fail with a syntax
error.
(Bug#22042)
The MySqlexception
class is now derived from
the DbException
class.
(Bug#21874)
The #
would not be accepted within
column/table names, even though it was valid.
(Bug#21521)
You can now install the Connector/NET MSI package from the
command line using the /passive
,
/quiet
, /q
options.
(Bug#19994)
Submitting an empty string to a command object through
prepare
raises an
System.IndexOutOfRangeException
, rather than
a Connector/Net exception.
(Bug#18391)
Using ExecuteScalar
with a datetime field,
where the value of the field is "0000-00-00 00:00:00",
a MySqlConversionException
exception would be
raised.
(Bug#11991)
An MySql.Data.Types.MySqlConversionException
would be raised when trying to update a row that contained a
date field, where the date field contained a zero value
(0000-00-00 00:00:00).
(Bug#9619)
Executing multiple queries as part of a transaction returns
There is already an openDataReader associated with this
Connection which must be closed first
.
(Bug#7248)
Incorrect field/data lengths could be returned for
VARCHAR
UTF8 columns. Bug (#14592)
Functionality added or changed:
Replaced use of ICSharpCode with .NET 2.0 internal deflate support.
Refactored test suite to test all protocols in a single pass.
Added usage advisor warnings for requesting column values by the wrong type.
Reimplemented PacketReader/PacketWriter support into
MySqlStream
class.
Reworked connection string classes to be simpler and faster.
Added procedure metadata caching.
Added internal implemention of SHA1 so we don't have to distribute the OpenNetCF on mobile devices.
Implemented MySqlClientFactory
class.
Added perfmon hooks for stored procedure cache hits and misses.
Implemented classes and interfaces for ADO.Net 2.0 support.
Added Async query methods.
Implemented Usage Advisor.
Completely refactored how column values are handled to avoid boxing in some cases.
Implemented MySqlConnectionBuilder
class.
Bugs fixed:
CommandText: Question mark in comment line is being parsed as a parameter. (Bug#6214)
Bugs fixed:
Setting the size of a string parameter after the value could cause an exception. (Bug#32094)
Creation of parameter objects with non-input direction using a constructor would fail. This was cause by some old legacy code preventing their use. (Bug#32093)
Memory usage could increase and decrease significantly when updating or inserting a large number of rows. (Bug#31090)
Commands executed from within the state change handeler would
fail with a NULL
exception.
(Bug#30964)
Extracting data through XML functions within a query returns the
data as System.Byte[]
. This was due to
Connector/NET incorrectly identifying BLOB
fields as binary, rather than text.
(Bug#30233)
Using compression in the MySQL connection with Connector/NET would be slower than using native (uncompressed) communication. (Bug#27865)
Changing the connection string of a connection to one that changes the parameter marker after the connection had been assigned to a command but before the connection is opened could cause parameters to not be found. (Bug#13991)
Bugs fixed:
An incorrect ConstraintException
could be
raised on an INSERT
when adding rows to a
table with a multiple-column unique key index.
(Bug#30204)
The availability of a MySQL server would not be reset when using
pooled connections (pooling=true
). This would
lead to the server being reported as unavailable, even if the
server become available while the application was still running.
(Bug#29409)
Publisher listed in "Add/Remove Programs" is not consistent with other MySQL products. (Bug#27253)
MySqlParameterCollection
and parameters added
with Insert
method can not be retrieved later
using ParameterName
.
(Bug#27135)
BINARY
and VARBINARY
columns would be returned as a string, not binary, datatype.
(Bug#25605)
A critical ConnectionPool
error would result
in repeated System.NullReferenceException
.
(Bug#25603)
When a MySqlConversionException
is raised on
a remote object, the client application would receive a
SerializationException
instead.
(Bug#24957)
High CPU utilization would be experienced when there is no idle
connection waiting when using pooled connections through
MySqlPool.GetConnection
.
(Bug#24373)
Functionality added or changed:
The ICSharpCode ZipLib is no longer used by the Connector, and is no longer distributed with it.
Important change: 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.
Improved CommandBuilder.DeriveParameters
to
first try and use the procedure cache before querying for the
stored procedure metadata. Return parameters created with
DeriveParameters
now have the name
RETURN_VALUE
.
An Ignore Prepare
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.
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 procedure cache
connection string.
Important change: 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.
To enable server-side prepared statements you must add the following configuration property to your connector string properties:
ignore prepare=false
The default value of this property is true.
Bugs fixed:
Times with negative values would be returned incorrectly. (Bug#25912)
MySqlConnection
throws a
NullReferenceException
and
ArgumentNullException
when connecting to
MySQL v4.1.7.
(Bug#25726)
SELECT
did not work correctly when using a
WHERE
clause containing a UTF-8 string.
(Bug#25651)
When closing and then re-opening a connection to a database, the character set specification is lost. (Bug#25614)
Trying to fill a table schema through a stored procedure triggers a runtime error. (Bug#25609)
Using ExecuteScalar()
with more than one
query, where one query fails, will hang the connection.
(Bug#25443)
Additional text added to error message. (Bug#25178)
When adding parameter objects to a command object, if the
parameter direction is set to ReturnValue
before the parameter is added to the command object then when
the command is executed it throws an error.
(Bug#25013)
When connecting to a server, the return code from the connection could be zero, even though the hostname was incorrect. (Bug#24802)
Using Driver.IsTooOld()
would return the
wrong value.
(Bug#24661)
When using a DbNull.Value
as the value for a
parameter value, and then later setting a specific value type,
the command would fail with an exception because the wrong type
was implied from the DbNull.Value
.
(Bug#24565)
Stored procedure executions are not thread safe. (Bug#23905)
The CommandBuilder
would mistakenly add
insert parameters for a table column with auto incrementation
enabled.
(Bug#23862)
One system where IPv6 was enabled, Connector/NET would incorrectly resolve hostnames. (Bug#23758)
Nested transactions do not raise an error or warning. (Bug#22400)
An System.OverflowException
would be raised
when accessing a varchar field over 255 bytes. Bug (#23749)
Within Mono, using the PreparedStatement
interface could result in an error due to a
BitArray
copying error. (Bug 18186)
Functionality added or changed:
Stored procedures are now cached.
The method for retrieving stored procedured metadata has been
changed so that users without SELECT
privileges on the mysql.proc
table can use a
stored procedure.
Bugs fixed:
Connector/NET on a Tukish operating system, may fail to execute certain SQL statements correctly. (Bug#22452)
The #
would not be accepted within
column/table names, even though it was valid.
(Bug#21521)
Calling Close
on a connection after
calling a stored procedure would trigger a
NullReferenceException
.
(Bug#20581)
You can now install the Connector/NET MSI package from the
command line using the /passive
,
/quiet
, /q
options.
(Bug#19994)
The DiscoverParameters function would fail when a stored
procedure used a NUMERIC
parameter type.
(Bug#19515)
When running a query that included a date comparison, a DateReader error would be raised. (Bug#19481)
IDataRecord.GetString
would raise
NullPointerException
for null values in
returned rows. Method now throws
SqlNullValueException
.
(Bug#19294)
Parameter substitution in queries where the order of parameters and table fields did not match would substitute incorrect values. (Bug#19261)
Submitting an empty string to a command object through
prepare
raises an
System.IndexOutOfRangeException
, rather than
a Connector/Net exception.
(Bug#18391)
An exception would be raised when using an output parameter to a
System.String
value.
(Bug#17814)
CHAR type added to MySqlDbType. (Bug#17749)
A SELECT
query on a table with a date with a
value of '0000-00-00'
would hang the
application.
(Bug#17736)
The CommandBuilder ignored Unsigned flag at Parameter creation. (Bug#17375)
When working with multiple threads, character set initialization would generate errors. (Bug#17106)
When using an unsigned 64-bit integer in a stored procedure, the unsigned bit would be lost stored. (Bug#16934)
DataReader
would show the value of the
previous row (or last row with non-null data) if the current row
contained a datetime
field with a null value.
(Bug#16884)
Unsigned data types were not properly supported. (Bug#16788)
The connection string parser did not allow single or double quotes in the password. (Bug#16659)
The MySqlDateTime
class did not contain
constructors.
(Bug#15112)
Called MySqlCommandBuilder.DeriveParameters
for a stored procedure that has no paramers would cause an
application crash.
(Bug#15077)
Using ExecuteScalar
with a datetime field,
where the value of the field is "0000-00-00 00:00:00",
a MySqlConversionException
exception would be
raised.
(Bug#11991)
An MySql.Data.Types.MySqlConversionException
would be raised when trying to update a row that contained a
date field, where the date field contained a zero value
(0000-00-00 00:00:00).
(Bug#9619)
When using MySqlDataAdapter
, connections to a
MySQL server may remain open and active, even though the use of
the connection has been completed and the data received.
(Bug#8131)
Executing multiple queries as part of a transaction returns
There is already an openDataReader associated with this
Connection which must be closed first
.
(Bug#7248)
Incorrect field/data lengths could be returned for
VARCHAR
UTF8 columns. Bug (#14592)
Bugs fixed:
Unsigned tinyint
(NET byte) would lead to and
incorrectly determined parameter type from the parameter value.
(Bug#18570)
A #42000Query was empty
exception occurred
when executing a query built with
MySqlCommandBuilder
, if the query string
ended with a semicolon.
(Bug#14631)
The parameter collection object's Add()
method added parameters to the list without first checking to
see whether they already existed. Now it updates the value of
the existing parameter object if it exists.
(Bug#13927)
Added support for the cp932
character set.
(Bug#13806)
Calling a stored procedure where a parameter contained special
characters (such as '@'
) would produce an
exception. Note that ANSI_QUOTES
had to be
enabled to make this possible.
(Bug#13753)
The Ping()
method did not update the
State
property of the
Connection
object.
(Bug#13658)
Implemented the
MySqlCommandBuilder.DeriveParameters
method
that is used to discover the parameters for a stored procedure.
(Bug#13632)
A statement that contained multiple references to the same parameter could not be prepared. (Bug#13541)
Bugs fixed:
Connector/NET 1.0.5 could not connect on Mono. (Bug#13345)
Serializing a parameter failed if the first value passed in was
NULL
.
(Bug#13276)
Field names that contained the following characters caused
errors: ()%<>/
(Bug#13036)
The nant
build sequence had problems.
(Bug#12978)
The Connector/NET 1.0.5 installer would not install alongside Connector/NET 1.0.4. (Bug#12835)
Bugs fixed:
Connector/NET could not connect to MySQL 4.1.14. (Bug#12771)
With multiple hosts in the connection string, Connector/NET would not connect to the last host in the list. (Bug#12628)
The ConnectionString
property could not be
set when a MySqlConnection
object was added
with the designer.
(Bug#12551, Bug#8724)
The cp1250
character set was not supported.
(Bug#11621)
A call to a stored procedure caused an exception if the stored procedure had no parameters. (Bug#11542)
Certain malformed queries would trigger a Connection
must be valid and open
error message.
(Bug#11490)
Trying to use a stored procedure when
Connection.Database
was not populated
generated an exception.
(Bug#11450)
Connector/NET interpreted the new decimal data type as a byte array. (Bug#11294)
Added support to call a stored function from Connector/NET. (Bug#10644)
Connection could fail when .NET thread pool had no available worker threads. (Bug#10637)
Calling MySqlConnection.clone
when a
connection string had not yet been set on the original
connection would generate an error.
(Bug#10281)
Decimal parameters caused syntax errors. (Bug#10152, Bug#11550, Bug#10486)
Parameters were not recognized when they were separated by linefeeds. (Bug#9722)
The MySqlCommandBuilder
class could not
handle queries that referenced tables in a database other than
the default database.
(Bug#8382)
Trying to read a TIMESTAMP
column generated
an exception.
(Bug#7951)
Connector/NET could not work properly with certain regional settings. (WL#8228)
Bugs fixed:
MySqlReader.GetInt32
throws exception if
column is unsigned.
(Bug#7755)
Quote character \222 not quoted in
EscapeString
.
(Bug#7724)
GetBytes is working no more. (Bug#7704)
MySqlDataReader.GetString(index)
returns
non-Null value when field is Null
.
(Bug#7612)
Clone method bug in MySqlCommand
.
(Bug#7478)
Problem with Multiple resultsets. (Bug#7436)
MySqlAdapter.Fill
method throws error message
Non-negative number required
.
(Bug#7345)
MySqlCommand.Connection
returns an
IDbConnection.
(Bug#7258)
Calling prepare causing exception. (Bug#7243)
Fixed problem with shared memory connections.
Added or filled out several more topics in the API reference documentation.
Fixed another small problem with prepared statements.
Fixed problem that causes named pipes to not work with some blob functionality.
Bugs fixed:
Invalid query string when using inout parameters (Bug#7133)
Inserting DateTime
causes
System.InvalidCastException
to be thrown.
(Bug#7132)
MySqlDateTime
in Datatables sorting by Text,
not Date.
(Bug#7032)
Exception stack trace lost when re-throwing exceptions. (Bug#6983)
Errors in parsing stored procedure parameters. (Bug#6902)
InvalidCast when using DATE_ADD
-function.
(Bug#6879)
Int64 Support in MySqlCommand
Parameters.
(Bug#6863)
Test suite fails with MySQL 4.0 because of case sensitivity of table names. (Bug#6831)
MySqlDataReader.GetChar(int i)
throws
IndexOutOfRange
exception.
(Bug#6770)
Integer "out" parameter from stored procedure returned as string. (Bug#6668)
An Open Connection has been Closed by the Host System. (Bug#6634)
Fixed Invalid character set index: 200. (Bug#6547)
Connections now do not have to give a database on the connection string.
Installer now includes options to install into GAC and create
items.Fixed major problem with detecting null values when using prepared statements.
Fixed problem where multiple resultsets having different numbers of columns would cause a problem.
Added ServerThread
property to
MySqlConnection
to expose server thread id.
Added Ping method to MySqlConnection
.
Changed the name of the test suite to
MySql.Data.Tests.dll
.
Now SHOW COLLATION
is used upon connection to
retrieve the full list of charset ids.
Made MySQL the default named pipe name.
Bugs fixed:
Fixed Objects not being disposed (Bug#6649)
Fixed Charset-map for UCS-2 (Bug#6541)
Fixed Zero date "0000-00-00" is returned wrong when filling Dataset (Bug#6429)
Fixed double type handling in MySqlParameter(string parameterName, object value) (Bug#6428)
Fixed Installation directory ignored using custom installation (Bug#6329)
Fixed #HY000 Illegal mix of collations (latin1_swedish_ci,IMPLICIT) and (utf8_general_ (Bug#6322)
Added the TableEditor CS and VB sample
Added charset connection string option
Fixed problem with MySqlBinary where string values could not be used to update extended text columns
Provider is now using character set specified by server as default
Updated the installer to include the new samples
Fixed problem where setting command text leaves the command in a prepared state
Fixed Long inserts take very long time (Bu #5453)
Fixed problem where calling stored procedures might cause an "Illegal mix of collations" problem.
Bugs fixed:
Fixed IndexOutOfBounds when reading BLOB with DataReader with GetString(index) (Bug#6230)
Fixed GetBoolean returns wrong values (Bug#6227)
Fixed Method TokenizeSql() uses only a limited set of valid characters for parameters (Bug#6217)
Fixed NET Connector source missing resx files (Bug#6216)
Fixed System.OverflowException when using YEAR datatype (Bug#6036)
Fixed MySqlDateTime sets IsZero property on all subseq.records after first zero found (Bug#6006)
Fixed serializing of floating point parameters (double, numeric, single, decimal) (Bug#5900)
Fixed missing Reference in DbType setter (Bug#5897)
Fixed Parsing the ';' char (Bug#5876)
Fixed DBNull Values causing problems with retrieving/updating queries. (Bug#5798)
IsNullable error (Bug#5796)
Fixed problem where MySqlParameterCollection.Add() would throw unclear exception when given a null value (Bug#5621)
Fixed construtor initialize problems in MySqlCommand() (Bug#5613)
Fixed Yet Another "object reference not set to an instance of an object" (Bug#5496)
Fixed Can't display Chinese correctly (Bug#5288)
Fixed MySqlDataReader and 'show tables from ...' behavior (Bug#5256)
Fixed problem in PacketReader where it could try to allocate the wrong buffer size in EnsureCapacity
Fixed problem where using old syntax while using the interfaces caused problems
Fixed Bug#5458 Calling GetChars on a longtext column throws an exception
Added test case for resetting the command text on a prepared command
Fixed Bug#5388 DataReader reports all rows as NULL if one row is NULL
Fixed problem where connection lifetime on the connect string was not being respected
Fixed Bug#5602 Possible bug in MySqlParameter(string, object) constructor
Field buffers being reused to decrease memory allocations and increase speed
Fixed Bug#5392 MySqlCommand sees "?" as parameters in string literals
Added Aggregate function test (wasn't really a bug)
Using PacketWriter instead of Packet for writing to streams
Implemented SequentialAccess
Fixed problem with ConnectionInternal where a key might be added more than once
Fixed Russian character support as well
Fixed Bug#5474 cannot run a stored procedure populating mysqlcommand.parameters
Fixed problem where connector was not issuing a CMD_QUIT before closing the socket
Fixed problem where Min Pool Size was not being respected
Refactored compression code into CompressedStream to clean up NativeDriver
CP1252 is now used for Latin1 only when the server is 4.1.2 and later
Fixed Bug#5469 Setting DbType throws NullReferenceException
Virtualized driver subsystem so future releases could easily support client or embedded server support
Bugs fixed:
Thai encoding not correctly supported. (Bug#3889)
Bumped version number to 1.0.0 for beta 1 release.
Removed all of the XML comment warnings.
Added COPYING.rtf
file for use in
installer.
Updated many of the test cases.
Fixed problem with using compression.
Removed some last references to ByteFX.
Added test fixture for prepared statements.
All type classes now implement a
SerializeBinary
method for sending their
data to a PacketWriter
.
Added PacketWriter
class that will enable
future low-memory large object handling.
Fixed many small bugs in running prepared statements and stored procedures.
Changed command so that an exception will not be thrown in executing a stored procedure with parameters in old syntax mode.
SingleRow
behavior now working right even
with limit.
GetBytes
now only works on binary columns.
Logger now truncates long sql commands so blob columns don't blow out our log.
host and database now have a default value of "" unless otherwise set.
Connection Timeout seems to be ignored. (Bug#5214)
Added test case for bug# 5051: GetSchema not working correctly.
Fixed problem where GetSchema
would return
false for IsUnique
when the column is key.
MySqlDataReader GetXXX
methods now using
the field level MySqlValue
object and not
performing conversions.
DataReader
returning
NULL
for time column. (Bug#5097)
Added test case for LOAD DATA LOCAL INFILE
.
Added replacetext custom nant task.
Added CommandBuilderTest
fixture.
Added Last One Wins feature to
CommandBuilder
.
Fixed persist security info case problem.
Fixed GetBool
so that 1, true, "true", and
"yes" all count as true.
Make parameter mark configurable.
Added the "old syntax" connection string parameter to allow use of @ parameter marker.
MySqlCommandBuilder
. (Bug#4658)
ByteFX.MySqlClient
caches passwords if
Persist Security Info
is false. (Bug#4864)
Updated license banner in all source files to include FLOSS exception.
Added new .Types namespace and implementations for most current MySql types.
Added MySqlField41
as a subclass of
MySqlField
.
Changed many classes to now use the new .Types types.
Changed type enum int
to
Int32
, short
to
Int16
, and bigint
to
Int64
.
Added dummy types UInt16
,
UInt32
, and UInt64
to
allow an unsigned parameter to be made.
Connections are now reset when they are pulled from the connection pool.
Refactored auth code in driver so it can be used for both auth and reset.
Added UserReset
test in
PoolingTests.cs
.
Connections are now reset using
COM_CHANGE_USER
when pulled from the pool.
Implemented SingleResultSet
behavior.
Implemented support of unicode.
Added char set mappings for utf-8 and ucs-2.
Time fields overflow using bytefx .net mysql driver (Bug#4520)
Modified time test in data type test fixture to check for time spans where hours > 24.
Wrong string with backslash escaping in
ByteFx.Data.MySqlClient.MySqlParameter
.
(Bug#4505)
Added code to Parameter test case TestQuoting to test for backslashes.
MySqlCommandBuilder
fails with multi-word
column names. (Bug#4486)
Fixed bug in TokenizeSql
where underscore
would terminate character capture in parameter name.
Added test case for spaces in column names.
MySqlDataReader.GetBytes
don't works
correctly. (Bug#4324)
Added GetBytes()
test case to
DataReader
test fixture.
Now reading all server variables in
InternalConnection.Configure
into
Hashtable
.
Now using string[]
for index map in
CharSetMap
.
Added CRInSQL test case for carriage returns in SQL.
Setting maxPacketSize to default value in
Driver.ctor
.
Setting MySqlDbType
on a parameter doesn't
set generic type. (Bug#4442)
Removed obsolete data types Long
and
LongLong
.
Overflow exception thrown when using "use pipe" on connection string. (Bug#4071)
Changed "use pipe" keyword to "pipe name" or just "pipe".
Allow reading multiple resultsets from a single query.
Added flags attribute to ServerStatusFlags
enum.
Changed name of ServerStatus
enum to
ServerStatusFlags
.
Inserted data row doesn't update properly.
Error processing show create table. (Bug#4074)
Change Packet.ReadLenInteger
to
ReadPackedLong
and added
packet.ReadPackedInteger
that always reads
integers packed with 2,3,4.
Added syntax.cs
test fixture to test
various SQL syntax bugs.
Improper handling of time values. Now time value of 00:00:00 is not treated as null. (Bug#4149)
Moved all test suite files into TestSuite
folder.
Fixed bug where null column would move the result packet pointer backward.
Added new nant build script.
Clear tablename so it will be regen'ed properly during the
next GenerateSchema
. (Bug#3917)
GetValues
was always returning zero and was
also always trying to copy all fields rather than respecting
the size of the array passed in. (Bug#3915)
Implemented shared memory access protocol.
Implemented prepared statements for MySQL 4.1.
Implemented stored procedures for MySQL 5.0.
Renamed MySqlInternalConnection
to
InternalConnection
.
SQL is now parsed as chars, fixes problems with other languages.
Added logging and allow batch connection string options.
RowUpdating
event not set when setting the
DataAdapter
property. (Bug#3888)
Fixed bug in char set mapping.
Implemented 4.1 authentication.
Improved open/auth code in driver.
Improved how connection bits are set during connection.
Database name is now passed to server during initial handshake.
Changed namespace for client to
MySql.Data.MySqlClient
.
Changed assembly name of client to
MySql.Data.dll
.
Changed license text in all source files to GPL.
Added the MySqlClient.build
Nant file.
Removed the mono batch files.
Moved some of the unused files into notused folder so nant build file can use wildcards.
Implemented shared memory access.
Major revamp in code structure.
Prepared statements now working for MySql 4.1.1 and later.
Finished implementing auth for 4.0, 4.1.0, and 4.1.1.
Changed namespace from
MySQL.Data.MySQLClient
back to
MySql.Data.MySqlClient
.
Fixed bug in CharSetMapping
where it was
trying to use text names as ints.
Changed namespace to
MySQL.Data.MySQLClient
.
Integrated auth changes from UC2004.
Fixed bug where calling any of the GetXXX methods on a datareader before or after reading data would not throw the appropriate exception (thanks Luca Morelli).
Added TimeSpan
code in parameter.cs to
properly serialize a timespan object to mysql time format
(thanks Gianluca Colombo).
Added TimeStamp
to parameter serialization
code. Prevented DataAdatper
updates from
working right (thanks Michael King).
Fixed a misspelling in MySqlHelper.cs
(thanks Patrick Kristiansen).
Driver now using charset number given in handshake to create encoding.
Changed command editor to point to
MySqlClient.Design
.
Fixed bug in Version.isAtLeast
.
Changed DBConnectionString
to support
changes done to MySqlConnectionString
.
Removed SqlCommandEditor
and
DataAdapterPreviewDialog
.
Using new long return values in many places.
Integrated new CompressedStream
class.
Changed ConnectionString
and added
attributes to allow it to be used in
MySqlClient.Design
.
Changed packet.cs
to support newer
lengths in ReadLenInteger
.
Changed other classes to use new properties and fields of
MySqlConnectionString
.
ConnectionInternal
is now using PING to see
whether the server is alive.
Moved toolbox bitmaps into resource folder.
Changed field.cs
to allow values to come
directly from row buffer.
Changed to use the new driver.Send syntax.
Using a new packet queueing system.
Started work handling the "broken" compression packet handling.
Fixed bug in StreamCreator
where failure to
connect to a host would continue to loop infinitly (thanks
Kevin Casella).
Improved connectstring handling.
Moved designers into Pro product.
Removed some old commented out code from
command.cs
.
Fixed a problem with compression.
Fixed connection object where an exception throw prior to the connection opening would not leave the connection in the connecting state (thanks Chris Cline).
Added GUID support.
Fixed sequence out of order bug (thanks Mark Reay).
Enum values now supported as parameter values (thanks Philipp Sumi).
Year datatype now supported.
Fixed compression.
Fixed bug where a parameter with a TimeSpan
as the value would not serialize properly.
Fixed bug where default constructor would not set default connection string values.
Added some XML comments to some members.
Work to fix/improve compression handling.
Improved ConnectionString
handling so that
it better matches the standard set by
SqlClient
.
A MySqlException
is now thrown if a
username is not included in the connection string.
Localhost is now used as the default if not specified on the connection string.
An exception is now thrown if an attempt is made to set the connection string while the connection is open.
Small changes to ConnectionString
docs.
Removed MultiHostStream
and
MySqlStream
. Replaced it with
Common/StreamCreator
.
Added support for Use Pipe connection string value.
Added Platform class for easier access to platform utility functions.
Fixed small pooling bug where new connection was not getting
created after IsAlive
fails.
Added Platform.cs
and
StreamCreator.cs
.
Fixed Field.cs
to properly handle 4.1
style timestamps.
Changed Common.Version
to
Common.DBVersion
to avoid name conflict.
Fixed field.cs
so that text columns
return the right field type.
Added MySqlError
class to provide some
reference for error codes (thanks Geert Veenstra).
Added Unix socket support (thanks Mohammad DAMT).
Only calling Thread.Sleep
when no data is
available.
Improved escaping of quote characters in parameter data.
Removed misleading comments from
parameter.cs
.
Fixed pooling bug.
Fixed ConnectionString
editor dialog
(thanks marco p (pomarc)).
UserId
now supported in connection strings
(thanks Jeff Neeley).
Attempting to create a parameter that is not input throws an exception (thanks Ryan Gregg).
Added much documentation.
Checked in new MultiHostStream
capability.
Big thanks to Dan Guisinger for this. he originally submitted
the code and idea of supporting multiple machines on the
connect string.
Added a lot of documentation.
Fixed speed issue with 0.73.
Changed to Thread.Sleep(0) in MySqlDataStream to help optimize the case where it doesn't need to wait (thanks Todd German).
Prepopulating the idlepools to MinPoolSize
.
Fixed MySqlPool
deadlock condition as well
as stupid bug where CreateNewPooledConnection was not ever
adding new connections to the pool. Also fixed
MySqlStream.ReadBytes
and
ReadByte
to not use
TicksPerSecond
which does not appear to
always be right. (thanks Matthew J. Peddlesden)
Fix for precision and scale (thanks Matthew J. Peddlesden).
Added Thread.Sleep(1)
to stream reading
methods to be more cpu friendly (thanks Sean McGinnis).
Fixed problem where ExecuteReader
would
sometime return null (thanks Lloyd Dupont).
Fixed major bug with null field handling (thanks Naucki).
Enclosed queries for max_allowed_packet
and
characterset
inside try catch (and set
defaults).
Fixed problem where socket was not getting closed properly (thanks Steve!).
Fixed problem where ExecuteNonQuery
was not
always returning the right value.
Fixed InternalConnection
to not use
@@session.max_allowed_packet
but use
@@max_allowed_packet
. (Thanks Miguel)
Added many new XML doc lines.
Fixed sql parsing to not send empty queries (thanks Rory).
Fixed problem where the reader was not unpeeking the packet on close.
Fixed problem where user variables were not being handled (thanks Sami Vaaraniemi).
Fixed loop checking in the MySqlPool (thanks Steve M. Brown)
Fixed ParameterCollection.Add
method to
match SqlClient
(thanks Joshua Mouch).
Fixed ConnectionString
parsing to handle no
and yes for boolean and not lowercase values (thanks Naucki).
Added InternalConnection
class, changes to
pooling.
Implemented Persist Security Info.
Added security.cs
and
version.cs
to project
Fixed DateTime
handling in
Parameter.cs
(thanks Burkhard
Perkens-Golomb).
Fixed parameter serialization where some types would throw a cast exception.
Fixed DataReader
to convert all returned
values to prevent casting errors (thanks Keith Murray).
Added code to Command.ExecuteReader
to
return null if the initial SQL statement throws an exception
(thanks Burkhard Perkens-Golomb).
Fixed ExecuteScalar
bug introduced with
restructure.
Restructure to allow for LOCAL DATA INFILE
and better sequencing of packets.
Fixed several bugs related to restructure.
Early work done to support more secure passwords in Mysql 4.1. Old passwords in 4.1 not supported yet.
Parameters appearing after system parameters are now handled correctly (Adam M. (adammil)).
Strings can now be assigned directly to blob fields (Adam M.).
Fixed float parameters (thanks Pent).
Improved Parameter constructor and
ParameterCollection.Add
methods to better
match SqlClient (thanks Joshua Mouch).
Corrected Connection.CreateCommand
to
return a MySqlCommand
type.
Fixed connection string designer dialog box problem (thanks Abraham Guyt).
Fixed problem with sending commands not always reading the response packet (thanks Joshua Mouch).
Fixed parameter serialization where some blobs types were not being handled (thanks Sean McGinnis).
Removed spurious MessageBox.show
from
DataReader
code (thanks Joshua Mouch).
Fixed a nasty bug in the split sql code (thanks everyone!).
Fixed bug in MySqlStream
where too much
data could attempt to be read (thanks Peter Belbin)
Implemented HasRows
(thanks Nash Pherson).
Fixed bug where tables with more than 252 columns cause an exception (thanks Joshua Kessler).
Fixed bug where SQL statements ending in ; would cause a problem (thanks Shane Krueger).
Fixed bug in driver where error messages were getting truncated by 1 character (thanks Shane Krueger).
Made MySqlException
serializable (thanks
Mathias Hasselmann).
Updated some of the character code pages to be more accurate.
Fixed problem where readers could be opened on connections that had readers open.
Moved test to separate assembly
MySqlClientTests
.
Fixed stupid problem in driver with sequence out of order (Thanks Peter Belbin).
Added some pipe tests.
Increased default max pool size to 50.
Compiles with Mono 0-24.
Fixed connection and data reader dispose problems.
Added String
datatype handling to parameter
serialization.
Fixed sequence problem in driver that occurred after thrown exception (thanks Burkhard Perkens-Golomb).
Added support for CommandBehavior.SingleRow
to DataReader
.
Fixed command sql processing so quotes are better handled (thanks Theo Spears).
Fixed parsing of double, single, and decimal values to account for non-English separators. You still have to use the right syntax if you using hard coded sql, but if you use parameters the code will convert floating point types to use '.' appropriately internal both into the server and out.
Added MySqlStream
class to simplify
timeouts and driver coding.
Fixed DataReader
so that it is closed
properly when the associated connection is closed. [thanks
smishra]
Made client more SqlClient compliant so that DataReaders have to be closed before the connection can be used to run another command.
Improved DBNull.Value
handling in the
fields.
Added several unit tests.
Fixed MySqlException
base class.
Improved driver coding
Fixed bug where NextResult was returning false on the last resultset.
Added more tests for MySQL.
Improved casting problems by equating unsigned 32bit values to Int64 and unsigned 16bit values to Int32, and so forth.
Added new constructor for MySqlParameter
for (name, type, size, srccol)
Fixed bug in MySqlDataReader
where it
didn't check for null fieldlist before returning field count.
Started adding MySqlClient
unit tests
(added MySqlClient/Tests
folder and some
test cases).
Fixed some things in Connection String handling.
Moved INIT_DB
to
MySqlPool
. I may move it again, this is in
preparation of the conference.
Fixed bug inside CommandBuilder
that
prevented inserts from happening properly.
Reworked some of the internals so that all three execute methods of Command worked properly.
Fixed many small bugs found during benchmarking.
The first cut of CoonectionPooling
is
working. "min pool size" and "max pool size" are respected.
Work to enable multiple resultsets to be returned.
Character sets are handled much more intelligently now. The driver queries MySQL at startup for the default character set. That character set is then used for conversions if that code page can be loaded. If not, then the default code page for the current OS is used.
Added code to save the inferred type in the name,value
constructor of Parameter
.
Also, inferred type if value of null parameter is changed
using Value
property.
Converted all files to use proper Camel case. MySQL is now MySql in all files. PgSQL is now PgSql.
Added attribute to PgSql code to prevent designer from trying to show.
Added MySQLDbType
property to Parameter
object and added proper conversion code to convert from
DbType
to MySQLDbType
).
Removed unused ObjectToString
method from
MySQLParameter.cs
.
Fixed Add(..)
method in
ParameterCollection
so that it doesn't use
Add(name, value)
instead.
Fixed IndexOf
and
Contains
in
ParameterCollection
to be aware that
parameter names are now stored without @.
Fixed Command.ConvertSQLToBytes
so it only
allows characters that can be in MySQL variable names.
Fixed DataReader
and
Field
so that blob fields read their data
from Field.cs
and
GetBytes
works right.
Added simple query builder editor to
CommandText
property of
MySQLCommand
.
Fixed CommandBuilder
and
Parameter
serialization to account for
Parameters not storing @ in their names.
Removed MySQLFieldType
enum from Field.cs.
Now using MySQLDbType
enum.
Added Designer
attribute to several classes
to prevent designer view when using VS.Net.
Fixed Initial catalog typo in
ConnectionString
designer.
Removed 3 parameter constructor for
MySQLParameter
that conflicted with (name,
type, value).
Changed MySQLParameter
so
paramName
is now stored without leading @
(this fixed null inserts when using designer).
Changed TypeConverter
for
MySQLParameter
to use the constructor with
all properties.
Fixed sequence issue in driver.
Added DbParametersEditor
to make parameter
editing more like SqlClient
.
Fixed Command
class so that parameters can
be edited using the designer
Update connection string designer to support Use
Compression
flag.
Fixed string encoding so that European characters like ä will work correctly.
Creating base classes to aid in building new data providers.
Added support for UID key in connection string.
Field, parameter, command now using DBNull.Value instead of null.
CommandBuilder
using
DBNull.Value
.
CommandBuilder
now builds insert command
correctly when an auto_insert field is not present.
Field now uses typeof keyword to return
System.Types
(performance).
MySQLCommandBuilder
now implemented.
Transaction support now implemented (not all table types support this).
GetSchemaTable
fixed to not use xsd (for
Mono).
Driver is now Mono-compatible.
TIME data type now supported.
More work to improve Timestamp data type handling.
Changed signatures of all classes to match corresponding
SqlClient
classes.
Protocol compression using SharpZipLib (www.icsharpcode.net).
Named pipes on Windows now working properly.
Work done to improve Timestamp
data type
handling.
Implemented IEnumerable
on
DataReader
so DataGrid
would work.
As of Connector/NET 5.1.2 (14 June 2007), the Visual Studion Plugin is part of the main Connector/NET package. For the change history for the Visual Studio Plugin, see Section C.4, “MySQL Connector/NET Change History”.
Bugs fixed:
Running queries based on a stored procedure would cause the data set designer to terminate. (Bugs #26364)
DataSet wizard would show all tables instead of only the tables available within the selected database. (Bugs #26348)
Bugs fixed:
The Add Connection dialog of the Server Explorer would freeze when accessing databases with capitalized characters in their name. (Bug#24875)
Creating a connection through the Server Explorer when using the Visual Studio Plugin would fail. The installer for the Visual Studio Plugin has been updated to ensure that Connector/NET 5.0.2 must be installed. (Bug#23071)
This is a bug fix release to resolve an incompatibility issue with Connector/NET 5.0.1.
It is critical that this release only be used with Connector/NET
5.0.1. After installing Connector/NET 5.0.1, you will need to
make a small change in your machine.config file. This file
should be located at
%win%\Microsoft.Net\Framework\v2.0.50727\CONFIG\machine.config
(%win%
should be the location of your Windows
folder). Near the bottom of the file you will see a line like
this:
<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data"/>
It needs to be changed to be like this:
<add name="MySQL Data Provider" invariant="MySql.Data.MySqlClient" description=".Net Framework Data Provider for MySQL" type="MySql.Data.MySqlClient.MySqlClientFactory, MySql.Data, Version=5.0.1.0, Culture=neutral, PublicKeyToken=c5687fc88969c44d"/>
Functionality added or changed:
XAConnections and datasources have been updated to the JDBC-4.0 standard.
The profiler event handling has been made extensible via the
profilerEventHandler
connection property.
Add the verifyServerCertificate
propery. If
set to "false" the driver will not verify the server's
certificate when useSSL
is set to "true"
When using this feature, the keystore parameters should be
specified by the clientCertificateKeyStore*
properties, rather than system properties, as the JSSE doesn't
it straightforward to have a non-verifying trust store and the
"default" key store.
Bugs fixed:
During a Daylight Savings Time (DST) switchover, there was no way to store two timestamp/datetime values , as the hours end up being the same when sent as the literal that MySQL requires.
Note that to get this scenario to work with MySQL (since it
doesn't support per-value timezones), you need to configure your
server (or session) to be in UTC, and tell the driver not to use
the legacy date/time code by setting
useLegacyDatetimeCode
to "false". This will
cause the driver to always convert to/from the server and client
timezone consistently.
This bug fix also fixes Bug#15604, by adding entirely new
date/time handling code that can be switched on by
useLegacyDatetimeCode
being set to "false" as a
JDBC configuration property. For Connector/J 5.1.x, the default
is "true", in trunk and beyond it will be "false" (i.e. the old
date/time handling code will be deprecated)
(Bug#32577, Bug#15604)
When unpacking rows directly, we don't hand off error message packets to the internal method which decodes them correctly, so no exception is raised, and the driver than hangs trying to read rows that aren't there. This tends to happen when calling stored procedures, as normal SELECTs won't have an error in this spot in the protocol unless an I/O error occurs. (Bug#32246)
When using a connection from
ConnectionPoolDataSource
, some
Connection.prepareStatement()
methods would
return null instead of the prepared statement.
(Bug#32101)
Using CallableStatement.setNull()
on a
stored function would throw an
ArrayIndexOutOfBounds
exception when setting
the last parameter to null.
(Bug#31823)
MysqlValidConnectionChecker
doesn't
properly handle connections created using
ReplicationConnection
.
(Bug#31790)
DatabaseMetadata.getColumns()
doesn't
return the correct column names if the connection character
isn't UTF-8. A bug in MySQL server compounded the issue, but was
fixed within the MySQL 5.0 release cycle. The fix includes
changes to all the sections of the code that access the server
metadata.
(Bug#20491)
Fixed ResultSetMetadata.getColumnName()
for result sets returned from
Statement.getGeneratedKeys()
- it was
returning null instead of "GENERATED_KEY" as in 5.0.x.
The following features are new, compared to the 5.0 series of Connector/J
Support for JDBC-4.0 NCHAR
,
NVARCHAR
and NCLOB
types.
JDBC-4.0 support for setting per-connection client information
(which can be viewed in the comments section of a query via
SHOW PROCESSLIST
on a MySQL server, or can be
extended to support custom persistence of the information via a
public interface).
Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX and StAX.
JDBC-4.0 standardized unwrapping to interfaces that include vendor extensions.
Functionality added or changed:
Added autoSlowLog
configuration property,
overrides slowQueryThreshold*
properties,
driver determines slow queries by those that are slower than 5 *
stddev of the mean query time (outside the 96% percentile).
Bugs fixed:
When a connection is in read-only mode, queries that are wrapped in parentheses were incorrectly identified DML statements. (Bug#28256)
The following features are new, compared to the 5.0 series of Connector/J
Support for JDBC-4.0 NCHAR
,
NVARCHAR
and NCLOB
types.
JDBC-4.0 support for setting per-connection client information
(which can be viewed in the comments section of a query via
SHOW PROCESSLIST
on a MySQL server, or can be
extended to support custom persistence of the information via a
public interface).
Support for JDBC-4.0 XML processing via JAXP interfaces to DOM, SAX and StAX.
JDBC-4.0 standardized unwrapping to interfaces that include vendor extensions.
Functionality added or changed:
Connector/J now connects using an initial character set of
utf-8
solely for the purpose of
authentication to allow user names or database names in any
character set to be used in the JDBC connection URL.
(Bug#29853)
Added two configuration parameters:
blobsAreStrings
— Should the driver
always treat BLOBs as Strings. Added specifically to work
around dubious metadata returned by the server for
GROUP BY
clauses. Defaults to false.
functionsNeverReturnBlobs
— Should
the driver always treat data from functions returning
BLOBs
as Strings. Added specifically to
work around dubious metadata returned by the server for
GROUP BY
clauses. Defaults to false.
Setting rewriteBatchedStatements
to
true
now causes CallableStatements with
batched arguments to be re-written in the form "CALL (...); CALL
(...); ..." to send the batch in as few client-server round
trips as possible.
The driver now picks appropriate internal row representation
(whole row in one buffer, or individual byte[]s for each column
value) depending on heuristics, including whether or not the row
has BLOB
or TEXT
types and
the overall row-size. The threshold for row size that will cause
the driver to use a buffer rather than individual byte[]s is
configured by the configuration property
largeRowSizeThreshold
, which has a default
value of 2KB.
The data (and how it's stored) for ResultSet
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.
Added experimental support for statement "interceptors" via the
com.mysql.jdbc.StatementInterceptor
interface, examples are in
com/mysql/jdbc/interceptors
. Implement this
interface to be placed "in between" query execution, so that it
can be influenced (currently experimental).
The driver will automatically adjust the server session variable
net_write_timeout
when it determines its been
asked for a "streaming" result, and resets it to the previous
value when the result set has been consumed. (The configuration
property is named
netTimeoutForStreamingResults
, with a unit of
seconds, the value '0' means the driver will not try and adjust
this value).
JDBC-4.0 ease-of-development features including
auto-registration with the DriverManager
via
the service provider mechanism, standardized Connection validity
checks and categorized SQLExceptions
based on
recoverability/retry-ability and class of the underlying error.
Statement.setQueryTimeout()
s now affect the
entire batch for batched statements, rather than the individual
statements that make up the batch.
Errors encountered during
Statement
/PreparedStatement
/CallableStatement.executeBatch()
when rewriteBatchStatements
has been set to
true
now return
BatchUpdateExceptions
according to the
setting of continueBatchOnError
.
If continueBatchOnError
is set to
true
, the update counts for the "chunk" that
were sent as one unit will all be set to
EXECUTE_FAILED
, but the driver will attempt
to process the remainder of the batch. You can determine which
"chunk" failed by looking at the update counts returned in the
BatchUpdateException
.
If continueBatchOnError
is set to "false",
the update counts returned will contain all updates up-to and
including the failed "chunk", with all counts for the failed
"chunk" set to EXECUTE_FAILED
.
Since MySQL doesn't return multiple error codes for
multiple-statements, or for multi-value
INSERT
/REPLACE
, it is the
application's responsibility to handle determining which item(s)
in the "chunk" actually failed.
New methods on com.mysql.jdbc.Statement:
setLocalInfileInputStream()
and
getLocalInfileInputStream()
:
setLocalInfileInputStream()
sets an
InputStream
instance that will be used to
send data to the MySQL server for a LOAD DATA LOCAL
INFILE
statement rather than a
FileInputStream
or
URLInputStream
that represents the path
given as an argument to the statement.
This stream will be read to completion upon execution of a
LOAD DATA LOCAL INFILE
statement, and
will automatically be closed by the driver, so it needs to
be reset before each call to execute*()
that would cause the MySQL server to request data to fulfill
the request for LOAD DATA LOCAL INFILE
.
If this value is set to NULL
, the driver
will revert to using a FileInputStream
or
URLInputStream
as required.
getLocalInfileInputStream()
returns the
InputStream
instance that will be used to
send data in response to a LOAD DATA LOCAL
INFILE
statement.
This method returns NULL
if no such
stream has been set via
setLocalInfileInputStream()
.
Setting useBlobToStoreUTF8OutsideBMP
to
true
tells the driver to treat
[MEDIUM/LONG]BLOB
columns as
[LONG]VARCHAR
columns holding text encoded in
UTF-8 that has characters outside the BMP (4-byte encodings),
which MySQL server can't handle natively.
Set utf8OutsideBmpExcludedColumnNamePattern
to
a regex so that column names matching the given regex will still
be treated as BLOBs
The regex must follow the
patterns used for the java.util.regex
package. The default is to exclude no columns, and
include all columns.
Set utf8OutsideBmpIncludedColumnNamePattern
to
specify exclusion rules to
utf8OutsideBmpExcludedColumnNamePattern". The regex must follow
the patterns used for the java.util.regex
package.
Bugs fixed:
setObject(int, Object, int, int)
delegate in
PreparedStatmentWrapper delegates to wrong method.
(Bug#30892)
NPE with null column values when
padCharsWithSpace
is set to true.
(Bug#30851)
Collation on VARBINARY
column types would be
misidentified. A fix has been added, but this fix only works for
MySQL server versions 5.0.25 and newer, since earlier versions
didn't consistently return correct metadata for functions, and
thus results from subqueries and functions were
indistinguishable from each other, leading to type-related bugs.
(Bug#30664)
An ArithmeticException
or
NullPointerException
would be raised when the
batch had zero members and
rewriteBatchedStatements=true
when
addBatch()
was never called, or
executeBatch()
was called immediately after
clearBatch()
.
(Bug#30550)
Closing a load-balanced connection would cause a
ClassCastException
.
(Bug#29852)
Connection checker for JBoss didn't use same method parameters via reflection, causing connections to always seem "bad". (Bug#29106)
DatabaseMetaData.getTypeInfo()
for the types
DECIMAL
and NUMERIC
will
return a precision of 254 for server versions older than 5.0.3,
64 for versions 5.0.3-5.0.5 and 65 for versions newer than
5.0.5.
(Bug#28972)
CallableStatement.executeBatch()
doesn't work
when connection property
noAccessToProcedureBodies
has been set to
true
.
The fix involves changing the behavior of
noAccessToProcedureBodies
,in that the driver
will now report all paramters as "IN" paramters but allow
callers to call registerOutParameter() on them without throwing
an exception.
(Bug#28689)
DatabaseMetaData.getColumns()
doesn't contain
SCOPE_*
or
IS_AUTOINCREMENT
columns.
(Bug#27915)
Schema objects with identifiers other than the connection
character aren't retrieved correctly in
ResultSetMetadata
.
(Bug#27867)
Connection.getServerCharacterEncoding()
doesn't work for servers with version >= 4.1.
(Bug#27182)
The automated SVN revisions in
DBMD.getDriverVersion()
. The SVN revision of
the directory is now inserted into the version information
during the build.
(Bug#21116)
Specifying a "validation query" in your connection pool that starts with "/* ping */" _exactly_ will cause the driver to instead send a ping to the server and return a fake result set (much lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection, will send the ping across all active connections.
This is a new Beta development release, fixing recently discovered bugs.
Functionality added or changed:
Setting the configuration property
rewriteBatchedStatements
to
true
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 (i.e. without
or SELECT
or ON DUPLICATE KEY UPDATE
clauses) INSERT
REPLACE
statements.
This is a new Alpha development release, adding new features and fixing recently discovered bugs.
Functionality added or changed:
Incompatible Change:
Pulled vendor-extension methods of Connection
implementation out into an interface to support
java.sql.Wrapper
functionality from
ConnectionPoolDataSource
. The vendor
extensions are javadoc'd in the
com.mysql.jdbc.Connection
interface.
For those looking further into the driver implementation, it is
not an API that is used for plugability of implementations
inside our driver (which is why there are still references to
ConnectionImpl
throughout the code).
We've also added server and client
prepareStatement()
methods that cover all of
the variants in the JDBC API.
Connection.serverPrepare(String)
has been
re-named to
Connection.serverPrepareStatement()
for
consistency with
Connection.clientPrepareStatement()
.
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.
Made it possible to retrieve prepared statement parameter
bindings (to be used in
StatementInterceptors
, primarily).
Externalized the descriptions of connection properties.
The data (and how it's stored) for ResultSet
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.
Similar to Connection
, we pulled out vendor
extensions to Statement
into an interface
named com.mysql.Statement
, and moved the
Statement
class into
com.mysql.StatementImpl
. The two methods
(javadoc'd in com.mysql.Statement
are
enableStreamingResults()
, which already
existed, and disableStreamingResults()
which
sets the statement instance back to the fetch size and result
set type it had before
enableStreamingResults()
was called.
Driver now picks appropriate internal row representation (whole
row in one buffer, or individual byte[]s for each column value)
depending on heuristics, including whether or not the row has
BLOB
or TEXT
types and the
overall row-size. The threshold for row size that will cause the
driver to use a buffer rather than individual byte[]s is
configured by the configuration property
largeRowSizeThreshold
, which has a default
value of 2KB.
Added experimental support for statement
"interceptors" via the
com.mysql.jdbc.StatementInterceptor
interface, examples are in
com/mysql/jdbc/interceptors
.
Implement this interface to be placed "in between" query execution, so that you can influence it. (currently experimental).
StatementInterceptors
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
statementInterceptors
.
See the sources (fully javadoc'd) for
com.mysql.jdbc.StatementInterceptor
for more
details until we iron out the API and get it documented in the
manual.
Setting rewriteBatchedStatements
to
true
now causes
CallableStatements
with batched arguments to
be re-written in the form CALL (...); CALL (...);
...
to send the batch in as few client-server round
trips as possible.
This is the first public alpha release of the current Connector/J 5.1 development branch, providing an insight to upcoming features. Although some of these are still under development, this release includes the following new features and changes (in comparison to the current Connector/J 5.0 production release):
Important change: 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.
To enable server-side prepared statements you must add the following configuration property to your connector string:
useServerPrepStmts=true
The default value of this property is false
(that is, Connector/J does not use server-side prepared
statements).
The disabling of server-side prepared statements does not
affect the operation of the connector. However, if you use the
useTimezone=true
connection option and use
client-side prepared statements (instead of server-side
prepared statements) you should also set
useSSPSCompatibleTimezoneShift=true
.
Functionality added or changed:
Refactored CommunicationsException
into a
JDBC-3.0 version, and a JDBC-4.0 version (which extends
SQLRecoverableException
, now that it exists).
This change means that if you were catching
com.mysql.jdbc.CommunicationsException
in
your applications instead of looking at the SQLState class of
08
, and are moving to Java 6 (or newer),
you need to change your imports to that exception to be
com.mysql.jdbc.exceptions.jdbc4.CommunicationsException
,
as the old class will not be instantiated for communications
link-related errors under Java 6.
Added support for JDBC-4.0 categorized
SQLExceptions
.
Added support for JDBC-4.0's NCLOB
, and
NCHAR
/NVARCHAR
types.
com.mysql.jdbc.java6.javac
— full path
to your Java-6 javac executable
Added support for JDBC-4.0's SQLXML interfaces.
Re-worked Ant buildfile to build JDBC-4.0 classes separately, as well as support building under Eclipse (since Eclipse can't mix/match JDKs).
To build, you must set JAVA_HOME
to
J2SDK-1.4.2 or Java-5, and set the following properties on your
Ant command line:
com.mysql.jdbc.java6.javac
— full
path to your Java-6 javac executable
com.mysql.jdbc.java6.rtjar
— full
path to your Java-6 rt.jar
file
New feature — driver will automatically adjust session
variable net_write_timeout
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
netTimeoutForStreamingResults
value and has a
unit of seconds, the value 0
means the driver
will not try and adjust this value).
Added support for JDBC-4.0's client information. The backend
storage of information provided via
Connection.setClientInfo()
and retrieved by
Connection.getClientInfo()
is pluggable by
any class that implements the
com.mysql.jdbc.JDBC4ClientInfoProvider
interface and has a no-args constructor.
The implementation used by the driver is configured using the
clientInfoProvider
configuration property
(with a default of value of
com.mysql.jdbc.JDBC4CommentClientInfoProvider
,
an implementation which lists the client information as a
comment prepended to every query sent to the server).
This functionality is only available when using Java-6 or newer.
com.mysql.jdbc.java6.rtjar
— full path
to your Java-6 rt.jar
file
Added support for JDBC-4.0's Wrapper
interface.
Functionality added or changed:
blobsAreStrings
— Should the driver
always treat BLOBs as Strings. Added specifically to work around
dubious metadata returned by the server for GROUP
BY
clauses. Defaults to false.
Added two configuration parameters:
blobsAreStrings
— Should the driver
always treat BLOBs as Strings. Added specifically to work
around dubious metadata returned by the server for
GROUP BY
clauses. Defaults to false.
functionsNeverReturnBlobs
— Should
the driver always treat data from functions returning
BLOBs
as Strings. Added specifically to
work around dubious metadata returned by the server for
GROUP BY
clauses. Defaults to false.
functionsNeverReturnBlobs
— Should the
driver always treat data from functions returning
BLOBs
as Strings. Added specifically to work
around dubious metadata returned by the server for
GROUP BY
clauses. Defaults to false.
XAConnections now start in auto-commit mode (as per JDBC-4.0 specification clarification).
Driver will now fall back to sane defaults for
max_allowed_packet
and
net_buffer_length
if the server reports them
incorrectly (and will log this situation at
WARN
level, since it's actually an error
condition).
Bugs fixed:
Connections established using URLs of the form
jdbc:mysql:loadbalance://
weren't doing
failover if they tried to connect to a MySQL server that was
down. The driver now attempts connections to the next "best"
(depending on the load balance strategy in use) server, and
continues to attempt connecting to the next "best" server every
250 milliseconds until one is found that is up and running or 5
minutes has passed.
If the driver gives up, it will throw the last-received
SQLException
.
(Bug#31053)
setObject(int, Object, int, int)
delegate in
PreparedStatmentWrapper delegates to wrong method.
(Bug#30892)
NPE with null column values when
padCharsWithSpace
is set to true.
(Bug#30851)
Collation on VARBINARY
column types would be
misidentified. A fix has been added, but this fix only works for
MySQL server versions 5.0.25 and newer, since earlier versions
didn't consistently return correct metadata for functions, and
thus results from subqueries and functions were
indistinguishable from each other, leading to type-related bugs.
(Bug#30664)
An ArithmeticException
or
NullPointerException
would be raised when the
batch had zero members and
rewriteBatchedStatements=true
when
addBatch()
was never called, or
executeBatch()
was called immediately after
clearBatch()
.
(Bug#30550)
Closing a load-balanced connection would cause a
ClassCastException
.
(Bug#29852)
Connection checker for JBoss didn't use same method parameters via reflection, causing connections to always seem "bad". (Bug#29106)
DatabaseMetaData.getTypeInfo()
for the types
DECIMAL
and NUMERIC
will
return a precision of 254 for server versions older than 5.0.3,
64 for versions 5.0.3-5.0.5 and 65 for versions newer than
5.0.5.
(Bug#28972)
CallableStatement.executeBatch()
doesn't work
when connection property
noAccessToProcedureBodies
has been set to
true
.
The fix involves changing the behavior of
noAccessToProcedureBodies
,in that the driver
will now report all paramters as "IN" paramters but allow
callers to call registerOutParameter() on them without throwing
an exception.
(Bug#28689)
When a connection is in read-only mode, queries that are wrapped in parentheses were incorrectly identified DML statements. (Bug#28256)
UNSIGNED
types not reported via
DBMD.getTypeInfo()
, and capitalization of
type names is not consistent between
DBMD.getColumns()
,
RSMD.getColumnTypeName()
and
DBMD.getTypeInfo()
.
This fix also ensures that the precision of UNSIGNED
MEDIUMINT
and UNSIGNED BIGINT
is
reported correctly via DBMD.getColumns()
.
(Bug#27916)
DatabaseMetaData.getColumns()
doesn't contain
SCOPE_*
or
IS_AUTOINCREMENT
columns.
(Bug#27915)
Schema objects with identifiers other than the connection
character aren't retrieved correctly in
ResultSetMetadata
.
(Bug#27867)
Cached metadata with
PreparedStatement.execute()
throws
NullPointerException
.
(Bug#27412)
Connection.getServerCharacterEncoding()
doesn't work for servers with version >= 4.1.
(Bug#27182)
The automated SVN revisions in
DBMD.getDriverVersion()
. The SVN revision of
the directory is now inserted into the version information
during the build.
(Bug#21116)
Specifying a "validation query" in your connection pool that starts with "/* ping */" _exactly_ will cause the driver to instead send a ping to the server and return a fake result set (much lighter weight), and when using a ReplicationConnection or a LoadBalancedConnection, will send the ping across all active connections.
Functionality added or changed:
The driver will now automatically set
useServerPrepStmts
to true
when useCursorFetch
has been set to
true
, since the feature requires server-side
prepared statements in order to function.
tcpKeepAlive
- Should the driver set
SO_KEEPALIVE (default true
)?
Give more information in EOFExceptions thrown out of MysqlIO (how many bytes the driver expected to read, how many it actually read, say that communications with the server were unexpectedly lost).
Driver detects when it is running in a ColdFusion MX server
(tested with version 7), and uses the configuration bundle
coldFusion
, which sets
useDynamicCharsetInfo
to
false
(see previous entry), and sets
useLocalSessionState
and autoReconnect to
true
.
tcpNoDelay
- Should the driver set
SO_TCP_NODELAY (disabling the Nagle Algorithm, default
true
)?
Added configuration property
slowQueryThresholdNanos
- if
useNanosForElapsedTime
is set to
true
, and this property is set to a non-zero
value the driver will use this threshold (in nanosecond units)
to determine if a query was slow, instead of using millisecond
units.
tcpRcvBuf
- Should the driver set SO_RCV_BUF
to the given value? The default value of '0', means use the
platform default value for this property.
Setting useDynamicCharsetInfo
to
false
now causes driver to use static lookups
for collations as well (makes
ResultSetMetadata.isCaseSensitive() much more efficient, which
leads to performance increase for ColdFusion, which calls this
method for every column on every table it sees, it appears).
Added configuration properties to allow tuning of TCP/IP socket parameters:
tcpNoDelay
- Should the driver set
SO_TCP_NODELAY (disabling the Nagle Algorithm, default
true
)?
tcpKeepAlive
- Should the driver set
SO_KEEPALIVE (default true
)?
tcpRcvBuf
- Should the driver set
SO_RCV_BUF to the given value? The default value of '0',
means use the platform default value for this property.
tcpSndBuf
- Should the driver set
SO_SND_BUF to the given value? The default value of '0',
means use the platform default value for this property.
tcpTrafficClass
- Should the driver set
traffic class or type-of-service fields? See the
documentation for java.net.Socket.setTrafficClass() for more
information.
Setting the configuration parameter
useCursorFetch
to true
for
MySQL-5.0+ enables the use of cursors that allow Connector/J to
save memory by fetching result set rows in chunks (where the
chunk size is set by calling setFetchSize() on a Statement or
ResultSet) by using fully-materialized cursors on the server.
tcpSndBuf
- Should the driver set SO_SND_BUF
to the given value? The default value of '0', means use the
platform default value for this property.
tcpTrafficClass
- Should the driver set
traffic class or type-of-service fields? See the documentation
for java.net.Socket.setTrafficClass() for more information.
Added new debugging functionality - Setting configuration
property
includeInnodbStatusInDeadlockExceptions
to
true
will cause the driver to append the
output of SHOW ENGINE INNODB STATUS
to
deadlock-related exceptions, which will enumerate the current
locks held inside InnoDB.
Added configuration property
useNanosForElapsedTime
- for
profiling/debugging functionality that measures elapsed time,
should the driver try to use nanoseconds resolution if available
(requires JDK >= 1.5)?
If useNanosForElapsedTime
is set to
true
, 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).
Bugs fixed:
Don't send any file data in response to LOAD DATA LOCAL INFILE 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. (Bug#29605)
Parser in client-side prepared statements runs to end of statement, rather than end-of-line for '#' comments. Also added support for '--' single-line comments. (Bug#28956)
Parser in client-side prepared statements eats character following '/' if it's not a multi-line comment. (Bug#28851)
PreparedStatement.getMetaData() for statements containing leading one-line comments is not returned correctly.
As part of this fix, we also overhauled detection of DML for
executeQuery()
and SELECT
s
for executeUpdate()
in plain and prepared
statements to be aware of the same types of comments.
(Bug#28469)
Functionality added or changed:
Added an experimental load-balanced connection designed for use
with SQL nodes in a MySQL Cluster/NDB environment (This is not
for master-slave replication. For that, we suggest you look at
ReplicationConnection
or
lbpool
).
If the JDBC URL starts with
jdbc:mysql:loadbalance://host-1,host-2,...host-n
,
the driver will create an implementation of
java.sql.Connection
that load balances
requests across a series of MySQL JDBC connections to the given
hosts, where the balancing takes place after transaction commit.
Therefore, for this to work (at all), you must use transactions, even if only reading data.
Physical connections to the given hosts will not be created until needed.
The driver will invalidate connections that it detects have had communication errors when processing a request. A new connection to the problematic host will be attempted the next time it is selected by the load balancing algorithm.
There are two choices for load balancing algorithms, which may
be specified by the loadBalanceStrategy
JDBC
URL configuration property:
random
— the driver will pick a
random host for each request. This tends to work better than
round-robin, as the randomness will somewhat account for
spreading loads where requests vary in response time, while
round-robin can sometimes lead to overloaded nodes if there
are variations in response times across the workload.
bestResponseTime
— the driver will
route the request to the host that had the best response
time for the previous transaction.
bestResponseTime
— the driver will
route the request to the host that had the best response time
for the previous transaction.
Added configuration property
padCharsWithSpace
(defaults to
false
). If set to true
,
and a result set column has the CHAR
type and
the value does not fill the amount of characters specified in
the DDL for the column, the driver will pad the remaining
characters with space (for ANSI compliance).
When useLocalSessionState
is set to
true
and connected to a MySQL-5.0 or later
server, the JDBC driver will now determine whether an actual
commit
or rollback
statement needs to be sent to the database when
Connection.commit()
or
Connection.rollback()
is called.
This is especially helpful for high-load situations with
connection pools that always call
Connection.rollback()
on connection
check-in/check-out because it avoids a round-trip to the server.
Added configuration property
useDynamicCharsetInfo
. If set to
false
(the default), the driver will use a
per-connection cache of character set information queried from
the server when necessary, or when set to
true
, use a built-in static mapping that is
more efficient, but isn't aware of custom character sets or
character sets implemented after the release of the JDBC driver.
This only affects the padCharsWithSpace
configuration property and the
ResultSetMetaData.getColumnDisplayWidth()
method.
New configuration property,
enableQueryTimeouts
(default
true
).
When enabled, query timeouts set via
Statement.setQueryTimeout()
use a shared
java.util.Timer
instance for scheduling. Even
if the timeout doesn't expire before the query is processed,
there will be memory used by the TimerTask
for the given timeout which won't be reclaimed until the time
the timeout would have expired if it hadn't been cancelled by
the driver. High-load environments might want to consider
disabling this functionality. (this configuration property is
part of the maxPerformance
configuration
bundle).
Give better error message when "streaming" result
sets, and the connection gets clobbered because of exceeding
net_write_timeout
on the server.
random
— the driver will pick a random
host for each request. This tends to work better than
round-robin, as the randomness will somewhat account for
spreading loads where requests vary in response time, while
round-robin can sometimes lead to overloaded nodes if there are
variations in response times across the workload.
com.mysql.jdbc.[NonRegistering]Driver
now
understands URLs of the format
jdbc:mysql:replication://
and
jdbc:mysql:loadbalance://
which will create a
ReplicationConnection (exactly like when using
[NonRegistering]ReplicationDriver
) and an
experimental load-balanced connection designed for use with SQL
nodes in a MySQL Cluster/NDB environment, respectively.
In an effort to simplify things, we're working on deprecating
multiple drivers, and instead specifying different core behavior
based upon JDBC URL prefixes, so watch for
[NonRegistering]ReplicationDriver
to
eventually disappear, to be replaced with
com.mysql.jdbc[NonRegistering]Driver
with the
new URL prefix.
Fixed issue where a failed-over connection would let an
application call setReadOnly(false)
, when
that call should be ignored until the connection is reconnected
to a writable master unless failoverReadOnly
had been set to false
.
Driver will now use INSERT INTO ... VALUES (DEFAULT)
form of statement for updatable result sets for
ResultSet.insertRow()
, rather than
pre-populating the insert row with values from
DatabaseMetaData.getColumns()
(which results
in a SHOW FULL COLUMNS
on the server for
every result set). If an application requires access to the
default values before insertRow()
has been
called, the JDBC URL should be configured with
populateInsertRowWithDefaultValues
set to
true
.
This fix specifically targets performance issues with ColdFusion and the fact that it seems to ask for updatable result sets no matter what the application does with them.
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.
Bugs fixed:
More useful error messages are generated when the driver thinks a result set is not updatable. (Thanks to Ashley Martens for the patch). (Bug#28085)
Connection.getTransactionIsolation()
uses
"SHOW VARIABLES LIKE
" which is very
inefficient on MySQL-5.0+ servers.
(Bug#27655)
Fixed issue where calling getGeneratedKeys()
on a prepared statement after calling
execute()
didn't always return the generated
keys (executeUpdate()
worked fine however).
(Bug#27655)
CALL /* ... */
doesn't work.
As a side effect of this fix, you can now use some_proc
()/*
*/
and #
comments when preparing
statements using client-side prepared statement emulation.
If the comments happen to contain parameter markers
(?
), they will be treated as belonging to the
comment (that is, not recognized) rather than being a parameter
of the statement.
The statement when sent to the server will contain the
comments as-is, they're not stripped during the process of
preparing the PreparedStatement
or
CallableStatement
.
ResultSet.get*()
with a column index < 1
returns misleading error message.
(Bug#27317)
Using ResultSet.get*()
with a column index
less than 1 returns a misleading error message.
(Bug#27317)
Comments in DDL of stored procedures/functions confuse procedure parser, and thus metadata about them can not be created, leading to inability to retrieve said metadata, or execute procedures that have certain comments in them. (Bug#26959)
Fast date/time parsing doesn't take into account
00:00:00
as a legal value.
(Bug#26789)
PreparedStatement
is not closed in
BlobFromLocator.getBytes()
.
(Bug#26592)
When the configuration property
useCursorFetch
was set to
true
, sometimes server would return new, more
exact metadata during the execution of the server-side prepared
statement that enables this functionality, which the driver
ignored (using the original metadata returned during
prepare()
), causing corrupt reading of data
due to type mismatch when the actual rows were returned.
(Bug#26173)
CallableStatements
with
OUT/INOUT
parameters that are
"binary" (BLOB
,
BIT
, (VAR)BINARY
,
JAVA_OBJECT
) have extra 7 bytes.
(Bug#25715)
Whitespace surrounding storage/size specifiers in stored
procedure parameters declaration causes
NumberFormatException
to be thrown when
calling stored procedure on JDK-1.5 or newer, as the Number
classes in JDK-1.5+ are whitespace intolerant.
(Bug#25624)
Client options not sent correctly when using SSL, leading to stored procedures not being able to return results. Thanks to Don Cohen for the bug report, testcase and patch. (Bug#25545)
Statement.setMaxRows()
is not effective on
result sets materialized from cursors.
(Bug#25517)
BIT(> 1)
is returned as
java.lang.String
from
ResultSet.getObject()
rather than
byte[]
.
(Bug#25328)
Functionality added or changed:
Usage Advisor will now issue warnings for result sets with large
numbers of rows. You can configure the trigger value by using
the resultSetSizeThreshold
parameter, which
has a default value of 100.
The rewriteBatchedStatements
feature can now
be used with server-side prepared statements.
Important change: 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.
To enable server-side prepared statements you must add the following configuration property to your connector string:
useServerPrepStmts=true
The default value of this property is false
(that is, Connector/J does not use server-side prepared
statements).
Improved speed of datetime
parsing for
ResultSets that come from plain or non-server-side prepared
statements. You can enable old implementation with
useFastDateParsing=false
as a configuration
parameter.
Usage Advisor now detects empty results sets and does not report on columns not referenced in those empty sets.
Fixed logging of XA commands sent to server, it's now
configurable via logXaCommands
property
(defaults to false
).
Added configuration property
localSocketAddress
,which is the hostname or
IP address given to explicitly configure the interface that the
driver will bind the client side of the TCP/IP connection to
when connecting.
We've added a new configuration option
treatUtilDateAsTimestamp
, which is
false
by default, as (1) We already had
specific behavior to treat java.util.Date as a
java.sql.Timestamp because it's useful to many folks, and (2)
that behavior will very likely be required for drivers
JDBC-post-4.0.
Bugs fixed:
Connection property socketFactory
wasn't
exposed via correctly named mutator/accessor, causing data
source implementations that use JavaBean naming conventions to
set properties to fail to set the property (and in the case of
SJAS, fail silently when trying to set this parameter).
(Bug#26326)
A query execution which timed out did not always throw a
MySQLTimeoutException
.
(Bug#25836)
Storing a java.util.Date
object in a
BLOB
column would not be serialized correctly
during setObject
.
(Bug#25787)
Timer instance used for
Statement.setQueryTimeout()
created
per-connection, rather than per-VM, causing memory leak.
(Bug#25514)
EscapeProcessor
gets confused by multiple
backslashes. We now push the responsibility of syntax errors
back on to the server for most escape sequences.
(Bug#25399)
INOUT
parameters in
CallableStatements
get doubly-escaped.
(Bug#25379)
When using the rewriteBatchedStatements
connection option with
PreparedState.executeBatch()
an internal
memory leak would occur.
(Bug#25073)
Fixed issue where field-level for metadata from
DatabaseMetaData
when using
INFORMATION_SCHEMA
didn't have references to
current connections, sometimes leading to Null Pointer
Exceptions (NPEs) when introspecting them via
ResultSetMetaData
.
(Bug#25073)
StringUtils.indexOfIgnoreCaseRespectQuotes()
isn't case-insensitive on the first character of the target.
This bug also affected
rewriteBatchedStatements
functionality when
prepared statements did not use uppercase for the
VALUES
clause.
(Bug#25047)
Client-side prepared statement parser gets confused by in-line
comments /*...*/
and therefore cannot rewrite
batch statements or reliably detect the type of statements when
they are used.
(Bug#25025)
Results sets from UPDATE
statements that are
part of multi-statement queries would cause an
SQLException
error, "Result is from
UPDATE".
(Bug#25009)
Specifying US-ASCII
as the character set in a
connection to a MySQL 4.1 or newer server does not map
correctly.
(Bug#24840)
Using DatabaseMetaData.getSQLKeywords()
does
not return a all of the of the reserved keywords for the current
MySQL version. Current implementation returns the list of
reserved words for MySQL 5.1, and does not distinguish between
versions.
(Bug#24794)
Calling Statement.cancel()
could result in a
Null Pointer Exception (NPE).
(Bug#24721)
Using setFetchSize()
breaks prepared
SHOW
and other commands.
(Bug#24360)
Calendars and timezones are now lazily instantiated when required. (Bug#24351)
Using DATETIME
columns would result in time
shifts when useServerPrepStmts
was true. The
reason was due to different behavior when using client-side
compared to server-side prepared statements and the
useJDBCCompliantTimezoneShift
option. This is
now fixed if moving from server-side prepared statements to
client-side prepared statements by setting
useSSPSCompatibleTimezoneShift
to
true
, as the driver can't tell if this is a
new deployment that never used server-side prepared statements,
or if it is an existing deployment that is switching to
client-side prepared statements from server-side prepared
statements.
(Bug#24344)
Connector/J now returns a better error message when server doesn't return enough information to determine stored procedure/function parameter types. (Bug#24065)
A connection error would occur when connecting to a MySQL server
with certain 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)
Inconsistency between getSchemas
and
INFORMATION_SCHEMA
.
(Bug#23304)
DatabaseMetaData.getSchemas()
doesn't return
a TABLE_CATALOG
column.
(Bug#23303)
When using a JDBC connection URL that is malformed, the
NonRegisteringDriver.getPropertyInfo
method
will throw a Null Pointer Exception (NPE).
(Bug#22628)
Some exceptions thrown out of
StandardSocketFactory
were needlessly
wrapped, obscuring their true cause, especially when using
socket timeouts.
(Bug#21480)
When using a server-side prepared statement the driver would send timestamps to the server using nanoseconds instead of milliseconds. (Bug#21438)
When using server-side prepared statements and timestamp columns, value would be incorrectly populated (with nanoseconds, not microseconds). (Bug#21438)
ParameterMetaData
throws
NullPointerException
when prepared SQL has a
syntax error. Added
generateSimpleParameterMetadata
configuration
property, which when set to true
will
generate metadata reflecting VARCHAR
for
every parameter (the default is false
, which
will cause an exception to be thrown if no parameter metadata
for the statement is actually available).
(Bug#21267)
Fixed an issue where XADataSources
couldn't
be bound into JNDI, as the DataSourceFactory
didn't know how to create instances of them.
Other changes:
Avoid static synchronized code in JVM class libraries for dealing with default timezones.
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.
Re-worked stored procedure parameter parser to be more robust.
Driver no longer requires BEGIN
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.
Throw exceptions encountered during timeout to thread calling
Statement.execute*()
, rather than
RuntimeException
.
Changed cached result set metadata (when using
cacheResultSetMetadata=true
) to be cached
per-connection rather than per-statement as previously
implemented.
Reverted back to internal character conversion routines for single-byte character sets, as the ones internal to the JVM are using much more CPU time than our internal implementation.
When extracting foreign key information from SHOW
CREATE TABLE
in DatabaseMetaData
,
ignore exceptions relating to tables being missing (which could
happen for cross-reference or imported-key requests, as the list
of tables is generated first, then iterated).
Fixed some Null Pointer Exceptions (NPEs) when cached metadata
was used with UpdatableResultSets
.
Take localSocketAddress
property into account
when creating instances of
CommunicationsException
when the underyling
exception is a java.net.BindException
, so
that a friendlier error message is given with a little internal
diagnostics.
Fixed cases where ServerPreparedStatements
weren't using cached metadata when
cacheResultSetMetadata=true
was used.
Use a java.util.TreeMap
to map column names
to ordinal indexes for ResultSet.findColumn()
instead of a HashMap. This allows us to have case-insensitive
lookups (required by the JDBC specification) without resorting
to the many transient object instances needed to support this
requirement with a normal HashMap
with either
case-adjusted keys, or case-insensitive keys. (In the worst case
scenario for lookups of a 1000 column result set, TreeMaps are
about half as fast wall-clock time as a HashMap, however in
normal applications their use gives many orders of magnitude
reduction in transient object instance creation which pays off
later for CPU usage in garbage collection).
When using cached metadata, skip field-level metadata packets
coming from the server, rather than reading them and discarding
them without creating com.mysql.jdbc.Field
instances.
Bugs fixed:
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. (Bug#22613)
Added new _ci collations to CharsetMapping - utf8_unicode_ci not working. (Bug#22456)
Driver was using milliseconds for Statement.setQueryTimeout() when specification says argument is to be in seconds. (Bug#22359)
Workaround for server crash when calling stored procedures via a server-side prepared statement (driver now detects prepare(stored procedure) and substitutes client-side prepared statement). (Bug#22297)
Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement). (Bug#22290)
Newlines causing whitespace to span confuse procedure parser when getting parameter metadata for stored procedures. (Bug#22024)
When using information_schema for metadata, COLUMN_SIZE for getColumns() is not clamped to range of java.lang.Integer as is the case when not using information_schema, thus leading to a truncation exception that isn't present when not using information_schema. (Bug#21544)
Column names don't match metadata in cases where server doesn't return original column names (column functions) thus breaking compatibility with applications that expect 1-1 mappings between findColumn() and rsmd.getColumnName(), usually manifests itself as "Can't find column ('')" exceptions. (Bug#21379)
Driver now sends numeric 1 or 0 for client-prepared statement
setBoolean()
calls instead of '1' or '0'.
Fixed configuration property
jdbcCompliantTruncation
was not being used
for reads of result set values.
DatabaseMetaData correctly reports true
for
supportsCatalog*()
methods.
Driver now supports {call sp}
(without
"()" if procedure has no arguments).
Functionality added or changed:
Added configuration option
noAccessToProcedureBodies
which will cause
the driver to create basic parameter metadata for
CallableStatements
when the user does not
have access to procedure bodies via SHOW CREATE
PROCEDURE
or selecting from
mysql.proc
instead of throwing an exception.
The default value for this option is false
Bugs fixed:
Fixed Statement.cancel()
causes
NullPointerException
if underlying connection
has been closed due to server failure.
(Bug#20650)
If the connection to the server has been closed due to a server
failure, then the cleanup process will call
Statement.cancel()
, triggering a
NullPointerException
, even though there is no
active connection.
(Bug#20650)
Bugs fixed:
MysqlXaConnection.recover(int flags)
now
allows combinations of
XAResource.TMSTARTRSCAN
and
TMENDRSCAN
. To simulate the
“scanning” nature of the interface, we return all
prepared XIDs for TMSTARTRSCAN
, and no new
XIDs for calls with TMNOFLAGS
, or
TMENDRSCAN
when not in combination with
TMSTARTRSCAN
. This change was made for API
compliance, as well as integration with IBM WebSphere's
transaction manager.
(Bug#20242)
Fixed MysqlValidConnectionChecker
for JBoss
doesn't work with MySQLXADataSources
.
(Bug#20242)
Added connection/datasource property
pinGlobalTxToPhysicalConnection
(defaults to
false
). When set to true
,
when using XAConnections
, 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).
(Bug#20242)
Better caching of character set converters (per-connection) to remove a bottleneck for multibyte character sets. (Bug#20242)
Fixed ConnectionProperties
(and thus some
subclasses) are not serializable, even though some J2EE
containers expect them to be.
(Bug#19169)
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
systtem variable to the character
set that is used for error messages.
(Bug#18086)
Fixed can't use XAConnection
for local
transactions when no global transaction is in progress.
(Bug#17401)
Bugs fixed:
Added support for Connector/MXJ integration via url subprotocol
jdbc:mysql:mxj://...
.
(Bug#14729)
Idle timeouts cause XAConnections
to whine
about rolling themselves back.
(Bug#14729)
When fix for Bug#14562 was merged from 3.1.12, added
functionality for CallableStatement
's
parameter metadata to return correct information for
.getParameterClassName()
.
(Bug#14729)
Added service-provider entry to
META-INF/services/java.sql.Driver
for
JDBC-4.0 support.
(Bug#14729)
Fuller synchronization of Connection
to avoid
deadlocks when using multithreaded frameworks that multithread a
single connection (usually not recommended, but the JDBC spec
allows it anyways), part of fix to Bug#14972).
(Bug#14729)
Moved all SQLException
constructor usage to a
factory in SQLError
(ground-work for JDBC-4.0
SQLState
-based exception classes).
(Bug#14729)
Removed Java5-specific calls to BigDecimal
constructor (when result set value is ''
,
(int)0
was being used as an argument
indirectly via method return value. This signature doesn't exist
prior to Java5.)
(Bug#14729)
Implementation of Statement.cancel()
and
Statement.setQueryTimeout()
. Both require
MySQL-5.0.0 or newer server, require a separate connection to
issue the KILL QUERY
statement, and in the
case of setQueryTimeout()
creates an
additional thread to handle the timeout functionality.
Note: Failures to cancel the statement for
setQueryTimeout()
may manifest themselves as
RuntimeExceptions
rather than failing
silently, as there is currently no way to unblock the thread
that is executing the query being cancelled due to timeout
expiration and have it throw the exception instead.
(Bug#14729)
Return "[VAR]BINARY" for
RSMD.getColumnTypeName()
when that is
actually the type, and it can be distinguished (MySQL-4.1 and
newer).
(Bug#14729)
Attempt detection of the MySQL type BINARY
(it's an alias, so this isn't always reliable), and use the
java.sql.Types.BINARY
type mapping for it.
Added unit tests for XADatasource
, as well as
friendlier exceptions for XA failures compared to the
"stock" XAException
(which has no
messages).
If the connection useTimezone
is set to
true
, then also respect time zone conversions
in escape-processed string literals (for example,
"{ts ...}"
and "{t
...}"
).
Don't allow .setAutoCommit(true)
, or
.commit()
or .rollback()
on an XA-managed connection as per the JDBC specification.
XADataSource
implemented (ported from 3.2
branch which won't be released as a product). Use
com.mysql.jdbc.jdbc2.optional.MysqlXADataSource
as your datasource class name in your application server to
utilize XA transactions in MySQL-5.0.10 and newer.
Moved -bin-g.jar
file into separate
debug
subdirectory to avoid confusion.
Return original column name for
RSMD.getColumnName()
if the column was
aliased, alias name for .getColumnLabel()
(if
aliased), and original table name for
.getTableName()
. Note this only works for
MySQL-4.1 and newer, as older servers don't make this
information available to clients.
Setting useJDBCCompliantTimezoneShift=true
(it's not the default) causes the driver to use GMT for
all
TIMESTAMP
/DATETIME
time
zones, and the current VM time zone for any other type that
refers to time zones. This feature can not be used when
useTimezone=true
to convert between server
and client time zones.
PreparedStatement.setString()
didn't work
correctly when sql_mode
on server contained
NO_BACKSLASH_ESCAPES
and no characters that
needed escaping were present in the string.
Add one level of indirection of internal representation of
CallableStatement
parameter metadata to avoid
class not found issues on JDK-1.3 for
ParameterMetadata
interface (which doesn't
exist prior to JDBC-3.0).
Important change: 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.
To enable server-side prepared statements you must add the following configuration property to your connector string:
useServerPrepStmts=true
The default value of this property is false
(that is, Connector/J does not use server-side prepared
statements).
Bugs fixed:
Specifying US-ASCII
as the character set in a
connection to a MySQL 4.1 or newer server does not map
correctly.
(Bug#24840)
Bugs fixed:
Check and store value for continueBatchOnError property in constructor of Statements, rather than when executing batches, so that Connections closed out from underneath statements don't cause NullPointerExceptions when it's required to check this property. (Bug#22290)
Fixed Bug#18258 - DatabaseMetaData.getTables(), columns() with bad catalog parameter threw exception rather than return empty result set (as required by spec). (Bug#22290)
Driver now sends numeric 1 or 0 for client-prepared statement setBoolean() calls instead of '1' or '0'. (Bug#22290)
Fixed bug where driver would not advance to next host if roundRobinLoadBalance=true and the last host in the list is down. (Bug#22290)
Driver issues truncation on write exception when it shouldn't (due to sending big decimal incorrectly to server with server-side prepared statement). (Bug#22290)
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"). (Bug#22290)
Removed logger autodetection altogether, must now specify logger explicitly if you want to use a logger other than one that logs to STDERR. (Bug#21207)
DDriver throws NPE when tracing prepared statements that have been closed (in asSQL()). (Bug#21207)
ResultSet.getSomeInteger() doesn't work for BIT(>1). (Bug#21062)
Escape of quotes in client-side prepared statements parsing not respected. Patch covers more than bug report, including NO_BACKSLASH_ESCAPES being set, and stacked quote characters forms of escaping (that is, '' or ""). (Bug#20888)
Fixed can't pool server-side prepared statements, exception raised when re-using them. (Bug#20687)
Fixed Updatable result set that contains a BIT column fails when server-side prepared statements are used. (Bug#20485)
Fixed updatable result set throws ClassCastException when there is row data and moveToInsertRow() is called. (Bug#20479)
Fixed ResultSet.getShort() for UNSIGNED TINYINT returns incorrect values when using server-side prepared statements. (Bug#20306)
ReplicationDriver does not always round-robin load balance depending on URL used for slaves list. (Bug#19993)
Fixed calling toString() on ResultSetMetaData for driver-generated (that is, from DatabaseMetaData method calls, or from getGeneratedKeys()) result sets would raise a NullPointerException. (Bug#19993)
Connection fails to localhost when using timeout and IPv6 is configured. (Bug#19726)
ResultSet.getFloatFromString() can't retrieve values near Float.MIN/MAX_VALUE. (Bug#18880)
Fixed memory leak with profileSQL=true. (Bug#16987)
Fixed NullPointerException in MysqlDataSourceFactory due to Reference containing RefAddrs with null content. (Bug#16791)
Bugs fixed:
Fixed PreparedStatement.setObject(int, Object,
int)
doesn't respect scale of BigDecimals.
(Bug#19615)
Fixed ResultSet.wasNull()
returns incorrect
value when extracting native string from server-side prepared
statement generated result set.
(Bug#19282)
Fixed invalid classname returned for
ResultSetMetaData.getColumnClassName()
for
BIGINT type
.
(Bug#19282)
Fixed case where driver wasn't reading server status correctly when fetching server-side prepared statement rows, which in some cases could cause warning counts to be off, or multiple result sets to not be read off the wire. (Bug#19282)
Fixed data truncation and getWarnings()
only
returns last warning in set.
(Bug#18740)
Fixed aliased column names where length of name > 251 are corrupted. (Bug#18554)
Improved performance of retrieving
BigDecimal
, Time
,
Timestamp
and Date
values
from server-side prepared statements by creating fewer
short-lived instances of Strings
when the
native type is not an exact match for the requested type.
(Bug#18496)
Added performance feature, re-writing of batched executes for
Statement.executeBatch()
(for all DML
statements) and
PreparedStatement.executeBatch()
(for INSERTs
with VALUE clauses only). Enable by using
"rewriteBatchedStatements=true" in your JDBC URL.
(Bug#18041)
Fixed issue where server-side prepared statements don't cause truncation exceptions to be thrown when truncation happens. (Bug#18041)
Fixed
CallableStatement.registerOutParameter()
not
working when some parameters pre-populated. Still waiting for
feedback from JDBC experts group to determine what correct
parameter count from getMetaData()
should be,
however.
(Bug#17898)
Fixed calling clearParameters()
on a closed
prepared statement causes NPE.
(Bug#17587)
Map "latin1" on MySQL server to CP1252 for MySQL > 4.1.0. (Bug#17587)
Added additional accessor and mutator methods on ConnectionProperties so that DataSource users can use same naming as regular URL properties. (Bug#17587)
Fixed ResultSet.wasNull()
not always reset
correctly for booleans when done via conversion for server-side
prepared statements.
(Bug#17450)
Fixed Statement.getGeneratedKeys()
throws
NullPointerException
when no query has been
processed.
(Bug#17099)
Fixed updatable result set doesn't return
AUTO_INCREMENT
values for
insertRow()
when multiple column primary keys
are used. (the driver was checking for the existence of
single-column primary keys and an autoincrement value > 0
instead of a straightforward
isAutoIncrement()
check).
(Bug#16841)
DBMD.getColumns()
returns wrong type for
BIT
.
(Bug#15854)
lib-nodist
directory missing from package
breaks out-of-box build.
(Bug#15676)
Fixed issue with ReplicationConnection
incorrectly copying state, doesn't transfer connection context
correctly when transitioning between the same read-only states.
(Bug#15570)
No "dos" character set in MySQL > 4.1.0. (Bug#15544)
INOUT
parameter does not store
IN
value.
(Bug#15464)
PreparedStatement.setObject()
serializes
BigInteger
as object, rather than sending as
numeric value (and is thus not complementary to
.getObject()
on an UNSIGNED
LONG
type).
(Bug#15383)
Fixed issue where driver was unable to initialize character set
mapping tables. Removed reliance on
.properties
files to hold this information,
as it turns out to be too problematic to code around class
loader hierarchies that change depending on how an application
is deployed. Moved information back into the
CharsetMapping
class.
(Bug#14938)
Exception thrown for new decimal type when using updatable result sets. (Bug#14609)
Driver now aware of fix for BIT
type metadata
that went into MySQL-5.0.21 for server not reporting length
consistently .
(Bug#13601)
Added support for Apache Commons logging, use "com.mysql.jdbc.log.CommonsLogger" as the value for the "logger" configuration property. (Bug#13469)
Fixed driver trying to call methods that don't exist on older and newer versions of Log4j. The fix is not trying to auto-detect presence of log4j, too many different incompatible versions out there in the wild to do this reliably.
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. (Bug#13469)
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". (Bug#13469)
ResultSet.getShort()
for UNSIGNED
TINYINT
returned wrong values.
(Bug#11874)
Bugs fixed:
Process escape tokens in
Connection.prepareStatement(...)
. You can
disable this behavior by setting the JDBC URL configuration
property processEscapeCodesForPrepStmts
to
false
.
(Bug#15141)
Usage advisor complains about unreferenced columns, even though they've been referenced. (Bug#15065)
Driver incorrectly closes streams passed as arguments to
PreparedStatements
. Reverts to legacy
behavior by setting the JDBC configuration property
autoClosePStmtStreams
to
true
(also included in the 3-0-Compat
configuration “bundle”).
(Bug#15024)
Deadlock while closing server-side prepared statements from multiple threads sharing one connection. (Bug#14972)
Unable to initialize character set mapping tables (due to J2EE classloader differences). (Bug#14938)
Escape processor replaces quote character in quoted string with string delimiter. (Bug#14909)
DatabaseMetaData.getColumns()
doesn't return
TABLE_NAME
correctly.
(Bug#14815)
storesMixedCaseIdentifiers()
returns
false
(Bug#14562)
storesLowerCaseIdentifiers()
returns
true
(Bug#14562)
storesMixedCaseQuotedIdentifiers()
returns
false
(Bug#14562)
storesMixedCaseQuotedIdentifiers()
returns
true
(Bug#14562)
If lower_case_table_names=0
(on server):
storesLowerCaseIdentifiers()
returns
false
storesLowerCaseQuotedIdentifiers()
returns false
storesMixedCaseIdentifiers()
returns
true
storesMixedCaseQuotedIdentifiers()
returns true
storesUpperCaseIdentifiers()
returns
false
storesUpperCaseQuotedIdentifiers()
returns true
storesUpperCaseIdentifiers()
returns
false
(Bug#14562)
storesUpperCaseQuotedIdentifiers()
returns
true
(Bug#14562)
If lower_case_table_names=1
(on server):
storesLowerCaseIdentifiers()
returns
true
storesLowerCaseQuotedIdentifiers()
returns true
storesMixedCaseIdentifiers()
returns
false
storesMixedCaseQuotedIdentifiers()
returns false
storesUpperCaseIdentifiers()
returns
false
storesUpperCaseQuotedIdentifiers()
returns true
storesLowerCaseQuotedIdentifiers()
returns
true
(Bug#14562)
Fixed DatabaseMetaData.stores*Identifiers()
:
If lower_case_table_names=0
(on server):
storesLowerCaseIdentifiers()
returns
false
storesLowerCaseQuotedIdentifiers()
returns false
storesMixedCaseIdentifiers()
returns
true
storesMixedCaseQuotedIdentifiers()
returns true
storesUpperCaseIdentifiers()
returns
false
storesUpperCaseQuotedIdentifiers()
returns true
If lower_case_table_names=1
(on server):
storesLowerCaseIdentifiers()
returns
true
storesLowerCaseQuotedIdentifiers()
returns true
storesMixedCaseIdentifiers()
returns
false
storesMixedCaseQuotedIdentifiers()
returns false
storesUpperCaseIdentifiers()
returns
false
storesUpperCaseQuotedIdentifiers()
returns true
storesMixedCaseIdentifiers()
returns
true
(Bug#14562)
storesLowerCaseQuotedIdentifiers()
returns
false
(Bug#14562)
Java type conversion may be incorrect for
MEDIUMINT
.
(Bug#14562)
storesLowerCaseIdentifiers()
returns
false
(Bug#14562)
Added configuration property
useGmtMillisForDatetimes
which when set to
true
causes
ResultSet.getDate()
,
.getTimestamp()
to return correct
millis-since GMT when .getTime()
is called on
the return value (currently default is false
for legacy behavior).
(Bug#14562)
Extraneous sleep on autoReconnect
.
(Bug#13775)
Reconnect during middle of executeBatch()
should not occur if autoReconnect
is enabled.
(Bug#13255)
maxQuerySizeToLog
is not respected. Added
logging of bound values for execute()
phase
of server-side prepared statements when
profileSQL=true
as well.
(Bug#13048)
OpenOffice expects
DBMD.supportsIntegrityEnhancementFacility()
to return true
if foreign keys are supported
by the datasource, even though this method also covers support
for check constraints, which MySQL doesn't
have. Setting the configuration property
overrideSupportsIntegrityEnhancementFacility
to true
causes the driver to return
true
for this method.
(Bug#12975)
Added com.mysql.jdbc.testsuite.url.default
system property to set default JDBC url for testsuite (to speed
up bug resolution when I'm working in Eclipse).
(Bug#12975)
logSlowQueries
should give better info.
(Bug#12230)
Don't increase timeout for failover/reconnect. (Bug#6577)
Fixed client-side prepared statement bug with embedded
?
characters inside quoted identifiers (it
was recognized as a placeholder, when it was not).
Don't allow executeBatch()
for
CallableStatements
with registered
OUT
/INOUT
parameters (JDBC
compliance).
Fall back to platform-encoding for
URLDecoder.decode()
when parsing driver URL
properties if the platform doesn't have a two-argument version
of this method.
Bugs fixed:
The configuration property sessionVariables
now allows you to specify variables that start with the
“@
” sign.
(Bug#13453)
URL configuration parameters don't allow
“&
” or
“=
” in their values. The JDBC
driver now parses configuration parameters as if they are
encoded using the application/x-www-form-urlencoded format as
specified by java.net.URLDecoder
(http://java.sun.com/j2se/1.5.0/docs/api/java/net/URLDecoder.html).
If the “%
” character is present
in a configuration property, it must now be represented as
%25
, which is the encoded form of
“%
” when using
application/x-www-form-urlencoded encoding.
(Bug#13453)
Workaround for Bug#13374:
ResultSet.getStatement()
on closed result set
returns NULL
(as per JDBC 4.0 spec, but not
backward-compatible). Set the connection property
retainStatementAfterResultSetClose
to
true
to be able to retrieve a
ResultSet
's statement after the
ResultSet
has been closed via
.getStatement()
(the default is
false
, to be JDBC-compliant and to reduce the
chance that code using JDBC leaks Statement
instances).
(Bug#13277)
ResultSetMetaData
from
Statement.getGeneratedKeys()
caused a
NullPointerException
to be thrown whenever a
method that required a connection reference was called.
(Bug#13277)
Backport of VAR[BINARY|CHAR] [BINARY]
types
detection from 5.0 branch.
(Bug#13277)
Fixed NullPointerException
when converting
catalog
parameter in many
DatabaseMetaDataMethods
to
byte[]
s (for the result set) when the
parameter is null
. (null
isn't technically allowed by the JDBC specification, but we've
historically allowed it).
(Bug#13277)
Backport of Field
class,
ResultSetMetaData.getColumnClassName()
, and
ResultSet.getObject(int)
changes from 5.0
branch to fix behavior surrounding VARCHAR
BINARY
/VARBINARY
and related types.
(Bug#13277)
Read response in MysqlIO.sendFileToServer()
,
even if the local file can't be opened, otherwise next query
issued will fail, because it's reading the response to the empty
LOAD DATA INFILE
packet sent to the server.
(Bug#13277)
When gatherPerfMetrics
is enabled for servers
older than 4.1.0, a NullPointerException
is
thrown from the constructor of ResultSet
if
the query doesn't use any tables.
(Bug#13043)
java.sql.Types.OTHER
returned for
BINARY
and VARBINARY
columns when using
DatabaseMetaData.getColumns()
.
(Bug#12970)
ServerPreparedStatement.getBinding()
now
checks if the statement is closed before attempting to reference
the list of parameter bindings, to avoid throwing a
NullPointerException
.
(Bug#12970)
Tokenizer for =
in URL properties was causing
sessionVariables=....
to be parameterized
incorrectly.
(Bug#12753)
cp1251
incorrectly mapped to
win1251
for servers newer than 4.0.x.
(Bug#12752)
getExportedKeys()
(Bug#12541)
Specifying a catalog works as stated in the API docs. (Bug#12541)
Specifying NULL
means that catalog will not
be used to filter the results (thus all databases will be
searched), unless you've set
nullCatalogMeansCurrent=true
in your JDBC URL
properties.
(Bug#12541)
getIndexInfo()
(Bug#12541)
getProcedures()
(and thus indirectly
getProcedureColumns()
)
(Bug#12541)
getImportedKeys()
(Bug#12541)
Specifying ""
means
“current” catalog, even though this isn't quite
JDBC spec compliant, it's there for legacy users.
(Bug#12541)
getCrossReference()
(Bug#12541)
Added Connection.isMasterConnection()
for
clients to be able to determine if a multi-host master/slave
connection is connected to the first host in the list.
(Bug#12541)
getColumns()
(Bug#12541)
Handling of catalog argument in
DatabaseMetaData.getIndexInfo()
, which also
means changes to the following methods in
DatabaseMetaData
:
getBestRowIdentifier()
getColumns()
getCrossReference()
getExportedKeys()
getImportedKeys()
getIndexInfo()
getPrimaryKeys()
getProcedures()
(and thus indirectly
getProcedureColumns()
)
getTables()
The catalog
argument in all of these methods
now behaves in the following way:
Specifying NULL
means that catalog will
not be used to filter the results (thus all databases will
be searched), unless you've set
nullCatalogMeansCurrent=true
in your JDBC
URL properties.
Specifying ""
means
“current” catalog, even though this isn't quite
JDBC spec compliant, it's there for legacy users.
Specifying a catalog works as stated in the API docs.
Made Connection.clientPrepare()
available
from “wrapped” connections in the
jdbc2.optional
package (connections built
by ConnectionPoolDataSource
instances).
getBestRowIdentifier()
(Bug#12541)
Made Connection.clientPrepare()
available
from “wrapped” connections in the
jdbc2.optional
package (connections built by
ConnectionPoolDataSource
instances).
(Bug#12541)
getTables()
(Bug#12541)
getPrimaryKeys()
(Bug#12541)
Connection.prepareCall()
is database name
case-sensitive (on Windows systems).
(Bug#12417)
explainSlowQueries
hangs with server-side
prepared statements.
(Bug#12229)
Properties shared between master and slave with replication connection. (Bug#12218)
Geometry types not handled with server-side prepared statements. (Bug#12104)
maxPerformance.properties
mis-spells
“elideSetAutoCommits”.
(Bug#11976)
ReplicationConnection
won't switch to slave,
throws “Catalog can't be null” exception.
(Bug#11879)
Pstmt.setObject(...., Types.BOOLEAN)
throws
exception.
(Bug#11798)
Escape tokenizer doesn't respect stacked single quotes for escapes. (Bug#11797)
GEOMETRY
type not recognized when using
server-side prepared statements.
(Bug#11797)
Foreign key information that is quoted is parsed incorrectly
when DatabaseMetaData
methods use that
information.
(Bug#11781)
The sendBlobChunkSize
property is now clamped
to max_allowed_packet
with consideration of
stream buffer size and packet headers to avoid
PacketTooBigExceptions
when
max_allowed_packet
is similar in size to the
default sendBlobChunkSize
which is 1M.
(Bug#11781)
CallableStatement.clearParameters()
now
clears resources associated with
INOUT
/OUTPUT
parameters as
well as INPUT
parameters.
(Bug#11781)
Fixed regression caused by fix for Bug#11552 that caused driver to return incorrect values for unsigned integers when those integers where within the range of the positive signed type. (Bug#11663)
Moved source code to Subversion repository. (Bug#11663)
Incorrect generation of testcase scripts for server-side prepared statements. (Bug#11663)
Fixed statements generated for testcases missing
;
for “plain” statements.
(Bug#11629)
Spurious !
on console when character encoding
is utf8
.
(Bug#11629)
StringUtils.getBytes()
doesn't work when
using multi-byte character encodings and a length in
characters is specified.
(Bug#11614)
DBMD.storesLower/Mixed/UpperIdentifiers()
reports incorrect values for servers deployed on Windows.
(Bug#11575)
Reworked Field
class,
*Buffer
, and MysqlIO
to be
aware of field lengths >
Integer.MAX_VALUE
.
(Bug#11498)
Escape processor didn't honor strings demarcated with double quotes. (Bug#11498)
Updated DBMD.supportsCorrelatedQueries()
to
return true
for versions > 4.1,
supportsGroupByUnrelated()
to return
true
and
getResultSetHoldability()
to return
HOLD_CURSORS_OVER_COMMIT
.
(Bug#11498)
Lifted restriction of changing streaming parameters with
server-side prepared statements. As long as
all
streaming parameters were set before
execution, .clearParameters()
does not have
to be called. (due to limitation of client/server protocol,
prepared statements can not reset
individual stream data on the server side).
(Bug#11498)
ResultSet.moveToCurrentRow()
fails to work
when preceded by a call to
ResultSet.moveToInsertRow()
.
(Bug#11190)
VARBINARY
data corrupted when using
server-side prepared statements and
.setBytes()
.
(Bug#11115)
Statement.getWarnings()
fails with NPE if
statement has been closed.
(Bug#10630)
Only get char[]
from SQL in
PreparedStatement.ParseInfo()
when needed.
(Bug#10630)
Bugs fixed:
Initial implemention of ParameterMetadata
for
PreparedStatement.getParameterMetadata()
.
Only works fully for CallableStatements
, as
current server-side prepared statements return every parameter
as a VARCHAR
type.
Fixed connecting without a database specified raised an
exception in MysqlIO.changeDatabaseTo()
.
Bugs fixed:
Production package doesn't include JBoss integration classes. (Bug#11411)
Removed nonsensical “costly type conversion” warnings when using usage advisor. (Bug#11411)
Fixed PreparedStatement.setClob()
not
accepting null
as a parameter.
(Bug#11360)
Connector/J dumping query into SQLException
twice.
(Bug#11360)
autoReconnect
ping causes exception on
connection startup.
(Bug#11259)
Connection.setCatalog()
is now aware of the
useLocalSessionState
configuration property,
which when set to true
will prevent the
driver from sending USE ...
to the server if
the requested catalog is the same as the current catalog.
(Bug#11115)
3-0-Compat
— Compatibility with
Connector/J 3.0.x functionality
(Bug#11115)
maxPerformance
— maximum performance
without being reckless
(Bug#11115)
solarisMaxPerformance
— maximum
performance for Solaris, avoids syscalls where it can
(Bug#11115)
Added maintainTimeStats
configuration
property (defaults to true
), which tells the
driver whether or not to keep track of the last query time and
the last successful packet sent to the server's time. If set to
false
, removes two syscalls per query.
(Bug#11115)
VARBINARY
data corrupted when using
server-side prepared statements and
ResultSet.getBytes()
.
(Bug#11115)
Added the following configuration bundles, use one or many via
the useConfigs
configuration property:
maxPerformance
— maximum
performance without being reckless
solarisMaxPerformance
— maximum
performance for Solaris, avoids syscalls where it can
3-0-Compat
— Compatibility with
Connector/J 3.0.x functionality
Try to handle OutOfMemoryErrors
more
gracefully. Although not much can be done, they will in most
cases close the connection they happened on so that further
operations don't run into a connection in some unknown state.
When an OOM has happened, any further operations on the
connection will fail with a “Connection closed”
exception that will also list the OOM exception as the reason
for the implicit connection close event.
(Bug#10850)
Setting cachePrepStmts=true
now causes the
Connection
to also cache the check the driver
performs to determine if a prepared statement can be server-side
or not, as well as caches server-side prepared statements for
the lifetime of a connection. As before, the
prepStmtCacheSize
parameter controls the size
of these caches.
(Bug#10850)
Don't send COM_RESET_STMT
for each execution
of a server-side prepared statement if it isn't required.
(Bug#10850)
0-length streams not sent to server when using server-side prepared statements. (Bug#10850)
Driver detects if you're running MySQL-5.0.7 or later, and does
not scan for LIMIT ?[,?]
in statements being
prepared, as the server supports those types of queries now.
(Bug#10850)
Reorganized directory layout. Sources now are in
src
folder. Don't pollute parent directory
when building, now output goes to ./build
,
distribution goes to ./dist
.
(Bug#10496)
Added support/bug hunting feature that generates
.sql
test scripts to
STDERR
when
autoGenerateTestcaseScript
is set to
true
.
(Bug#10496)
SQLException
is thrown when using property
characterSetResults
with
cp932
or eucjpms
.
(Bug#10496)
The datatype returned for TINYINT(1)
columns
when tinyInt1isBit=true
(the default) can be
switched between Types.BOOLEAN
and
Types.BIT
using the new configuration
property transformedBitIsBoolean
, which
defaults to false
. If set to
false
(the default),
DatabaseMetaData.getColumns()
and
ResultSetMetaData.getColumnType()
will return
Types.BOOLEAN
for
TINYINT(1)
columns. If
true
, Types.BOOLEAN
will
be returned instead. Regardless of this configuration property,
if tinyInt1isBit
is enabled, columns with the
type TINYINT(1)
will be returned as
java.lang.Boolean
instances from
ResultSet.getObject(...)
, and
ResultSetMetaData.getColumnClassName()
will
return java.lang.Boolean
.
(Bug#10485)
SQLException
thrown when retrieving
YEAR(2)
with
ResultSet.getString()
. The driver will now
always treat YEAR
types as
java.sql.Dates
and return the correct values
for getString()
. Alternatively, the
yearIsDateType
connection property can be set
to false
and the values will be treated as
SHORT
s.
(Bug#10485)
Driver doesn't support {?=CALL(...)}
for
calling stored functions. This involved adding support for
function retrieval to
DatabaseMetaData.getProcedures()
and
getProcedureColumns()
as well.
(Bug#10310)
Unsigned SMALLINT
treated as signed for
ResultSet.getInt()
, fixed all cases for
UNSIGNED
integer values and server-side
prepared statements, as well as
ResultSet.getObject()
for UNSIGNED
TINYINT
.
(Bug#10156)
Made ServerPreparedStatement.asSql()
work
correctly so auto-explain functionality would work with
server-side prepared statements.
(Bug#10155)
Double quotes not recognized when parsing client-side prepared statements. (Bug#10155)
Made JDBC2-compliant wrappers public in order to allow access to vendor extensions. (Bug#10155)
DatabaseMetaData.supportsMultipleOpenResults()
now returns true
. The driver has supported
this for some time, DBMD just missed that fact.
(Bug#10155)
Cleaned up logging of profiler events, moved code to dump a
profiler event as a string to
com.mysql.jdbc.log.LogUtils
so that third
parties can use it.
(Bug#10155)
Made enableStreamingResults()
visible on
com.mysql.jdbc.jdbc2.optional.StatementWrapper
.
(Bug#10155)
Actually write manifest file to correct place so it ends up in the binary jar file. (Bug#10144)
Added createDatabaseIfNotExist
property
(default is false
), which will cause the
driver to ask the server to create the database specified in the
URL if it doesn't exist. You must have the appropriate
privileges for database creation for this to work.
(Bug#10144)
Memory leak in ServerPreparedStatement
if
serverPrepare()
fails.
(Bug#10144)
com.mysql.jdbc.PreparedStatement.ParseInfo
does unnecessary call to toCharArray()
.
(Bug#9064)
Driver now correctly uses CP932 if available on the server for Windows-31J, CP932 and MS932 java encoding names, otherwise it resorts to SJIS, which is only a close approximation. Currently only MySQL-5.0.3 and newer (and MySQL-4.1.12 or .13, depending on when the character set gets backported) can reliably support any variant of CP932.
Overhaul of character set configuration, everything now lives in a properties file.
Bugs fixed:
Should accept null
for catalog (meaning use
current) in DBMD methods, even though it's not JDBC-compliant
for legacy's sake. Disable by setting connection property
nullCatalogMeansCurrent
to
false
(which will be the default value in C/J
3.2.x).
(Bug#9917)
Fixed driver not returning true
for
-1
when
ResultSet.getBoolean()
was called on result
sets returned from server-side prepared statements.
(Bug#9778)
Added a Manifest.MF
file with
implementation information to the .jar
file.
(Bug#9778)
More tests in Field.isOpaqueBinary()
to
distinguish opaque binary (that is, fields with type
CHAR(n)
and CHARACTER SET
BINARY
) from output of various scalar and aggregate
functions that return strings.
(Bug#9778)
DBMD.getTables()
shouldn't return tables if
views are asked for, even if the database version doesn't
support views.
(Bug#9778)
Should accept null
for name patterns in DBMD
(meaning “%
”), even though it
isn't JDBC compliant, for legacy's sake. Disable by setting
connection property nullNamePatternMatchesAll
to false
(which will be the default value in
C/J 3.2.x).
(Bug#9769)
Then fallback to our STDERR
logging.
(Bug#9704)
The performance metrics feature now gathers information about number of tables referenced in a SELECT. (Bug#9704)
The logging system is now automatically configured. If the value
has been set by the user, via the URL property
logger
or the system property
com.mysql.jdbc.logger
, then use that,
otherwise, autodetect it using the following steps:
Log4j, if it's available,
Then JDK1.4 logging,
Then fallback to our STDERR
logging.
(Bug#9704)
Then JDK1.4 logging, (Bug#9704)
Log4j, if it's available, (Bug#9704)
Statement.getMoreResults()
could throw NPE
when existing result set was .close()
d.
(Bug#9704)
Stored procedures with DECIMAL
parameters
with storage specifications that contained
“,
” in them would fail.
(Bug#9682)
PreparedStatement.setObject(int, Object, int type, int
scale)
now uses scale value for
BigDecimal
instances.
(Bug#9682)
Added support for the c3p0 connection pool's
(http://c3p0.sf.net/) validation/connection
checker interface which uses the lightweight
COM_PING
call to the server if available. To
use it, configure your c3p0 connection pool's
connectionTesterClassName
property to use
com.mysql.jdbc.integration.c3p0.MysqlConnectionTester
.
(Bug#9320)
PreparedStatement.getMetaData()
inserts blank
row in database under certain conditions when not using
server-side prepared statements.
(Bug#9320)
Better detection of LIMIT
inside/outside of
quoted strings so that the driver can more correctly determine
whether a prepared statement can be prepared on the server or
not.
(Bug#9320)
Connection.canHandleAsPreparedStatement()
now
makes “best effort” to distinguish
LIMIT
clauses with placeholders in them from
ones without in order to have fewer false positives when
generating work-arounds for statements the server cannot
currently handle as server-side prepared statements.
(Bug#9320)
Fixed build.xml
to not compile
log4j
logging if log4j
not
available.
(Bug#9320)
Added finalizers to ResultSet
and
Statement
implementations to be JDBC
spec-compliant, which requires that if not explicitly closed,
these resources should be closed upon garbage collection.
(Bug#9319)
Stored procedures with same name in different databases confuse the driver when it tries to determine parameter counts/types. (Bug#9319)
A continuation of Bug#8868, where functions used in queries
that should return non-string types when resolved by temporary
tables suddenly become opaque binary strings (work-around for
server limitation). Also fixed fields with type of
CHAR(n) CHARACTER SET BINARY
to return
correct/matching classes for
RSMD.getColumnClassName()
and
ResultSet.getObject()
.
(Bug#9236)
Cannot use UTF-8
for characterSetResults
configuration property.
(Bug#9206)
PreparedStatement.addBatch()
doesn't work
with server-side prepared statements and streaming
BINARY
data.
(Bug#9040)
ServerPreparedStatements
now correctly
“stream”
BLOB
/CLOB
data to the
server. You can configure the threshold chunk size using the
JDBC URL property blobSendChunkSize
(the
default is 1MB).
(Bug#8868)
DATE_FORMAT()
queries returned
as BLOB
s from getObject()
.
(Bug#8868)
Server-side session variables can be preset at connection time
by passing them as a comma-delimited list for the connection
property sessionVariables
.
(Bug#8868)
BlobFromLocator
now uses correct identifier
quoting when generating prepared statements.
(Bug#8868)
Fixed regression in ping()
for users using
autoReconnect=true
.
(Bug#8868)
Check for empty strings (''
) when converting
CHAR
/VARCHAR
column data
to numbers, throw exception if
emptyStringsConvertToZero
configuration
property is set to false
(for
backward-compatibility with 3.0, it is now set to
true
by default, but will most likely default
to false
in 3.2).
(Bug#8803)
DATA_TYPE
column from
DBMD.getBestRowIdentifier()
causes
ArrayIndexOutOfBoundsException
when accessed
(and in fact, didn't return any value).
(Bug#8803)
DBMD.supportsMixedCase*Identifiers()
returns
wrong value on servers running on case-sensitive filesystems.
(Bug#8800)
DBMD.supportsResultSetConcurrency()
not
returning true
for forward-only/read-only
result sets (we obviously support this).
(Bug#8792)
Fixed ResultSet.getTime()
on a
NULL
value for server-side prepared
statements throws NPE.
Made Connection.ping()
a public method.
Added support for new precision-math DECIMAL
type in MySQL 5.0.3 and up.
Fixed DatabaseMetaData.getTables()
returning
views when they were not asked for as one of the requested table
types.
Bugs fixed:
PreparedStatements
not creating streaming
result sets.
(Bug#8487)
Don't pass NULL
to
String.valueOf()
in
ResultSet.getNativeConvertToString()
, as it
stringifies it (that is, returns null
), which
is not correct for the method in question.
(Bug#8487)
Fixed NPE in ResultSet.realClose()
when using
usage advisor and result set was already closed.
(Bug#8428)
ResultSet.getString()
doesn't maintain format
stored on server, bug fix only enabled when
noDatetimeStringSync
property is set to
true
(the default is
false
).
(Bug#8428)
Added support for BIT
type in MySQL-5.0.3.
The driver will treat BIT(1-8)
as the JDBC
standard BIT
type (which maps to
java.lang.Boolean
), as the server does not
currently send enough information to determine the size of a
bitfield when < 9 bits are declared.
BIT(>9)
will be treated as
VARBINARY
, and will return
byte[]
when getObject()
is
called.
(Bug#8424)
Added useLocalSessionState
configuration
property, when set to true
the JDBC driver
trusts that the application is well-behaved and only sets
autocommit and transaction isolation levels using the methods
provided on java.sql.Connection
, and
therefore can manipulate these values in many cases without
incurring round-trips to the database server.
(Bug#8424)
Added enableStreamingResults()
to
Statement
for connection pool implementations
that check Statement.setFetchSize()
for
specification-compliant values. Call
Statement.setFetchSize(>=0)
to disable the
streaming results for that statement.
(Bug#8424)
ResultSet.getBigDecimal()
throws exception
when rounding would need to occur to set scale. The driver now
chooses a rounding mode of “half up” if
non-rounding BigDecimal.setScale()
fails.
(Bug#8424)
Fixed synchronization issue with
ServerPreparedStatement.serverPrepare()
that
could cause deadlocks/crashes if connection was shared between
threads.
(Bug#8096)
Emulated locators corrupt binary data when using server-side prepared statements. (Bug#8096)
Infinite recursion when “falling back” to master in failover configuration. (Bug#7952)
Disable multi-statements (if enabled) for MySQL-4.1 versions prior to version 4.1.10 if the query cache is enabled, as the server returns wrong results in this configuration. (Bug#7952)
Removed dontUnpackBinaryResults
functionality, the driver now always stores results from
server-side prepared statements as is from the server and
unpacks them on demand.
(Bug#7952)
Fixed duplicated code in
configureClientCharset()
that prevented
useOldUTF8Behavior=true
from working
properly.
(Bug#7952)
Added holdResultsOpenOverStatementClose
property (default is false
), that keeps
result sets open over statement.close() or new execution on same
statement (suggested by Kevin Burton).
(Bug#7715)
Detect new sql_mode
variable in string form
(it used to be integer) and adjust quoting method for strings
appropriately.
(Bug#7715)
Timestamps converted incorrectly to strings with server-side prepared statements and updatable result sets. (Bug#7715)
Timestamp key column data needed _binary
stripped for UpdatableResultSet.refreshRow()
.
(Bug#7686)
Choose correct “direction” to apply time
adjustments when both client and server are in GMT time zone
when using ResultSet.get(..., cal)
and
PreparedStatement.set(...., cal)
.
(Bug#4718)
Remove _binary
introducer from parameters
used as in/out parameters in
CallableStatement
.
(Bug#4718)
Always return byte[]
s for output parameters
registered as *BINARY
.
(Bug#4718)
By default, the driver now scans SQL you are preparing via all
variants of Connection.prepareStatement()
to
determine if it is a supported type of statement to prepare on
the server side, and if it is not supported by the server, it
instead prepares it as a client-side emulated prepared
statement. You can disable this by passing
emulateUnsupportedPstmts=false
in your JDBC
URL.
(Bug#4718)
Added dontTrackOpenResources
option (default
is false
, to be JDBC compliant), which helps
with memory use for non-well-behaved apps (that is, applications
that don't close Statement
objects when they
should).
(Bug#4718)
Send correct value for “boolean”
true
to server for
PreparedStatement.setObject(n, "true",
Types.BIT)
.
(Bug#4718)
Fixed bug with Connection not caching statements from
prepareStatement()
when the statement wasn't
a server-side prepared statement.
(Bug#4718)
Bugs fixed:
DBMD.getProcedures()
doesn't respect catalog
parameter.
(Bug#7026)
Fixed hang on SocketInputStream.read()
with
Statement.setMaxRows()
and multiple result
sets when driver has to truncate result set directly, rather
than tacking a LIMIT
on the end of it.
n
Bugs fixed:
Use 1MB packet for sending file for LOAD DATA LOCAL
INFILE
if that is <
max_allowed_packet
on server.
(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).
(Bug#6537)
Use
DatabaseMetaData.getIdentifierQuoteString()
when building DBMD queries.
(Bug#6537)
Use our own implementation of buffered input streams to get
around blocking behavior of
java.io.BufferedInputStream
. Disable this
with useReadAheadInput=false
.
(Bug#6399)
Make auto-deserialization of
java.lang.Objects
stored in
BLOB
columns configurable via
autoDeserialize
property (defaults to
false
).
(Bug#6399)
ResultSetMetaData.getColumnDisplaySize()
returns incorrect values for multi-byte charsets.
(Bug#6399)
Re-work Field.isOpaqueBinary()
to detect
CHAR(
to support fixed-length binary fields for
n
) CHARACTER SET
BINARYResultSet.getObject()
.
(Bug#6399)
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()
.
(Bug#6348)
Removed unwanted 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.
(Bug#6225)
ServerSidePreparedStatement
allocating
short-lived objects unnecessarily.
(Bug#6225)
Use null-safe-equals for key comparisons in updatable result sets. (Bug#6225)
Fixed too-early creation of StringBuffer
in
EscapeProcessor.escapeSQL()
, also return
String
when escaping not needed (to avoid
unnecessary object allocations). Found while profiling for Bug#6359.
(Bug#6225)
UNSIGNED BIGINT
unpacked incorrectly from
server-side prepared statement result sets.
(Bug#5729)
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.
(Bug#5706)
Don't throw exceptions for
Connection.releaseSavepoint()
.
(Bug#5706)
Inefficient detection of pre-existing string instances in
ResultSet.getNativeString()
.
(Bug#5706)
Use a per-session Calendar
instance by
default when decoding dates from
ServerPreparedStatements
(set to old, less
performant behavior by setting property
dynamicCalendars=true
).
(Bug#5706)
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()”. (Bug#5235)
Handle case when string representation of timestamp contains
trailing “.
” with no numbers
following it.
(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.
(Bug#5235)
Fix comparisons made between string constants and dynamic
strings that are converted with either
toUpperCase()
or
toLowerCase()
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.
Bugs fixed:
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
.
(Bug#5032)
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'
.
(Bug#5032)
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).
(Bug#5032)
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
.
(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 obscured test in
getObject()
for “pseudo” bit
type).
(Bug#5032)
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.
(Bug#5032)
ServerPreparedStatements
dealing with return
of DECIMAL
type don't work.
(Bug#5012)
Track packet sequence numbers if
enablePacketDebug=true
, and throw an
exception if packets received out-of-order.
(Bug#4689)
ResultSet.wasNull()
does not work for
primatives if a previous null
was returned.
(Bug#4689)
Optimized integer number parsing, enable “old”
slower integer parsing using JDK classes via
useFastIntParsing=false
property.
(Bug#4642)
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.
(Bug#4642)
ServerPreparedStatement.execute*()
sometimes
threw ArrayIndexOutOfBoundsException
when
unpacking field metadata.
(Bug#4642)
Connector/J 3.1.3 beta does not handle integers correctly
(caused by changes to support unsigned reads in
Buffer.readInt()
->
Buffer.readShort()
).
(Bug#4510)
Added support in DatabaseMetaData.getTables()
and getTableTypes()
for views, which are now
available in MySQL server 5.0.x.
(Bug#4510)
ResultSet.getObject()
returns wrong type for
strings when using prepared statements.
(Bug#4482)
Calling MysqlPooledConnection.close()
twice
(even though an application error), caused NPE. Fixed.
(Bug#4482)
Bugs fixed:
Support new time zone variables in MySQL-4.1.3 when
useTimezone=true
.
(Bug#4311)
Error in retrieval of mediumint
column with
prepared statements and binary protocol.
(Bug#4311)
Support for unsigned numerics as return types from prepared
statements. This also causes a change in
ResultSet.getObject()
for the bigint
unsigned
type, which used to return
BigDecimal
instances, it now returns
instances of java.lang.BigInteger
.
(Bug#4311)
Externalized more messages (on-going effort). (Bug#4119)
Null bitmask sent for server-side prepared statements was incorrect. (Bug#4119)
Added constants for MySQL error numbers (publicly accessible,
see com.mysql.jdbc.MysqlErrorNumbers
), and
the ability to generate the mappings of vendor error codes to
SQLStates that the driver uses (for documentation purposes).
(Bug#4119)
Added packet debuging code (see the
enablePacketDebug
property documentation).
(Bug#4119)
Use SQL Standard SQL states by default, unless
useSqlStateCodes
property is set to
false
.
(Bug#4119)
Mangle output parameter names for
CallableStatements
so they will not clash
with user variable names.
Added support for INOUT
parameters in
CallableStatements
.
Bugs fixed:
Don't enable server-side prepared statements for server version 5.0.0 or 5.0.1, as they aren't compatible with the '4.1.2+' style that the driver uses (the driver expects information to come back that isn't there, so it hangs). (Bug#3804)
getWarnings()
returns
SQLWarning
instead of
DataTruncation
.
(Bug#3804)
getProcedureColumns()
doesn't work with
wildcards for procedure name.
(Bug#3540)
getProcedures()
does not return any
procedures in result set.
(Bug#3539)
Fixed DatabaseMetaData.getProcedures()
when
run on MySQL-5.0.0 (output of SHOW PROCEDURE
STATUS
changed between 5.0.0 and 5.0.1.
(Bug#3520)
Added connectionCollation
property to cause
driver to issue set collation_connection=...
query on connection init if default collation for given charset
is not appropriate.
(Bug#3520)
DBMD.getSQLStateType()
returns incorrect
value.
(Bug#3520)
Correctly map output parameters to position given in
prepareCall()
versus. order implied during
registerOutParameter()
.
(Bug#3146)
Cleaned up detection of server properties. (Bug#3146)
Correctly detect initial character set for servers >= 4.1.0. (Bug#3146)
Support placeholder for parameter metadata for server >= 4.1.2. (Bug#3146)
Added gatherPerformanceMetrics
property,
along with properties to control when/where this info gets
logged (see docs for more info).
Fixed case when no parameters could cause a
NullPointerException
in
CallableStatement.setOutputParameters()
.
Enabled callable statement caching via
cacheCallableStmts
property.
Fixed sending of split packets for large queries, enabled nio ability to send large packets as well.
Added .toString()
functionality to
ServerPreparedStatement
, which should help if
you're trying to debug a query that is a prepared statement (it
shows SQL as the server would process).
Added logSlowQueries
property, along with
slowQueriesThresholdMillis
property to
control when a query should be considered “slow.”
Removed wrapping of exceptions in
MysqlIO.changeUser()
.
Fixed stored procedure parameter parsing info when size was
specified for a parameter (for example,
char()
, varchar()
).
ServerPreparedStatements
weren't actually
de-allocating server-side resources when
.close()
was called.
Fixed case when no output parameters specified for a stored procedure caused a bogus query to be issued to retrieve out parameters, leading to a syntax error from the server.
Bugs fixed:
Use DocBook version of docs for shipped versions of drivers. (Bug#2671)
NULL
fields were not being encoded correctly
in all cases in server-side prepared statements.
(Bug#2671)
Fixed rare buffer underflow when writing numbers into buffers for sending prepared statement execution requests. (Bug#2671)
Fixed ConnectionProperties
that weren't
properly exposed via accessors, cleaned up
ConnectionProperties
code.
(Bug#2623)
Class-cast exception when using scrolling result sets and server-side prepared statements. (Bug#2623)
Merged unbuffered input code from 3.0. (Bug#2623)
Enabled streaming of result sets from server-side prepared statements. (Bug#2606)
Server-side prepared statements were not returning datatype
YEAR
correctly.
(Bug#2606)
Fixed charset conversion issue in
getTables()
.
(Bug#2502)
Implemented multiple result sets returned from a statement or stored procedure. (Bug#2502)
Implemented Connection.prepareCall()
, and
DatabaseMetaData
.
getProcedures()
and
getProcedureColumns()
.
(Bug#2359)
Merged prepared statement caching, and
.getMetaData()
support from 3.0 branch.
(Bug#2359)
Fixed off-by-1900 error in some cases for years in
TimeUtil.fastDate
/TimeCreate()
when unpacking results from server-side prepared statements.
(Bug#2359)
Reset long binary
parameters in
ServerPreparedStatement
when
clearParameters()
is called, by sending
COM_RESET_STMT
to the server.
(Bug#2359)
NULL
values for numeric types in binary
encoded result sets causing
NullPointerExceptions
.
(Bug#2359)
Display where/why a connection was implicitly closed (to aid debugging). (Bug#1673)
DatabaseMetaData.getColumns()
is not
returning correct column ordinal info for
non-'%'
column name patterns.
(Bug#1673)
Fixed NullPointerException
in
ServerPreparedStatement.setTimestamp()
, as
well as year and month descrepencies in
ServerPreparedStatement.setTimestamp()
,
setDate()
.
(Bug#1673)
Added ability to have multiple database/JVM targets for
compliance and regression/unit tests in
build.xml
.
(Bug#1673)
Fixed sending of queries larger than 16M. (Bug#1673)
Merged fix of datatype mapping from MySQL type
FLOAT
to
java.sql.Types.REAL
from 3.0 branch.
(Bug#1673)
Fixed NPE and year/month bad conversions when accessing some
datetime functionality in
ServerPreparedStatements
and their resultant
result sets.
(Bug#1673)
Added named and indexed input/output parameter support to
CallableStatement
. MySQL-5.0.x or newer.
(Bug#1673)
CommunicationsException
implemented, that
tries to determine why communications was lost with a server,
and displays possible reasons when
.getMessage()
is called.
(Bug#1673)
Detect collation of column for
RSMD.isCaseSensitive()
.
(Bug#1673)
Optimized Buffer.readLenByteArray()
to return
shared empty byte array when length is 0.
Fix support for table aliases when checking for all primary keys
in UpdatableResultSet
.
Unpack “unknown” data types from server prepared
statements as Strings
.
Implemented Statement.getWarnings()
for
MySQL-4.1 and newer (using SHOW WARNINGS
).
Ensure that warnings are cleared before executing queries on prepared statements, as-per JDBC spec (now that we support warnings).
Correctly initialize datasource properties from JNDI Refs, including explicitly specified URLs.
Implemented long data (Blobs, Clobs, InputStreams, Readers) for server prepared statements.
Deal with 0-length tokens in EscapeProcessor
(caused by callable statement escape syntax).
DatabaseMetaData
now reports
supportsStoredProcedures()
for MySQL versions
>= 5.0.0
Support for
mysql_change_user()
. See the
changeUser()
method in
com.mysql.jdbc.Connection
.
Removed useFastDates
connection property.
Support for NIO. Use useNIO=true
on platforms
that support NIO.
Check for closed connection on delete/update/insert row
operations in UpdatableResultSet
.
Support for transaction savepoints (MySQL >= 4.0.14 or 4.1.1).
Support “old” profileSql
capitalization in ConnectionProperties
. This
property is deprecated, you should use
profileSQL
if possible.
Fixed character encoding issues when converting bytes to ASCII when MySQL doesn't provide the character set, and the JVM is set to a multi-byte encoding (usually affecting retrieval of numeric values).
Centralized setting of result set type and concurrency.
Fixed bug with UpdatableResultSets
not using
client-side prepared statements.
Default result set type changed to
TYPE_FORWARD_ONLY
(JDBC compliance).
Fixed IllegalAccessError
to
Calendar.getTimeInMillis()
in
DateTimeValue
(for JDK < 1.4).
Allow contents of PreparedStatement.setBlob()
to be retained between calls to .execute*()
.
Fixed stack overflow in
Connection.prepareCall()
(bad merge).
Refactored how connection properties are set and exposed as
DriverPropertyInfo
as well as
Connection
and DataSource
properties.
Reduced number of methods called in average query to be more efficient.
Prepared Statements
will be re-prepared on
auto-reconnect. Any errors encountered are postponed until first
attempt to re-execute the re-prepared statement.
Bugs fixed:
Added useServerPrepStmts
property (default
false
). The driver will use server-side
prepared statements when the server version supports them (4.1
and newer) when this property is set to true
.
It is currently set to false
by default until
all bind/fetch functionality has been implemented. Currently
only DML prepared statements are implemented for 4.1 server-side
prepared statements.
Added requireSSL
property.
Track open Statements
, close all when
Connection.close()
is called (JDBC
compliance).
Bugs fixed:
Workaround for server Bug#9098: Default values of
CURRENT_*
for DATE
,
TIME
, DATETIME
, and
TIMESTAMP
columns can't be distinguished from
string
values, so
UpdatableResultSet.moveToInsertRow()
generates bad SQL for inserting default values.
(Bug#8812)
NON_UNIQUE
column from
DBMD.getIndexInfo()
returned inverted value.
(Bug#8812)
EUCKR
charset is sent as SET NAMES
euc_kr
which MySQL-4.1 and newer doesn't understand.
(Bug#8629)
Added support for the EUC_JP_Solaris
character encoding, which maps to a MySQL encoding of
eucjpms
(backported from 3.1 branch). This
only works on servers that support eucjpms
,
namely 5.0.3 or later.
(Bug#8629)
Use hex escapes for
PreparedStatement.setBytes()
for double-byte
charsets including “aliases”
Windows-31J
, CP934
,
MS932
.
(Bug#8629)
DatabaseMetaData.supportsSelectForUpdate()
returns correct value based on server version.
(Bug#8629)
Which requires hex escaping of binary data when using multi-byte charsets with prepared statements. (Bug#8064)
Fixed duplicated code in
configureClientCharset()
that prevented
useOldUTF8Behavior=true
from working
properly.
(Bug#7952)
Backported SQLState codes mapping from Connector/J 3.1, enable
with useSqlStateCodes=true
as a connection
property, it defaults to false
in this
release, so that we don't break legacy applications (it defaults
to true
starting with Connector/J 3.1).
(Bug#7686)
Timestamp key column data needed _binary
stripped for UpdatableResultSet.refreshRow()
.
(Bug#7686)
MS932
, SHIFT_JIS
, and
Windows_31J
not recognized as aliases for
sjis
.
(Bug#7607)
Handle streaming result sets with more than 2 billion rows properly by fixing wraparound of row number counter. (Bug#7601)
PreparedStatement.fixDecimalExponent()
adding
extra +
, making number unparseable by MySQL
server.
(Bug#7601)
Escape sequence {fn convert(..., type)} now supports ODBC-style
types that are prepended by SQL_
.
(Bug#7601)
Statements created from a pooled connection were returning
physical connection instead of logical connection when
getConnection()
was called.
(Bug#7316)
Support new protocol type MYSQL_TYPE_VARCHAR
.
(Bug#7081)
Added useOldUTF8Behavior
' configuration
property, which causes JDBC driver to act like it did with
MySQL-4.0.x and earlier when the character encoding is
utf-8
when connected to MySQL-4.1 or newer.
(Bug#7081)
DatabaseMetaData.getIndexInfo()
ignored
unique
parameter.
(Bug#7081)
PreparedStatement.fixDecimalExponent()
adding
extra +
, making number unparseable by MySQL
server.
(Bug#7061)
PreparedStatements
don't encode Big5 (and
other multi-byte) character sets correctly in static SQL
strings.
(Bug#7033)
Connections starting up failed-over (due to down master) never retry master. (Bug#6966)
Timestamp
/Time
conversion
goes in the wrong “direction” when
useTimeZone=true
and server time zone differs
from client time zone.
(Bug#5874)
Bugs fixed:
Made TINYINT(1)
->
BIT
/Boolean
conversion
configurable via tinyInt1isBit
property
(default true
to be JDBC compliant out of the
box).
(Bug#5664)
Off-by-one bug in
Buffer.readString(
.
(Bug#5664)string
)
ResultSet.updateByte()
when on insert row
throws ArrayOutOfBoundsException
.
(Bug#5664)
Fixed regression where useUnbufferedInput
was
defaulting to false
.
(Bug#5664)
ResultSet.getTimestamp()
on a column with
TIME
in it fails.
(Bug#5664)
Fixed DatabaseMetaData.getTypes()
returning
incorrect (this is, non-negative) scale for the
NUMERIC
type.
(Bug#5664)
Only set character_set_results
during
connection establishment if server version >= 4.1.1.
(Bug#5664)
Fixed ResultSetMetaData.isReadOnly()
to
detect non-writable columns when connected to MySQL-4.1 or
newer, based on existence of “original” table and
column names.
Re-issue character set configuration commands when re-using
pooled connections and/or
Connection.changeUser()
when connected to
MySQL-4.1 or newer.
Bugs fixed:
ResultSet.getMetaData()
should not return
incorrectly initialized metadata if the result set has been
closed, but should instead throw an
SQLException
. Also fixed for
getRow()
and getWarnings()
and traversal methods by calling
checkClosed()
before operating on
instance-level fields that are nullified during
.close()
.
(Bug#5069)
Use _binary
introducer for
PreparedStatement.setBytes()
and
set*Stream()
when connected to MySQL-4.1.x or
newer to avoid misinterpretation during character conversion.
(Bug#5069)
Parse new time zone variables from 4.1.x servers. (Bug#5069)
ResultSet
should release
Field[]
instance in
.close()
.
(Bug#5022)
RSMD.getPrecision()
returning 0 for
non-numeric types (should return max length in chars for
non-binary types, max length in bytes for binary types). This
fix also fixes mapping of
RSMD.getColumnType()
and
RSMD.getColumnTypeName()
for the
BLOB
types based on the length sent from the
server (the server doesn't distinguish between
TINYBLOB
, BLOB
,
MEDIUMBLOB
or LONGBLOB
at
the network protocol level).
(Bug#4880)
“Production” is now “GA” (General Availability) in naming scheme of distributions. (Bug#4860, Bug#4138)
DBMD.getColumns()
returns incorrect JDBC type
for unsigned columns. This affects type mappings for all numeric
types in the RSMD.getColumnType()
and
RSMD.getColumnTypeNames()
methods as well, to
ensure that “like” types from
DBMD.getColumns()
match up with what
RSMD.getColumnType()
and
getColumnTypeNames()
return.
(Bug#4860, Bug#4138)
Calling .close()
twice on a
PooledConnection
causes NPE.
(Bug#4808)
DOUBLE
mapped twice in
DBMD.getTypeInfo()
.
(Bug#4742)
Added FLOSS license exemption. (Bug#4742)
Removed redundant calls to checkRowPos()
in
ResultSet
.
(Bug#4334)
Failover for autoReconnect
not using port
numbers for any hosts, and not retrying all hosts.
This required a change to the SocketFactory
connect()
method signature, which is now
public Socket connect(String host, int portNumber,
Properties props)
; therefore, any third-party socket
factories will have to be changed to support this signature.
(Bug#4334)
Logical connections created by
MysqlConnectionPoolDataSource
will now issue
a rollback()
when they are closed and sent
back to the pool. If your application server/connection pool
already does this for you, you can set the
rollbackOnPooledClose
property to
false
to avoid the overhead of an extra
rollback()
.
(Bug#4334)
StringUtils.escapeEasternUnicodeByteStream
was still broken for GBK.
(Bug#4010)
Bugs fixed:
Bugs fixed:
Inconsistent reporting of data type. The server still doesn't return all types for *BLOBs *TEXT correctly, so the driver won't return those correctly. (Bug#3570)
UpdatableResultSet
not picking up default
values for moveToInsertRow()
.
(Bug#3557)
Not specifying database in URL caused
MalformedURL
exception.
(Bug#3554)
Auto-convert MySQL encoding names to Java encoding names if used
for characterEncoding
property.
(Bug#3554)
Use junit.textui.TestRunner
for all unit
tests (to allow them to be run from the command line outside of
Ant or Eclipse).
(Bug#3554)
Added encoding names that are recognized on some JVMs to fix case where they were reverse-mapped to MySQL encoding names incorrectly. (Bug#3554)
Made StringRegressionTest
4.1-unicode aware.
(Bug#3520)
Fixed regression in
PreparedStatement.setString()
and eastern
character encodings.
(Bug#3520)
DBMD.getSQLStateType()
returns incorrect
value.
(Bug#3520)
Renamed StringUtils.escapeSJISByteStream()
to
more appropriate
escapeEasternUnicodeByteStream()
.
(Bug#3511)
StringUtils.escapeSJISByteStream()
not
covering all eastern double-byte charsets correctly.
(Bug#3511)
Return creating statement for ResultSets
created by getGeneratedKeys()
.
(Bug#2957)
Use SET character_set_results
during
initialization to allow any charset to be returned to the driver
for result sets.
(Bug#2670)
Don't truncate BLOB
or
CLOB
values when using
setBytes()
and/or
setBinary/CharacterStream()
. .
(Bug#2670)
Dynamically configure character set mappings for field-level
character sets on MySQL-4.1.0 and newer using SHOW
COLLATION
when connecting.
(Bug#2670)
Map binary
character set to
US-ASCII
to support
DATETIME
charset recognition for servers
>= 4.1.2.
(Bug#2670)
Use charsetnr
returned during connect to
encode queries before issuing SET NAMES
on
MySQL >= 4.1.0.
(Bug#2670)
Add helper methods to ResultSetMetaData
(getColumnCharacterEncoding()
and
getColumnCharacterSet()
) to allow end-users
to see what charset the driver thinks it should be using for the
column.
(Bug#2670)
Only set character_set_results
for MySQL
>= 4.1.0.
(Bug#2670)
Allow url
parameter for
MysqlDataSource
and
MysqlConnectionPool
DataSource
so that passing of other
properties is possible from inside appservers.
Don't escape SJIS/GBK/BIG5 when using MySQL-4.1 or newer.
Backport documentation tooling from 3.1 branch.
Added failOverReadOnly
property, to allow
end-user to configure state of connection (read-only/writable)
when failed over.
Allow java.util.Date
to be sent in as
parameter to PreparedStatement.setObject()
,
converting it to a Timestamp
to maintain full
precision. .
(Bug#103)
Add unsigned attribute to
DatabaseMetaData.getColumns()
output in the
TYPE_NAME
column.
Map duplicate key and foreign key errors to SQLState of
23000
.
Backported “change user” and “reset server
state” functionality from 3.1 branch, to allow clients of
MysqlConnectionPoolDataSource
to reset server
state on getConnection()
on a pooled
connection.
Bugs fixed:
Return java.lang.Double
for
FLOAT
type from
ResultSetMetaData.getColumnClassName()
.
(Bug#2855)
Return [B
instead of
java.lang.Object
for
BINARY
, VARBINARY
and
LONGVARBINARY
types from
ResultSetMetaData.getColumnClassName()
(JDBC
compliance).
(Bug#2855)
Issue connection events on all instances created from a
ConnectionPoolDataSource
.
(Bug#2855)
Return java.lang.Integer
for
TINYINT
and SMALLINT
types
from ResultSetMetaData.getColumnClassName()
.
(Bug#2852)
Added useUnbufferedInput
parameter, and now
use it by default (due to JVM issue
http://developer.java.sun.com/developer/bugParade/bugs/4401235.html)
(Bug#2578)
Fixed failover always going to last host in list. (Bug#2578)
Detect on
/off
or
1
, 2
, 3
form of lower_case_table_names
value on
server.
(Bug#2578)
AutoReconnect
time was growing faster than
exponentially.
(Bug#2447)
Trigger a SET NAMES utf8
when encoding is
forced to utf8
or
utf-8
via the
characterEncoding
property. Previously, only
the Java-style encoding name of utf-8
would
trigger this.
Bugs fixed:
Enable caching of the parsing stage of prepared statements via
the cachePrepStmts
,
prepStmtCacheSize
, and
prepStmtCacheSqlLimit
properties (disabled by
default).
(Bug#2006)
Fixed security exception when used in Applets (applets can't
read the system property file.encoding
which
is needed for LOAD DATA LOCAL INFILE
).
(Bug#2006)
Speed up parsing of PreparedStatements
, try
to use one-pass whenever possible.
(Bug#2006)
Fixed exception Unknown character set
'danish'
on connect with JDK-1.4.0
(Bug#2006)
Fixed mappings in SQLError to report deadlocks with SQLStates of
41000
.
(Bug#2006)
Removed static synchronization bottleneck from instance factory
method of SingleByteCharsetConverter
.
(Bug#2006)
Removed static synchronization bottleneck from
PreparedStatement.setTimestamp()
.
(Bug#2006)
ResultSet.findColumn()
should use first
matching column name when there are duplicate column names in
SELECT
query (JDBC-compliance).
(Bug#2006)
maxRows
property would affect internal
statements, so check it for all statement creation internal to
the driver, and set to 0 when it is not.
(Bug#2006)
Use constants for SQLStates. (Bug#2006)
Map charset ko18_ru
to
ko18r
when connected to MySQL-4.1.0 or newer.
(Bug#2006)
Ensure that Buffer.writeString()
saves room
for the \0
.
(Bug#2006)
ArrayIndexOutOfBounds
when parameter number
== number of parameters + 1.
(Bug#1958)
Connection property maxRows
not honored.
(Bug#1933)
Statements being created too many times in
DBMD.extractForeignKeyFromCreateTable()
.
(Bug#1925)
Support escape sequence {fn convert ... }. (Bug#1914)
Implement ResultSet.updateClob()
.
(Bug#1913)
Autoreconnect code didn't set catalog upon reconnect if it had been changed. (Bug#1913)
ResultSet.getObject()
on
TINYINT
and SMALLINT
columns should return Java type Integer
.
(Bug#1913)
Added more descriptive error message Server
Configuration Denies Access to DataSource
, as well as
retrieval of message from server.
(Bug#1913)
ResultSetMetaData.isCaseSensitive()
returned
wrong value for
CHAR
/VARCHAR
columns.
(Bug#1913)
Added alwaysClearStream
connection property,
which causes the driver to always empty any remaining data on
the input stream before each query.
(Bug#1913)
DatabaseMetaData.getSystemFunction()
returning bad function VResultsSion
.
(Bug#1775)
Foreign Keys column sequence is not consistent in
DatabaseMetaData.getImported/Exported/CrossReference()
.
(Bug#1731)
Fix for ArrayIndexOutOfBounds
exception when
using Statement.setMaxRows()
.
(Bug#1695)
Subsequent call to ResultSet.updateFoo()
causes NPE if result set is not updatable.
(Bug#1630)
Fix for 4.1.1-style authentication with no password. (Bug#1630)
Cross-database updatable result sets are not checked for updatability correctly. (Bug#1592)
DatabaseMetaData.getColumns()
should return
Types.LONGVARCHAR
for MySQL
LONGTEXT
type.
(Bug#1592)
Fixed regression of
Statement.getGeneratedKeys()
and
REPLACE
statements.
(Bug#1576)
Barge blobs and split packets not being read correctly. (Bug#1576)
Backported fix for aliased tables and
UpdatableResultSets
in
checkUpdatability()
method from 3.1 branch.
(Bug#1534)
“Friendlier” exception message for
PacketTooLargeException
.
(Bug#1534)
Don't count quoted IDs when inside a 'string' in
PreparedStatement
parsing.
(Bug#1511)
Bugs fixed:
ResultSet.get/setString
mashing char 127.
(Bug#1247)
Added property to “clobber” streaming results, by
setting the clobberStreamingResults
property
to true
(the default is
false
). This will cause a
“streaming” ResultSet
to be
automatically closed, and any oustanding data still streaming
from the server to be discarded if another query is executed
before all the data has been read from the server.
(Bug#1247)
Added com.mysql.jdbc.util.BaseBugReport
to
help creation of testcases for bug reports.
(Bug#1247)
Backported authentication changes for 4.1.1 and newer from 3.1 branch. (Bug#1247)
Made databaseName
,
portNumber
, and serverName
optional parameters for
MysqlDataSourceFactory
.
(Bug#1246)
Optimized CLOB.setChracterStream()
.
(Bug#1131)
Fixed CLOB.truncate()
.
(Bug#1130)
Fixed deadlock issue with
Statement.setMaxRows()
.
(Bug#1099)
DatabaseMetaData.getColumns()
getting
confused about the keyword “set” in character
columns.
(Bug#1099)
Clip +/- INF (to smallest and largest representative values for
the type in MySQL) and NaN (to 0) for
setDouble
/setFloat()
, and
issue a warning on the statement when the server does not
support +/- INF or NaN.
(Bug#884)
Don't fire connection closed events when closing pooled
connections, or on
PooledConnection.getConnection()
with already
open connections.
(Bug#884)
Double-escaping of '\'
when charset is SJIS
or GBK and '\'
appears in non-escaped input.
(Bug#879)
When emptying input stream of unused rows for
“streaming” result sets, have the current thread
yield()
every 100 rows in order to not
monopolize CPU time.
(Bug#879)
Issue exception on
ResultSet.get
on empty result set (wasn't caught in some cases).
(Bug#848)XXX
()
Don't hide messages from exceptions thrown in I/O layers. (Bug#848)
Fixed regression in large split-packet handling. (Bug#848)
Better diagnostic error messages in exceptions for “streaming” result sets. (Bug#848)
Don't change timestamp TZ twice if
useTimezone==true
.
(Bug#774)
Don't wrap SQLExceptions
in
RowDataDynamic
.
(Bug#688)
Don't try and reset isolation level on reconnect if MySQL doesn't support them. (Bug#688)
The insertRow
in an
UpdatableResultSet
is now loaded with the
default column values when moveToInsertRow()
is called.
(Bug#688)
DatabaseMetaData.getColumns()
wasn't
returning NULL
for default values that are
specified as NULL
.
(Bug#688)
Change default statement type/concurrency to
TYPE_FORWARD_ONLY
and
CONCUR_READ_ONLY
(spec compliance).
(Bug#688)
Fix UpdatableResultSet
to return values for
get
when on
insert row.
(Bug#675)XXX
()
Support InnoDB
contraint names when
extracting foreign key information in
DatabaseMetaData
(implementing ideas from
Parwinder Sekhon).
(Bug#664, Bug#517)
Backported 4.1 protocol changes from 3.1 branch (server-side SQL states, new field information, larger client capability flags, connect-with-database, and so forth). (Bug#664, Bug#517)
refreshRow
didn't work when primary key
values contained values that needed to be escaped (they ended up
being doubly escaped).
(Bug#661)
Fixed ResultSet.previous()
behavior to move
current position to before result set when on first row of
result set.
(Bug#496)
Fixed Statement
and
PreparedStatement
issuing bogus queries when
setMaxRows()
had been used and a
LIMIT
clause was present in the query.
(Bug#496)
Faster date handling code in ResultSet
and
PreparedStatement
(no longer uses
Date
methods that synchronize on static
calendars).
Fixed test for end of buffer in
Buffer.readString()
.
Bugs fixed:
Fixed SJIS encoding bug, thanks to Naoto Sato. (Bug#378)
Fix problem detecting server character set in some cases. (Bug#378)
Allow multiple calls to Statement.close()
.
(Bug#378)
Return correct number of generated keys when using
REPLACE
statements.
(Bug#378)
Unicode character 0xFFFF in a string would cause the driver to
throw an ArrayOutOfBoundsException
. .
(Bug#378)
Fix row data decoding error when using very large packets. (Bug#378)
Optimized row data decoding. (Bug#378)
Issue exception when operating on an already closed prepared statement. (Bug#378)
Optimized usage of EscapeProcessor
.
(Bug#378)
Use JVM charset with filenames and LOAD DATA [LOCAL]
INFILE
.
Fix infinite loop with Connection.cleanup()
.
Changed Ant target compile-core
to
compile-driver
, and made testsuite
compilation a separate target.
Fixed result set not getting set for
Statement.executeUpdate()
, which affected
getGeneratedKeys()
and
getUpdateCount()
in some cases.
Return list of generated keys when using multi-value
INSERTS
with
Statement.getGeneratedKeys()
.
Allow bogus URLs in Driver.getPropertyInfo()
.
Bugs fixed:
Fixed charset issues with database metadata (charset was not getting set correctly).
You can now toggle profiling on/off using
Connection.setProfileSql(boolean)
.
4.1 Column Metadata fixes.
Fixed MysqlPooledConnection.close()
calling
wrong event type.
Fixed StringIndexOutOfBoundsException
in
PreparedStatement.setClob()
.
IOExceptions
during a transaction now cause
the Connection
to be closed.
Remove synchronization from Driver.connect()
and Driver.acceptsUrl()
.
Fixed missing conversion for YEAR
type in
ResultSetMetaData.getColumnTypeName()
.
Updatable ResultSets
can now be created for
aliased tables/columns when connected to MySQL-4.1 or newer.
Fixed LOAD DATA LOCAL INFILE
bug when file
> max_allowed_packet
.
Don't pick up indexes that start with pri
as
primary keys for DBMD.getPrimaryKeys()
.
Ensure that packet size from
alignPacketSize()
does not exceed
max_allowed_packet
(JVM bug)
Don't reset Connection.isReadOnly()
when
autoReconnecting.
Fixed escaping of 0x5c ('\'
) character for
GBK and Big5 charsets.
Fixed ResultSet.getTimestamp()
when
underlying field is of type DATE
.
Throw SQLExceptions
when trying to do
operations on a forcefully closed Connection
(that is, when a communication link failure occurs).
Bugs fixed:
Backported 4.1 charset field info changes from Connector/J 3.1.
Fixed Statement.setMaxRows()
to stop sending
LIMIT
type queries when not needed
(performance).
Fixed DBMD.getTypeInfo()
and
DBMD.getColumns()
returning different value
for precision in TEXT
and
BLOB
types.
Fixed SQLExceptions
getting swallowed on
initial connect.
Fixed ResultSetMetaData
to return
""
when catalog not known. Fixes
NullPointerExceptions
with Sun's
CachedRowSet
.
Allow ignoring of warning for “non transactional
tables” during rollback (compliance/usability) by setting
ignoreNonTxTables
property to
true
.
Clean up Statement
query/method mismatch
tests (that is, INSERT
not allowed with
.executeQuery()
).
Fixed ResultSetMetaData.isWritable()
to
return correct value.
More checks added in ResultSet
traversal
method to catch when in closed state.
Implemented Blob.setBytes()
. You still need
to pass the resultant Blob
back into an
updatable ResultSet
or
PreparedStatement
to persist the changes,
because MySQL does not support “locators”.
Add “window” of different NULL
sorting behavior to
DBMD.nullsAreSortedAtStart
(4.0.2 to 4.0.10,
true; otherwise, no).
Bugs fixed:
Fixed ResultSet.isBeforeFirst()
for empty
result sets.
Added missing LONGTEXT
type to
DBMD.getColumns()
.
Implemented an empty TypeMap
for
Connection.getTypeMap()
so that some
third-party apps work with MySQL (IBM WebSphere 5.0 Connection
pool).
Added update options for foreign key metadata.
Fixed Buffer.fastSkipLenString()
causing
ArrayIndexOutOfBounds
exceptions with some
queries when unpacking fields.
Quote table names in
DatabaseMetaData.getColumns()
,
getPrimaryKeys()
,
getIndexInfo()
,
getBestRowIdentifier()
.
Retrieve TX_ISOLATION
from database for
Connection.getTransactionIsolation()
when the
MySQL version supports it, instead of an instance variable.
Greatly reduce memory required for
setBinaryStream()
in
PreparedStatements
.
Bugs fixed:
Streamlined character conversion and byte[]
handling in PreparedStatements
for
setByte()
.
Fixed PreparedStatement.executeBatch()
parameter overwriting.
Added quoted identifiers to database names for
Connection.setCatalog
.
Added support for 4.0.8-style large packets.
Reduce memory footprint of PreparedStatements
by sharing outbound packet with MysqlIO
.
Added strictUpdates
property to allow control
of amount of checking for “correctness” of
updatable result sets. Set this to false
if
you want faster updatable result sets and you know that you
create them from SELECT
statements on tables
with primary keys and that you have selected all primary keys in
your query.
Added support for quoted identifiers in
PreparedStatement
parser.
Bugs fixed:
Allow user to alter behavior of Statement
/
PreparedStatement.executeBatch()
via
continueBatchOnError
property (defaults to
true
).
More robust escape tokenizer: Recognize --
comments, and allow nested escape sequences (see
testsuite.EscapeProcessingTest
).
Fixed Buffer.isLastDataPacket()
for 4.1 and
newer servers.
NamedPipeSocketFactory
now works (only
intended for Windows), see README
for
instructions.
Changed charsToByte
in
SingleByteCharConverter
to be non-static.
Use non-aliased table/column names and database names to fully
qualify tables and columns in
UpdatableResultSet
(requires MySQL-4.1 or
newer).
LOAD DATA LOCAL INFILE ...
now works, if your
server is configured to allow it. Can be turned off with the
allowLoadLocalInfile
property (see the
README
).
Implemented Connection.nativeSQL()
.
Fixed ResultSetMetaData.getColumnTypeName()
returning BLOB
for TEXT
and TEXT
for BLOB
types.
Fixed charset handling in Fields.java
.
Because of above, implemented
ResultSetMetaData.isAutoIncrement()
to use
Field.isAutoIncrement()
.
Substitute '?'
for unknown character
conversions in single-byte character sets instead of
'\0'
.
Added CLIENT_LONG_FLAG
to be able to get more
column flags (isAutoIncrement()
being the
most important).
Honor lower_case_table_names
when enabled in
the server when doing table name comparisons in
DatabaseMetaData
methods.
DBMD.getImported/ExportedKeys()
now handles
multiple foreign keys per table.
More robust implementation of updatable result sets. Checks that all primary keys of the table have been selected.
Some MySQL-4.1 protocol support (extended field info from selects).
Check for connection closed in more
Connection
methods
(createStatement
,
prepareStatement
,
setTransactionIsolation
,
setAutoCommit
).
Fixed ResultSetMetaData.getPrecision()
returning incorrect values for some floating-point types.
Changed SingleByteCharConverter
to use lazy
initialization of each converter.
Bugs fixed:
Implemented Clob.setString()
.
Added com.mysql.jdbc.MiniAdmin
class, which
allows you to send shutdown
command to MySQL
server. This is intended to be used when
“embedding” Java and MySQL server together in an
end-user application.
Added SSL support. See README
for
information on how to use it.
All DBMD
result set columns describing
schemas now return NULL
to be more compliant
with the behavior of other JDBC drivers for other database
systems (MySQL does not support schemas).
Use SHOW CREATE TABLE
when possible for
determining foreign key information for
DatabaseMetaData
. Also allows cascade options
for DELETE
information to be returned.
Implemented Clob.setCharacterStream()
.
Failover and autoReconnect
work only when the
connection is in an autoCommit(false)
state,
in order to stay transaction-safe.
Fixed DBMD.supportsResultSetConcurrency()
so
that it returns true
for
ResultSet.TYPE_SCROLL_INSENSITIVE
and
ResultSet.CONCUR_READ_ONLY
or
ResultSet.CONCUR_UPDATABLE
.
Implemented Clob.setAsciiStream()
.
Removed duplicate code from
UpdatableResultSet
(it can be inherited from
ResultSet
, the extra code for each method to
handle updatability I thought might someday be necessary has not
been needed).
Fixed UnsupportedEncodingException
thrown
when “forcing” a character encoding via properties.
Fixed incorrect conversion in
ResultSet.getLong()
.
Implemented ResultSet.updateBlob()
.
Removed some not-needed temporary object creation by smarter use
of Strings
in
EscapeProcessor
,
Connection
and
DatabaseMetaData
classes.
Escape 0x5c
character in strings for the SJIS
charset.
PreparedStatement
now honors stream lengths
in setBinary/Ascii/Character Stream() unless you set the
connection property
useStreamLengthsInPrepStmts
to
false
.
Fixed issue with updatable result sets and
PreparedStatements
not working.
Fixed start position off-by-1 error in
Clob.getSubString()
.
Added connectTimeout
parameter that allows
users of JDK-1.4 and newer to specify a maximum time to wait to
establish a connection.
Fixed various non-ASCII character encoding issues.
Fixed ResultSet.isLast()
for empty result
sets (should return false
).
Added driver property useHostsInPrivileges
.
Defaults to true
. Affects whether or not
@hostname
will be used in
DBMD.getColumn/TablePrivileges
.
Fixed
ResultSet.setFetchDirection(FETCH_UNKNOWN)
.
Added queriesBeforeRetryMaster
property that
specifies how many queries to issue when failed over before
attempting to reconnect to the master (defaults to 50).
Fixed issue when calling
Statement.setFetchSize()
when using arbitrary
values.
Properly restore connection properties when autoReconnecting or
failing-over, including autoCommit
state, and
isolation level.
Implemented Clob.truncate()
.
Bugs fixed:
Charsets now automatically detected. Optimized code for single-byte character set conversion.
Fixed ResultSetMetaData.isSigned()
for
TINYINT
and BIGINT
.
Fixed RowDataStatic.getAt()
off-by-one bug.
Fixed ResultSet.getRow()
off-by-one bug.
Massive code clean-up to follow Java coding conventions (the time had come).
Implemented ResultSet.getCharacterStream()
.
Added limited Clob
functionality
(ResultSet.getClob()
,
PreparedStatemtent.setClob()
,
PreparedStatement.setObject(Clob)
.
Connection.isClosed()
no longer
“pings” the server.
Connection.close()
issues
rollback()
when
getAutoCommit()
is false
.
Added socketTimeout
parameter to URL.
Added LOCAL TEMPORARY
to table types in
DatabaseMetaData.getTableTypes()
.
Added paranoid
parameter, which sanitizes
error messages by removing “sensitive” information
from them (such as hostnames, ports, or usernames), as well as
clearing “sensitive” data structures when possible.
Bugs fixed:
General source-code cleanup.
The driver now only works with JDK-1.2 or newer.
Fix and sort primary key names in DBMetaData
(SF bugs 582086 and 582086).
ResultSet.getTimestamp()
now works for
DATE
types (SF bug 559134).
Float types now reported as
java.sql.Types.FLOAT
(SF bug 579573).
Support for streaming (row-by-row) result sets (see
README
) Thanks to Doron.
Testsuite now uses Junit (which you can get from http://www.junit.org.
JDBC Compliance: Passes all tests besides stored procedure tests.
ResultSet.getDate/Time/Timestamp
now
recognizes all forms of invalid values that have been set to all
zeros by MySQL (SF bug 586058).
Added multi-host failover support (see
README
).
Repackaging: New driver name is
com.mysql.jdbc.Driver
, old name still works,
though (the driver is now provided by MySQL-AB).
Support for large packets (new addition to MySQL-4.0 protocol),
see README
for more information.
Better checking for closed connections in
Statement
and
PreparedStatement
.
Performance improvements in string handling and field metadata creation (lazily instantiated) contributed by Alex Twisleton-Wykeham-Fiennes.
JDBC-3.0 functionality including
Statement/PreparedStatement.getGeneratedKeys()
and ResultSet.getURL()
.
Overall speed improvements via controlling transient object
creation in MysqlIO
class when reading
packets.
!!! LICENSE CHANGE !!! The
driver is now GPL. If you need non-GPL licenses, please contact
me <mark@mysql.com>
.
Performance enchancements: Driver is now 50–100% faster in most situations, and creates fewer temporary objects.
Bugs fixed:
ResultSet.getDouble()
now uses code built
into JDK to be more precise (but slower).
Fixed typo for relaxAutoCommit
parameter.
LogicalHandle.isClosed()
calls through to
physical connection.
Added SQL profiling (to STDERR
). Set
profileSql=true
in your JDBC URL. See
README
for more information.
PreparedStatement
now releases resources on
.close()
. (SF bug 553268)
More code cleanup.
Quoted identifiers not used if server version does not support
them. Also, if server started with --ansi
or
--sql-mode=ANSI_QUOTES
,
“"
” will be used as an
identifier quote character, otherwise
“'
” will be used.
Bugs fixed:
Fixed unicode chars being read incorrectly. (SF bug 541088)
Faster blob escaping for PrepStmt
.
Added setURL()
to
MySQLXADataSource
. (SF bug 546019)
Added set
/getPortNumber()
to DataSource(s)
. (SF bug 548167)
PreparedStatement.toString()
fixed. (SF bug
534026)
More code cleanup.
Rudimentary version of
Statement.getGeneratedKeys()
from JDBC-3.0
now implemented (you need to be using JDK-1.4 for this to work,
I believe).
DBMetaData.getIndexInfo()
- bad PAGES fixed.
(SF BUG 542201)
ResultSetMetaData.getColumnClassName()
now
implemented.
Bugs fixed:
Fixed testsuite.Traversal
afterLast()
bug, thanks to Igor Lastric.
Added new types to getTypeInfo()
, fixed
existing types thanks to Al Davis and Kid Kalanon.
Fixed time zone off-by-1-hour bug in
PreparedStatement
(538286, 528785).
Added identifier quoting to all
DatabaseMetaData
methods that need them
(should fix 518108).
Added support for BIT
types (51870) to
PreparedStatement
.
ResultSet.insertRow()
should now detect
auto_increment fields in most cases and use that value in the
new row. This detection will not work in multi-valued keys,
however, due to the fact that the MySQL protocol does not return
this information.
Relaxed synchronization in all classes, should fix 520615 and 520393.
DataSources
- fixed setUrl
bug (511614, 525565), wrong datasource class name (532816,
528767).
Added support for YEAR
type (533556).
Fixes for ResultSet
updatability in
PreparedStatement
.
ResultSet
: Fixed updatability (values being
set to null
if not updated).
Added getTable/ColumnPrivileges()
to DBMD
(fixes 484502).
Added getIdleFor()
method to
Connection
and
MysqlLogicalHandle
.
ResultSet.refreshRow()
implemented.
Fixed getRow()
bug (527165) in
ResultSet
.
General code cleanup.
Bugs fixed:
Full synchronization of Statement.java
.
Fixed missing DELETE_RULE
value in
DBMD.getImported/ExportedKeys()
and
getCrossReference()
.
More changes to fix Unexpected end of input
stream
errors when reading BLOB
values. This should be the last fix.
Bugs fixed:
Fixed null-pointer-exceptions when using
MysqlConnectionPoolDataSource
with Websphere
4 (bug 505839).
Fixed spurious Unexpected end of input stream
errors in MysqlIO
(bug 507456).
Bugs fixed:
Fixed extra memory allocation in
MysqlIO.readPacket()
(bug 488663).
Added detection of network connection being closed when reading packets (thanks to Todd Lizambri).
Fixed casting bug in PreparedStatement
(bug
488663).
DataSource
implementations moved to
org.gjt.mm.mysql.jdbc2.optional
package, and
(initial) implementations of
PooledConnectionDataSource
and
XADataSource
are in place (thanks to Todd
Wolff for the implementation and testing of
PooledConnectionDataSource
with IBM WebSphere
4).
Fixed quoting error with escape processor (bug 486265).
Removed concatenation support from driver (the
||
operator), as older versions of VisualAge
seem to be the only thing that use it, and it conflicts with the
logical ||
operator. You will need to start
mysqld with the --ansi
flag
to use the ||
operator as concatenation (bug
491680).
Ant build was corrupting included
jar
files, fixed (bug 487669).
Report batch update support through
DatabaseMetaData
(bug 495101).
Implementation of
DatabaseMetaData.getExported/ImportedKeys()
and getCrossReference()
.
Fixed off-by-one-hour error in
PreparedStatement.setTimestamp()
(bug
491577).
Full synchronization on methods modifying instance and class-shared references, driver should be entirely thread-safe now (please let me know if you have problems).
Bugs fixed:
XADataSource
/ConnectionPoolDataSource
code (experimental)
DatabaseMetaData.getPrimaryKeys()
and
getBestRowIdentifier()
are now more robust in
identifying primary keys (matches regardless of case or
abbreviation/full spelling of Primary Key
in
Key_type
column).
Batch updates now supported (thanks to some inspiration from Daniel Rall).
PreparedStatement.setAnyNumericType()
now
handles positive exponents correctly (adds +
so MySQL can understand it).
Bugs fixed:
Character sets read from database if
useUnicode=true
and
characterEncoding
is not set. (thanks to
Dmitry Vereshchagin)
Initial transaction isolation level read from database (if avaialable). (thanks to Dmitry Vereshchagin)
Fixed PreparedStatement
generating SQL that
would end up with syntax errors for some queries.
PreparedStatement.setCharacterStream()
now
implemented
Captialize type names when
captializeTypeNames=true
is passed in URL or
properties (for WebObjects. (thanks to Anjo Krank)
ResultSet.getBlob()
now returns
null
if column value was
null
.
Fixed ResultSetMetaData.getPrecision()
returning one less than actual on newer versions of MySQL.
Fixed dangling socket problem when in high availability
(autoReconnect=true
) mode, and finalizer for
Connection
will close any dangling sockets on
GC.
Fixed time zone issue in
PreparedStatement.setTimestamp()
. (thanks to
Erik Olofsson)
PreparedStatement.setDouble() now uses full-precision doubles (reverting a fix made earlier to truncate them).
Fixed
DatabaseMetaData.supportsTransactions()
, and
supportsTransactionIsolationLevel()
and
getTypeInfo()
SQL_DATETIME_SUB
and
SQL_DATA_TYPE
fields not being readable.
Updatable result sets now correctly handle
NULL
values in fields.
PreparedStatement.setBoolean() will use 1/0 for values if your MySQL version is 3.21.23 or higher.
Fixed ResultSet.isAfterLast()
always
returning false
.
Bugs fixed:
Fixed PreparedStatement
parameter checking.
Fixed case-sensitive column names in
ResultSet.java
.
Bugs fixed:
ResultSet.insertRow()
works now, even if not
all columns are set (they will be set to
NULL
).
Added Byte
to
PreparedStatement.setObject()
.
Fixed data parsing of TIMESTAMP
values with
2-digit years.
Added ISOLATION
level support to
Connection.setIsolationLevel()
DataBaseMetaData.getCrossReference()
no
longer ArrayIndexOOB
.
ResultSet.getBoolean()
now recognizes
-1
as true
.
ResultSet
has +/-Inf/inf support.
getObject()
on ResultSet
correctly does
TINYINT
->Byte
and
SMALLINT
->Short
.
Fixed ResultSetMetaData.getColumnTypeName
for
TEXT
/BLOB
.
Fixed ArrayIndexOutOfBounds
when sending
large BLOB
queries. (Max size packet was not
being set)
Fixed NPE on
PreparedStatement.executeUpdate()
when all
columns have not been set.
Fixed ResultSet.getBlob()
ArrayIndex
out-of-bounds.
Bugs fixed:
Fixed composite key problem with updatable result sets.
Faster ASCII string operations.
Fixed off-by-one error in java.sql.Blob
implementation code.
Fixed incorrect detection of
MAX_ALLOWED_PACKET
, so sending large blobs
should work now.
Added detection of -/+INF for doubles.
Added ultraDevHack
URL parameter, set to
true
to allow (broken) Macromedia UltraDev to
use the driver.
Implemented getBigDecimal()
without scale
component for JDBC2.
Bugs fixed:
Columns that are of type TEXT
now return as
Strings
when you use
getObject()
.
Cleaned up exception handling when driver connects.
Fixed RSMD.isWritable()
returning wrong
value. Thanks to Moritz Maass.
DatabaseMetaData.getPrimaryKeys()
now works
correctly with respect to key_seq
. Thanks to
Brian Slesinsky.
Fixed many JDBC-2.0 traversal, positioning bugs, especially with respect to empty result sets. Thanks to Ron Smits, Nick Brook, Cessar Garcia and Carlos Martinez.
No escape processing is done on
PreparedStatements
anymore per JDBC spec.
Fixed some issues with updatability support in
ResultSet
when using multiple primary keys.
Fixes to ResultSet for insertRow() - Thanks to Cesar Garcia
Fix to Driver to recognize JDBC-2.0 by loading a JDBC-2.0 class, instead of relying on JDK version numbers. Thanks to John Baker.
Fixed ResultSet to return correct row numbers
Statement.getUpdateCount() now returns rows matched, instead of rows actually updated, which is more SQL-92 like.
10-29-99
Statement/PreparedStatement.getMoreResults() bug fixed. Thanks to Noel J. Bergman.
Added Short as a type to PreparedStatement.setObject(). Thanks to Jeff Crowder
Driver now automagically configures maximum/preferred packet sizes by querying server.
Autoreconnect code uses fast ping command if server supports it.
Fixed various bugs with respect to packet sizing when reading from the server and when alloc'ing to write to the server.
Now compiles under JDK-1.2. The driver supports both JDK-1.1 and JDK-1.2 at the same time through a core set of classes. The driver will load the appropriate interface classes at runtime by figuring out which JVM version you are using.
Fixes for result sets with all nulls in the first row. (Pointed out by Tim Endres)
Fixes to column numbers in SQLExceptions in ResultSet (Thanks to Blas Rodriguez Somoza)
The database no longer needs to specified to connect. (Thanks to Christian Motschke)
Better Documentation (in progress), in doc/mm.doc/book1.html
DBMD now allows null for a column name pattern (not in spec), which it changes to '%'.
DBMD now has correct types/lengths for getXXX().
ResultSet.getDate(), getTime(), and getTimestamp() fixes. (contributed by Alan Wilken)
EscapeProcessor now handles \{ \} and { or } inside quotes correctly. (thanks to Alik for some ideas on how to fix it)
Fixes to properties handling in Connection. (contributed by Juho Tikkala)
ResultSet.getObject() now returns null for NULL columns in the table, rather than bombing out. (thanks to Ben Grosman)
ResultSet.getObject() now returns Strings for types from MySQL that it doesn't know about. (Suggested by Chris Perdue)
Removed DataInput/Output streams, not needed, 1/2 number of method calls per IO operation.
Use default character encoding if one is not specified. This is a work-around for broken JVMs, because according to spec, EVERY JVM must support "ISO8859_1", but they don't.
Fixed Connection to use the platform character encoding instead of "ISO8859_1" if one isn't explicitly set. This fixes problems people were having loading the character- converter classes that didn't always exist (JVM bug). (thanks to Fritz Elfert for pointing out this problem)
Changed MysqlIO to re-use packets where possible to reduce memory usage.
Fixed escape-processor bugs pertaining to {} inside quotes.
Fixed character-set support for non-Javasoft JVMs (thanks to many people for pointing it out)
Fixed ResultSet.getBoolean() to recognize 'y' & 'n' as well as '1' & '0' as boolean flags. (thanks to Tim Pizey)
Fixed ResultSet.getTimestamp() to give better performance. (thanks to Richard Swift)
Fixed getByte() for numeric types. (thanks to Ray Bellis)
Fixed DatabaseMetaData.getTypeInfo() for DATE type. (thanks to Paul Johnston)
Fixed EscapeProcessor for "fn" calls. (thanks to Piyush Shah at locomotive.org)
Fixed EscapeProcessor to not do extraneous work if there are no escape codes. (thanks to Ryan Gustafson)
Fixed Driver to parse URLs of the form "jdbc:mysql://host:port" (thanks to Richard Lobb)
Fixed Timestamps for PreparedStatements
Fixed null pointer exceptions in RSMD and RS
Re-compiled with jikes for valid class files (thanks ms!)
Fixed escape processor to deal with unmatched { and } (thanks to Craig Coles)
Fixed escape processor to create more portable (between DATETIME and TIMESTAMP types) representations so that it will work with BETWEEN clauses. (thanks to Craig Longman)
MysqlIO.quit() now closes the socket connection. Before, after many failed connections some OS's would run out of file descriptors. (thanks to Michael Brinkman)
Fixed NullPointerException in Driver.getPropertyInfo. (thanks to Dave Potts)
Fixes to MysqlDefs to allow all *text fields to be retrieved as Strings. (thanks to Chris at Leverage)
Fixed setDouble in PreparedStatement for large numbers to avoid sending scientific notation to the database. (thanks to J.S. Ferguson)
Fixed getScale() and getPrecision() in RSMD. (contrib'd by James Klicman)
Fixed getObject() when field was DECIMAL or NUMERIC (thanks to Bert Hobbs)
DBMD.getTables() bombed when passed a null table-name pattern. Fixed. (thanks to Richard Lobb)
Added check for "client not authorized" errors during connect. (thanks to Hannes Wallnoefer)
Result set rows are now byte arrays. Blobs and Unicode work bidriectonally now. The useUnicode and encoding options are implemented now.
Fixes to PreparedStatement to send binary set by setXXXStream to be sent untouched to the MySQL server.
Fixes to getDriverPropertyInfo().
Changed all ResultSet fields to Strings, this should allow Unicode to work, but your JVM must be able to convert between the character sets. This should also make reading data from the server be a bit quicker, because there is now no conversion from StringBuffer to String.
Changed PreparedStatement.streamToString() to be more efficient (code from Uwe Schaefer).
URL parsing is more robust (throws SQL exceptions on errors rather than NullPointerExceptions)
PreparedStatement now can convert Strings to Time/Date values via setObject() (code from Robert Currey).
IO no longer hangs in Buffer.readInt(), that bug was introduced in 1.1d when changing to all byte-arrays for result sets. (Pointed out by Samo Login)
Fixes to DatabaseMetaData to allow both IBM VA and J-Builder to work. Let me know how it goes. (thanks to Jac Kersing)
Fix to ResultSet.getBoolean() for NULL strings (thanks to Barry Lagerweij)
Beginning of code cleanup, and formatting. Getting ready to branch this off to a parallel JDBC-2.0 source tree.
Added "final" modifier to critical sections in MysqlIO and Buffer to allow compiler to inline methods for speed.
9-29-98
If object references passed to setXXX() in PreparedStatement are null, setNull() is automatically called for you. (Thanks for the suggestion goes to Erik Ostrom)
setObject() in PreparedStatement will now attempt to write a serialized representation of the object to the database for objects of Types.OTHER and objects of unknown type.
Util now has a static method readObject() which given a ResultSet and a column index will re-instantiate an object serialized in the above manner.
Got rid of "ugly hack" in MysqlIO.nextRow(). Rather than catch an exception, Buffer.isLastDataPacket() was fixed.
Connection.getCatalog() and Connection.setCatalog() should work now.
Statement.setMaxRows() works, as well as setting by property maxRows. Statement.setMaxRows() overrides maxRows set via properties or url parameters.
Automatic re-connection is available. Because it has to "ping" the database before each query, it is turned off by default. To use it, pass in "autoReconnect=true" in the connection URL. You may also change the number of reconnect tries, and the initial timeout value via "maxReconnects=n" (default 3) and "initialTimeout=n" (seconds, default 2) parameters. The timeout is an exponential backoff type of timeout; for example, if you have initial timeout of 2 seconds, and maxReconnects of 3, then the driver will timeout 2 seconds, 4 seconds, then 16 seconds between each re-connection attempt.
Fixed handling of blob data in Buffer.java
Fixed bug with authentication packet being sized too small.
The JDBC Driver is now under the LPGL
8-14-98
Fixed Buffer.readLenString() to correctly read data for BLOBS.
Fixed PreparedStatement.stringToStream to correctly read data for BLOBS.
Fixed PreparedStatement.setDate() to not add a day. (above fixes thanks to Vincent Partington)
Added URL parameter parsing (?user=... and so forth).
Big news! New package name. Tim Endres from ICE Engineering is starting a new source tree for GNU GPL'd Java software. He's graciously given me the org.gjt.mm package directory to use, so now the driver is in the org.gjt.mm.mysql package scheme. I'm "legal" now. Look for more information on Tim's project soon.
Now using dynamically sized packets to reduce memory usage when sending commands to the DB.
Small fixes to getTypeInfo() for parameters, and so forth.
DatabaseMetaData is now fully implemented. Let me know if these drivers work with the various IDEs out there. I've heard that they're working with JBuilder right now.
Added JavaDoc documentation to the package.
Package now available in .zip or .tar.gz.
Implemented getTypeInfo(). Connection.rollback() now throws an SQLException per the JDBC spec.
Added PreparedStatement that supports all JDBC API methods for PreparedStatement including InputStreams. Please check this out and let me know if anything is broken.
Fixed a bug in ResultSet that would break some queries that only returned 1 row.
Fixed bugs in DatabaseMetaData.getTables(), DatabaseMetaData.getColumns() and DatabaseMetaData.getCatalogs().
Added functionality to Statement that allows executeUpdate() to store values for IDs that are automatically generated for AUTO_INCREMENT fields. Basically, after an executeUpdate(), look at the SQLWarnings for warnings like "LAST_INSERTED_ID = 'some number', COMMAND = 'your SQL query'". If you are using AUTO_INCREMENT fields in your tables and are executing a lot of executeUpdate()s on one Statement, be sure to clearWarnings() every so often to save memory.
Split MysqlIO and Buffer to separate classes. Some ClassLoaders gave an IllegalAccess error for some fields in those two classes. Now mm.mysql works in applets and all classloaders. Thanks to Joe Ennis <jce@mail.boone.com> for pointing out the problem and working on a fix with me.
Fixed DatabaseMetadata problems in getColumns() and bug in switch statement in the Field constructor. Thanks to Costin Manolache <costin@tdiinc.com> for pointing these out.
Incorporated efficiency changes from Richard Swift
<Richard.Swift@kanatek.ca> in
MysqlIO.java
and
ResultSet.java
:
We're now 15% faster than gwe's driver.
Started working on DatabaseMetaData
.
The following methods are implemented:
getTables()
getTableTypes()
getColumns()
getCatalogs()
Bugs fixed:
Changed tests to shutdown mysqld prior to deleting files.
Fixed port file to always be writen to datadir.
Added os.name-os.arch to resource directory mapping properties file.
Swapped out commercial binaries for v5.0.40.
Delete portFile
on shutdown.
Moved platform-map.properties
into
db-files.jar
.
Clarified the startup max wait numbers.
Updated build.xml
in preperation for next
beta build.
Removed use-default-architecture
property
replaced.
Bugs fixed:
Moved MysqldFactory
to main package.
Reformatting: Added newlines some files which did not end in them.
Swapped out commercial binaries for v5.0.36.
Found and removed dynamic linking in mysql_kill; updated solution.
Changed protected constructor of
SimpleMysqldDynamicMBean
from taking a
MysqldResource
to taking a
MysqldFactory
, in order to lay groundwork for
addressing BUG discovered by Andrew Rubinger. See:
MySQL
Forums (Actual testing with JBoss, and filing a bug, is
still required.)
build.xml
: usage
now
slightly more verbose; some reformatting.
Now incoporates Reggie Bernett's
SafeTerminateProcess
and only calls the
unsafe TerminateProcess as a final last resort.
New windows kill.exe
fixes bug where mysqld
was being force terminated. Issue reported by bruno haleblian
and others, see:
MySQL
Forums.
Replaced Boolean.parseBoolean
with JDK 1.4
compliant valueOf
.
Changed connector-mxj.properties
default
mysql version to 5.0.37.
In testing so far mysqld reliably shuts down cleanly much faster.
Added testcase to
com.mysql.management.jmx.AcceptanceTest
which
demonstrats that dataDir
is a mutable MBean
property.
Updated build.xml
in prep for next release.
Changed SimpleMysqldDynamicMBean
to create
MysqldResource
on demand in order to allow
setting of datadir
. (Rubinger bug
groundwork).
Clarified the synchronization of
MysqldResource
methods.
SIGHUP
is replaced with
MySQLShutdown<PID>
event.
Clarified the immutability of baseDir
,
dataDir
, pidFile
,
portFile
.
Added 5.1.15 binaries to the repository.
Removed 5.1.14 binaries from the repository.
Added getDataDir()
to interface
MysqldResourceI
.
Added 5.1.14 binaries to repository.
Replaced windows kill.exe resource with re-written version specific to mysqld.
Added Patched StandardSocketFactory
from
Connector/J 5-0 HEAD.
Ensured 5.1.14 compatibility.
Swapped out gpl binaries for v5.0.37.
Removed 5.0.22 binaries from the repository.
Bugs fixed:
Allow multiple calls to start server from URL connection on non-3306 port. (Bug#24004)
Updated build.xml
to build to handle with
different gpl and commercial mysld version numbers.
Only populate the options map from the help text if specifically requested or in the MBean case.
Introduced property for Linux & WinXX to default to 32bit versions.
Swapped out gpl binaries for v5.0.27.
Swapped out commercial binaries for v5.0.32.
Moved mysqld binary resourced into separate jar file NOTICE:
CLASSPATH
will now need to
connector-mxj-db-files.jar
.
Minor test robustness improvements.
Moved default version string out of java class into a text
editable properties file
(connector-mxj.properties
) in the resources
directory.
Fixed test to be tollerant of /tmp
being a
symlink to /foo/tmp
.
Bugs fixed:
Removed unused imports, formatted code, made minor edits to tests.
Removed "TeeOutputStream" - no longer needed.
Swapped out the mysqld binaries for MySQL v5.0.22.
Bugs fixed:
Replaced string parsing with JDBC connection attempt for
determining if a mysqld is "ready for connections"
CLASSPATH
will now need to include
Connector/J jar.
"platform" directories replace spaces with underscores
extracted array and list printing to ListToString utility class
Swapped out the mysqld binaries for MySQL v5.0.21
Added trace level logging with Aspect/J.
CLASSPATH
will now need to include
lib/aspectjrt.jar
reformatted code
altered to be "basedir" rather than "port" oriented.
help parsing test reflects current help options
insulated users from problems with "." in basedir
swapped out the mysqld binaries for MySQL v5.0.18
Made tests more robust be deleting the /tmp/test-c.mxj directory before running tests.
ServerLauncherSocketFactory.shutdown API change: now takes File parameter (basedir) instead of port.
socket is now "mysql.sock" in datadir
added ability to specify "mysql-version" as an url parameter
Extended timeout for help string parsing, to avoid cases where the help text was getting prematurely flushed, and thus truncated.
swapped out the mysqld binaries for MySQL v5.0.19
MysqldResource now tied to dataDir as well as basedir (API CHANGE)
moved PID file into datadir
ServerLauncherSocketFactory.shutdown now works across JVMs.
extracted splitLines(String) to Str utility class
ServerLauncherSocketFactory.shutdown(port) no longer throws, only reports to System.err
ServerLauncherSocketFactory now treats URL parameters in the
form of &server.foo=null
as
serverOptionMap.put("foo", null)
ServerLauncherSocketFactory.shutdown API change: now takes 2 File parameters (basedir, datadir)
Bugs fixed:
Removed HelpOptionsParser's need to reference a MysqldResource.
Reorganized utils into a single "Utils" collaborator.
Minor test tweaks
Altered examples and tests to use new Connector/J 5.0 URL syntax for for launching Connector/MXJ ("jdbc:mysql:mxj://")
Swapped out the mysqld binaries for MySQL v5.0.16.
Ditched "ClassUtil" (merged with Str).
Minor refactorings for type casting and exception handling.
Functionality added or changed:
When using read/write splitting and the
rw-splitting.lua
example script, connecting
a second user to the proxy returns an error message.
(Bug#30867)
Added support in read_query_result()
to
overwrite the result-set.
Added --no-daemon
and
--pid-file
.
Added hooks for read_auth()
,
read_handshake()
and
read_auth_result()
.
Added handling of
proxy.connection.backend_ndx
in
connect_server()
and
read_query()
to support read/write
splitting.
Added support for proxy.response.packets
.
Added testcases.
Added --no-proxy
to disable the proxy.
Added support for listening UNIX sockets.
Added a global lua-scope proxy.global.*
.
Added connection pooling.
Bugs fixed:
Fixed assertion on COM_BINLOG_DUMP
.
(Bug#29764)
Fixed assertion on result-packets like [ field-len |
fields | EOF | ERR ]
.
(Bug#29732)
Fixed assertion at login with empty password + empty default db. (Bug#29719)
Fixed assertion at COM_SHUTDOWN
.
(Bug#29719)
Fixed crash if proxy.connection
is used in
connect_server()
.
Fixed check for glib2
to require at least
2.6.0.
Fixed assertion when all backends are down and we try to connect.
Fixed connection-stalling if
read_query_result()
throws an
assert()
ion.
Fixed len-encoding on proxy.resulsets
.
Fixed compilation on win32.
Fixed assertion when connecting to the MySQL 6.0.1.
Fixed decoding of len-encoded ints for 3-byte notation.
Fixed inj.resultset.affected_rows
on
SELECT
queries.
Fixed handling of (SQL) NULL
in result-sets.
Fixed mem-leak with proxy.response.*
is used.
Functionality added or changed:
Added resultset.affected_rows
and
resultset.insert_id
.
Changed --proxy.profiling
to
--proxy-skip-profiling
.
Added missing dependency to
libmysqlclient-dev
to the INSTALL file.
Added inj.query_time
and
inj.response_time
into the lua scripts.
Added support for pre-4.1 passwords in a 4.1 connection.
Added script examples for rewriting and injection.
Added proxy.VERSION
.
Added support for UNIX sockets.
Added protection against duplicate resultsets from a script.
Bugs fixed:
Fixed mysql check in configure to die when mysql.h isn't detected.
Fixed handling of duplicate ERR on
COM_CHANGE_USER
in MySQL 5.1.18+.
Fixed compile error with MySQL 4.1.x on missing COM_STMT_*.
Fixed crash on fields > 250 bytes when the resultset is inspected.
Fixed warning if connect_server()
is not
provided.
Fixed assertion when a error occurs at initial script exec time.
Fixed assertion when read_query_result()
is
not provided when PROXY_SEND_QUERY
is used.