Table of Contents
This appendix lists the changes from version to version in the MySQL source code through the latest version of MySQL 5.4, which is currently MySQL 5.4.3. We offer a version of the Manual for each series of MySQL releases (5.0, 5.1, and so forth). For information about changes in another release series of the MySQL database software, see the corresponding version of this Manual.
We update this section as we add new features in the 5.4 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 Bazaar 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 features added in MySQL 5.4 can be found here: Section 1.5, “What Is New in MySQL 5.4”. For a full list of changes, please refer to the changelog sections for individual 5.4 releases.
For discussion of upgrade issues that you may encounter for upgrades from MySQL 5.1 to MySQL 5.4, see Section 2.12.1.1, “Upgrading from MySQL 5.1 to 5.4”.
Functionality added or changed:
Incompatible Change:
If you upgrade to MySQL 5.4.3 from an earlier 5.4 release, the
server may fail to start due to changes in the default values of
innodb_log_files_in_group
and
innodb_log_file_size
, which
differ from those in earlier 5.4 releases. You should discard
the old InnoDB
log files and let
MySQL 5.4.3 create new ones. It is necessary to shut down your
current server cleanly so that no outstanding transaction
information remains in the log. The procedure to use depends on
the value of
innodb_fast_shutdown
used in
your current server:
If innodb_fast_shutdown
is
not set to 2: Stop your current MySQL server and make sure
that it shuts down without errors (to ensure that there is
no information for outstanding transactions in the log).
Copy the old log files into a safe place in case something
went wrong during the shutdown and you need them to recover
the tablespace. Delete the old log files and edit
my.cnf
if necessary to specify the
desired log file configuration. Then upgrade to MySQL 5.4.3
and start the new server. mysqld sees
that no InnoDB
log files exist
at startup and creates new ones.
If innodb_fast_shutdown
is
set to 2: Shut down your current server, set
innodb_fast_shutdown
to 1,
and restart the server. The server should be allowed to
recover. Then you should shut down the server again and
follow the procedure described in the preceding item to
change InnoDB
log file size.
Set innodb_fast_shutdown
back to 2 and start the MySQL 5.4.3 server.
Incompatible Change:
The following list indicates InnoDB
configuration changes in MySQL 5.4.3, compared to previous
versions of MySQL 5.4. For a description of cumulative changes
in MySQL 5.4 compared to MySQL 5.1, see
Section 1.5, “What Is New in MySQL 5.4”.
The default value of these system variables was changed:
Variable | Change in default value |
---|---|
innodb_autoextend_increment
| From 64MB to 8MB |
innodb_buffer_pool_size
| From 1GB to 128MB |
innodb_log_buffer_size
| From 16MB to 8MB |
innodb_log_file_size
| From 128MB to 5MB |
innodb_log_files_in_group
| From 3 to 2 |
innodb_read_io_threads
| From 8 to 4 |
innodb_write_io_threads
| From 8 to 4 |
These default value changes in most cases revert changes made in earlier MySQL 5.4 releases. The result is that the defaults are more similar to those in MySQL 5.1.
On Linux (and perhaps other systems), the performance of MySQL
Server can be improved by using a different
malloc()
implementation, developed by Google
and called tcmalloc
. The gain is noticeable
with a higher number of simultaneous users. MySQL 5.4.1 was
linked against this library, which improved performance but
imposed some restrictions. As a result of these restrictions,
MySQL 5.4.3 uses a different approach:
The server is linked against the default
malloc()
provided by the respective
platform.
Binary distributions for Linux include
libtcmalloc_minimal.so
(a shared
library that can be linked against at runtime) in
pkglibdir
(that is, the same directory
within the package where server plugins and similar object
files are located). The version of
tcmalloc
included with MySQL 5.4.3 comes
from google-perftools
1.4.
If you want to try tcmalloc
but are using
a binary distribution for a non-Linux platform or a source
distribution, you can install Google's
tcmalloc
. Some distributions provide it
in a google-perftools
package or with a
similar name, or you can download it from Google at
http://code.google.com/p/google-perftools/
and compile it yourself.
mysqld_safe now supports a
--malloc-lib
option that
enables administrators to specify that
mysqld should use
tcmalloc
.
The --malloc-lib
option
works by modifying the LD_PRELOAD
environment
value to affect dynamic linking to enable the loader to find the
memory-allocation library when mysqld runs:
If the option is not given, or is given without a value
(--malloc-lib=
),
LD_PRELOAD
is not modified and no attempt
is made to use tcmalloc
.
If the option is given as
--malloc-lib=tcmalloc
,
mysqld_safe looks for a
tcmalloc
library in
/usr/lib
and then in the MySQL
pkglibdir
location (for example,
/usr/local/mysql/lib
or whatever is
appropriate). If tmalloc
is found, its
path name is added to the beginning of the
LD_PRELOAD
value for
mysqld. If tcmalloc
is
not found, mysqld_safe aborts with an
error.
If the option is given as
--malloc-lib=
,
that full path is added to the beginning of the
/path/to/some/library
LD_PRELOAD
value. If the full path points
to a nonexistent or unreadable file,
mysqld_safe aborts with an error.
For cases where mysqld_safe adds a path
name to LD_PRELOAD
, it adds the path to
the beginning of any existing value the variable already
has.
As a result of the preceding changes, Linux users can use the
libtcmalloc_minimal.so
now included in
binary packages by adding these lines to the
my.cnf
file:
[mysqld_safe] malloc-lib=tcmalloc
Those lines also suffice for users on any platform who have
installed a tcmalloc
package in
/usr/lib
. To use a specific
tcmalloc
library, specify its full path name.
Example:
[mysqld_safe] malloc-lib=/opt/lib/libtcmalloc_minimal.so
Bugs fixed:
Performance:
For MyISAM
tables with
bulk_insert_buffer_size
values
larger than 256KB, the performance of bulk insert operations
such as multiple-row INSERT
and
INSERT ...
SELECT
operations has been improved greatly when up to
a hundred rows are inserted at the same time.
(Bug#44723)
Partitioning: Replication:
Attempting to replicate an
INSERT ...
SELECT
statement on a partitioned table using
row-based replication caused the slave to crash.
(Bug#44108)
Partitioning: When reorganizing partitions, not all affected subpartitions were removed prior to renaming. One way in which the issue was visible was that attempting to reorganize two partitions into a single partition having the same name as one of the original partitions could lead to a crash of the server. (Bug#47029)
Partitioning:
An INSERT ...
SELECT
statement on an empty partition of a
partitioned table failed with ERROR 1030 (HY000): Got
error 124 from storage engine. This issue also
caused queries run against a partitioned table while a
LOAD DATA CONCURRENT
INFILE
statement was in progress to fail with the same
error.
(Bug#46639)
Partitioning:
An online or fast ALTER TABLE
of
a partitioned table could leave behind temporary files in the
database directory.
(Bug#46483)
Partitioning:
A partitioned table having a
TIMESTAMP
column with a default
value of CURRENT_TIMESTAMP
and this column
was not defined using an ON UPDATE
option, an
ALTER TABLE ...
REORGANIZE PARTITION
statement on the table caused the
TIMESTAMP
column value to be set
to CURRENT_TIMESTAMP
regardless.
(Bug#46478)
Partitioning:
Partition pruning did not always work correctly when the
table's partitioning key used the
TO_DAYS()
function.
(Bug#46362)
Partitioning:
Inserting negative values into an
AUTO_INCREMENT
column of a partitioned table
could lead to apparently unrelated errors or a crash of the
server.
(Bug#45823)
Partitioning: Attempting to access a partitioned table when partitioning support was disabled in a MySQL server binary that had been compiled with partitioning support caused the server to crash. (Bug#39893)
Partitioning: Unnecessary calls were made in the server code for performing bulk inserts on partitions for which no inserts needed to be made. (Bug#35845)
See also Bug#35843.
Partitioning:
The use of TO_DAYS()
in the
partitioning expression led to selection failures when the
column having the date value contained invalid dates. This
occurred because the function returns NULL
in
such cases, and the partition containing NULL values was pruned
away. For example, this problem occurred if
'2001-02-00'
was inserted into a
DATE
column of such a table, and
a subsequent query on this table used WHERE
—while
date_col
<
'2001-02-00''2001-01-01'
is less than
'2001-02-00'
,
TO_DAYS('2001-02-00')
evaluates as
NULL
, and so the row containing
'2001-01-01'
was not returned. Now, for
tables using RANGE
or LIST
partitioning and having TO_DAYS()
in the partitioning expression, the NULL
partition is also scanned instead of being ignored.
The fix for this issue also corrects misbehavior such that a
query of the form SELECT * FROM
on a table
partitioned by table
WHERE
date_col
<
date_val
RANGE
or
LIST
was handled as though the server SQL
mode included
ALLOW_INVALID_DATES
even if
this was not actually part of the server SQL mode at the time
the query was issued.
(Bug#20577)
Replication:
Performing a multi-row update of the
AUTO_INCREMENT
column of a transactional
table could result in an inconsistency between master and slave
when there was a trigger on the transactional table that updated
a nontransactional table. When such an update failed on the
master, no rows were updated on the master, but some rows could
(erroneously) be updated on the slave.
(Bug#46864)
Replication:
When using the
--replicate-rewrite-db
option and
the database referenced by this option on the master was the
current database when the connection to the slave was closed,
any temporary tables existing in this database were not properly
dropped.
(Bug#46861)
Replication: When a statement that changed both transactional and nontransactional tables failed, the transactional changes were automatically rolled back on the master but the slave ignored the error and did not roll them back, thus leading to inconsistencies between master and slave.
This issue is fixed by automatically rolling back a statement
that fails on the slave; however, the transaction is not rolled
back unless a corresponding
ROLLBACK
statement is found in the relay log file.
(Bug#46130)
See also Bug#33864.
Replication:
When using row-based replication, importing a dump made with
mysqldump and replicating a row with an
AUTO_INCREMENT
column set to 0, with
NO_AUTO_VALUE_ON_ZERO
active
on the master, the row was inserted successfully on the master;
however any setting for
NO_AUTO_VALUE_ON_ZERO
was
ignored on the slave. When the AUTO_INCREMENT
column was incremented, this caused replication to fail on the
slave due to a duplicate key error. In some cases it could also
cause the slave to crash.
(Bug#45999)
Replication:
When slave_transaction_retries
is set, a statement that replicates, but is then rolled back due
to a deadlock on the slave, should be retried. However, in
certain cases, replication was stopped with error 1213
(Deadlock found when trying to get lock; try
restarting transaction) instead, even when this
variable was set.
(Bug#45694)
Replication:
The binary logging behavior (and thus, the replication behavior)
of CREATE
DATABASE IF NOT EXISTS
,
CREATE TABLE IF
NOT EXISTS
, and
CREATE EVENT IF
NOT EXISTS
was not consistent among these statements,
nor with that of
DROP DATABASE IF
EXISTS
,
DROP TABLE IF
EXISTS
, and
DROP EVENT IF
EXISTS
: A DROP ... IF EXISTS
statement is always logged even if the database object named in
the statement does not exist. However, of the CREATE
... IF NOT EXISTS
statements, only the
CREATE EVENT IF
NOT EXISTS
statement was logged when the database
object named in the statement already existed.
Now, every CREATE ... IF NOT EXISTS
statement
is written to the binary log (and thus replicated), whether the
database object named in the statement exists or not. For more
information, see
Section 16.4.1.3, “Replication of CREATE ... IF NOT EXISTS
Statements”.
Exception.
Replication and logging of
CREATE TABLE IF
NOT EXISTS ... SELECT
continues to be handled
according to existing rules. See
Section 16.4.1.4, “Replication of CREATE
TABLE ... SELECT
Statements”, for more
information.
Replication:
When using statement-based replication, database-level character
sets were not always honored by the replication SQL thread. This
could cause data inserted on the master using
LOAD DATA
to be replicated using
the wrong character set.
This was not an issue when using row-based replication.
Replication:
In some cases, a STOP SLAVE
statement could cause the replication slave to crash. This issue
was specific to MySQL on Windows or Macintosh platforms.
(Bug#45238, Bug#45242, Bug#45243, Bug#46013, Bug#46014, Bug#46030)
See also Bug#40796.
Replication:
Creating a scheduled event whose DEFINER
clause was either set to
CURRENT_USER
or not set
explicitly caused the master and the slave to become
inconsistent. This issue stems from the fact that, in both
cases, the DEFINER
is set to the
CURRENT_USER
of the current
thread. (On the master, the
CURRENT_USER
is the
mysqld user; on the slave, the
CURRENT_USER
is empty.)
This behavior has been modified as follows:
If CURRENT_USER
is used as
the DEFINER
, it is replaced with the
value of
CURRENT_USER
before the
CREATE EVENT
statement is
written to the binary log.
If the definer is not set explicitly, a
DEFINER
clause using the value of
CURRENT_USER
is added to the
CREATE EVENT
statement before
it is written to the binary log.
See also Bug#42217.
Replication:
When using the statement-based logging format, the only possible
safe combination of transactional and nontransactional
statements within the same transaction is to perform any updates
on nontransactional tables (such as
MyISAM
tables) first, before
updating any transactional tables (such as those using the
InnoDB
storage engine). This is due
to the fact that, although a modification made to a
nontransactional table is immediately visible to other
connections, the update is not immediately written to the binary
log, which can lead to inconsistencies between master and slave.
(Other combinations may hide a causal dependency, thus making it
impossible to write statements updating nontransactional tables
to the binary log in the correct order.)
However, in some cases, this situation was not handled properly, and the determination whether a given statement was safe or not under these conditions was not always correct. In particular, a multi-table update that affected both transactional and nontransactional tables or a statement modifying data in a nontransactional table having a trigger that operated on a transactional table (or the reverse) was not determined to be unsafe when it should have been.
With this fix, the following determinations regarding replication safety are made when combining updates to transactional and nontransactional tables within the same transaction in statement-based logging mode:
Any statement modifying data in a nontransactional table within a given transaction is considered safe if it is issued prior to any data modification statement accessing a transactional table within the same transaction.
A statement that updates transactional tables only is always considered safe.
A statement affecting both transactional and
nontransactional tables within a transaction is always
considered unsafe. It is not necessary that both tables be
modified for this to be true; for example, a statement such
as INSERT INTO
is also
considered unsafe.
innodb_table
SELECT * FROM
myisam_table
The current fix is valid only when using statement-based
logging mode; we plan to address similar issues occurring when
using the MIXED
or ROW
format in a future MySQL release.
The ARCHIVE
storage engine lost
records during a bulk insert.
(Bug#46961)
CONCAT_WS()
could return
incorrect results due to an argument buffer also being used as a
result buffer.
(Bug#46815)
Stack overflow checking did not account for the size of the structure stored in the heap. (Bug#46807)
The server crashed when re-using outer column references in correlated subqueries when the enclosing query used a temp table. (Bug#46791)
The server could crash for queries with the following elements:
1. An “impossible where” in the outermost
SELECT
; 2. An aggregate in the outermost
SELECT
; 3. A correlated subquery with a
WHERE
clause that includes an outer field
reference as a top-level WHERE
sargable
predicate;
(Bug#46749)
Assertion failure could result from repeated execution of a stored procedure containing an incorrect query with a subselect. (Bug#46629)
CREATE TABLE ...
SELECT
could cause assertion failure if a table
already existed with the same name and contained an
AUTO_INCREMENT
column.
(Bug#46616)
SHOW CREATE TRIGGER
for a
MERGE
table trigger caused an
assertion failure.
(Bug#46614)
In queries for which the loose index scan access method was
chosen, using a condition of the form
col_name
rather than the equivalent
caused an assertion failure.
(Bug#46607)col_name
<>
0
The server ignored the setting of
sync_frm
for
CREATE TABLE ...
LIKE
.
(Bug#46591)
TRUNCATE TABLE
for a table that
was opened with HANDLER
did not
close the handler and left it in an inconsistent state that
could lead to a server crash. Now TRUNCATE
TABLE
for a table closes all open handlers for the
table.
(Bug#46456)
An attempt to create a table with the same name as an existing view could cause a server crash. (Bug#46384)
A parser problem prevented properly stripping backquotes from an
argument to a user-defined function (UDF). If the UDF was in an
ORDER BY
clause, its name would not be
properly resolved against an alias with the same name in the
select list.
(Bug#46259)
A query containing a subquery in the FROM
clause and PROCEDURE ANALYSE()
caused a
server crash.
(Bug#46184)
See also Bug#48293.
Certain SELECT
statements
containing DISTINCT
, GROUP
BY
, and HAVING
clauses could hang
in an infinite loop.
(Bug#46159)
Killing a query that was performing a sort could result in a memory leak. (Bug#45962)
A Valgrind error when opening the
init_file
file was corrected.
(Bug#45894)
CREATE TEMPORARY TABLE
failed for
InnoDB
tables on systems with
case-insensitive file systems when
lower_case_table_names
= 2
and the pathname of the temporary file
directory contained uppercase characters.
(Bug#45638)
Truncation of DECIMAL
values
could lead to assertion failures; for example, when deducing the
type of a table column from a literal
DECIMAL
value.
(Bug#45261)
See also Bug#48370.
When re-installing MySQL on Windows on a server that has a data
directory from a previous MySQL installation, the installer
would fail to identify the existence of the installation and the
password configured for the root
user.
(Bug#45200)
Debug builds of the server on Windows crashed in debugging code. (Bug#45118)
The default value of
innodb_buffer_pool_size
was set
to 1GB in MySQL 5.4.0. This was too large for many
installations, so the default has been lowered to 128MB.
(Bug#44408)
SHOW ERRORS
returned an empty
result set after an attempt to drop a nonexistent table.
(Bug#42364)
A test for stack growth failed on some platforms, leading to server crashes. (Bug#42213)
A buffer overflow could occur during handling of IS
NULL
ranges.
(Bug#37044)
mysqladmin --wait ping crashed on Windows systems. (Bug#35132)
myisamchk performed parameter value casting at startup that generated unnecessary warning messages. (Bug#33785)
When using the ARCHIVE
storage
engine, SHOW TABLE STATUS
displayed incorrect
information for Max_data_length
,
Data_length
and
Avg_row_length
.
(Bug#29203)
InnoDB Notes:
As of MySQL 5.4.2, the InnoDB Plugin
is
included in MySQL 5.4 releases. The version of the
InnoDB Plugin
in this release is 1.0.4 and is
considered of Beta quality. It becomes the built-in version of
InnoDB
in MySQL Server, replacing the version
previously included as the built-in InnoDB
engine.
A number of performance and scalability enhancements were made
to the previous built-in version of InnoDB
in
MySQL 5.4.0 and 5.4.1. InnoDB Plugin
also
provides improvements in these areas, and in addition offers new
features and capabilities for flexibility and ease of use. Among
these features are enhanced reliability, “Fast index
creation,” table and index compression, file format
management, new INFORMATION_SCHEMA
tables,
capacity tuning, multiple background I/O threads, and group
commit.
For information about these features, see
InnoDB Plugin 1.0 for MySQL 5.1 User’s Guide. For general information
about using InnoDB
in MySQL, see
Section 13.6, “The InnoDB
Storage Engine”.
Due to inclusion of InnoDB Plugin
, a number
of InnoDB
configuration changes
were made, as described later in this section.
Functionality added or changed:
Incompatible Change:
The inclusion of InnoDB Plugin
as the
built-in version of InnoDB
in MySQL Server
results in an incompatibility for upgrades from MySQL 5.1.
InnoDB Plugin
is available in MySQL 5.1 as of
5.1.38, but it is an optional storage engine that must be
enabled explicitly using two server options:
[mysqld] ignore-builtin-innodb plugin-load=innodb=ha_innodb_plugin.so
If you were using InnoDB Plugin
in MySQL 5.1
by means of those options, you must remove them after an upgrade
to 5.4 or the server will fail to start.
Incompatible Change:
If you upgrade to MySQL 5.4.2 from MySQL 5.1, the server may
fail to start due to InnoDB
log
file configuration changes. MySQL 5.4 increases the default
value of
innodb_log_files_in_group
from
2 to 3. It also increases the default value of
innodb_log_file_size
from 5MB
to 128MB. (MySQL 5.4.0 increased the minimum value of
innodb_log_file_size
from 1MB
to 32MB, but this has been reverted to 1MB in 5.4.2.)
For an upgrade to MySQL 5.4.2, you should discard the old
InnoDB
log files and let MySQL
5.4.2 create new ones. It is necessary to shut down your current
server cleanly so that no outstanding transaction information
remains in the log. The procedure to use depends on the value of
innodb_fast_shutdown
used in
your current server:
If innodb_fast_shutdown
is
not set to 2: Stop your current MySQL server and make sure
that it shuts down without errors (to ensure that there is
no information for outstanding transactions in the log).
Copy the old log files into a safe place in case something
went wrong during the shutdown and you need them to recover
the tablespace. Delete the old log files and edit
my.cnf
if necessary to specify the
desired log file configuration. Then upgrade to MySQL 5.4.2
and start the new server. mysqld sees
that no InnoDB
log files exist
at startup and creates new ones.
If innodb_fast_shutdown
is
set to 2: Shut down your current server, set
innodb_fast_shutdown
to 1,
and restart the server. The server should be allowed to
recover. Then you should shut down the server again and
follow the procedure described in the preceding item to
change InnoDB
log file size.
Set innodb_fast_shutdown
back to 2 and start the MySQL 5.4.2 server.
Incompatible Change:
The following list indicates InnoDB
configuration changes in MySQL 5.4.2, compared to previous
versions of MySQL 5.4. For a description of cumulative changes
in MySQL 5.4 compared to MySQL 5.1, see
Section 1.5, “What Is New in MySQL 5.4”.
These system variables were added:
innodb_adaptive_flushing
:
Controls adaptive flushing of dirty pages.
innodb_change_buffering
:
Controls insert buffering.
innodb_file_format
: The
format for new InnoDB
tables.
innodb_file_format_check
:
Whether to perform file format compatibility checking.
innodb_read_ahead_threshold
:
Controls sensitivity of linear read-ahead.
innodb_replication_delay
:
The replication thread delay (in ms) on a slave server if
innodb_thread_concurrency
is reached.
innodb_spin_wait_delay
:
Maximum delay between polls for a spin lock.
innodb_stats_sample_pages
:
How many index pages to sample for statistics calculations.
innodb_strict_mode
: Whether
InnoDB
returns errors rather than
warnings for certain exceptional conditions (analogous to
strict SQL mode).
innodb_use_sys_malloc
:
Whether InnoDB
uses the OS (system) or
its own memory allocator.
innodb_version
: The current
version of InnoDB
.
More information about the new system variables can be found at InnoDB Plugin 1.0 for MySQL 5.1 User’s Guide.
These system variables have been made dynamic and can be modified at runtime:
innodb_adaptive_hash_index
(global value)
innodb_file_per_table
(global value)
innodb_io_capacity
(global
value)
innodb_lock_wait_timeout
(global and session values)
These system variables were removed, along with the functionality that they represented:
innodb_extra_dirty_writes
innodb_max_merged_io
innodb_thread_concurrency_timer_based
The minimum value of these system variables was changed:
Variable | Change in minimum value |
---|---|
innodb_additional_mem_pool_size
| From 2MB to 512KB |
innodb_buffer_pool_size
| From 64MB to 5MB |
innodb_log_buffer_size
| From 2MB to 256KB |
innodb_log_file_size
| From 32MB to 1MB |
These minimum value changes in most cases revert changes made in MySQL 5.4.0.
The default value of this system variable was changed:
Variable | Change in default value |
---|---|
innodb_sync_spin_loops
| From 20 to 30 |
These status variables were renamed or removed:
Innodb_have_sync_atomic
: renamed to
Innodb_have_atomic_builtins
Innodb_heap_enabled
: Removed
Innodb_wake_ups
: Removed
Important Change: Replication: Previously, incident log events were represented as comments in the output from mysqlbinlog, making them effectively silent when playing back the binlog.
(An incident log event represents an incident that could cause the contents of the database to change without that event being recorded in the binary log.)
This meant that, if the SQL were applied to a server, it could
potentially lead to the master and the slave having different
data. To make it possible to handle incident log events without
breaking applications that expect the previous behavior, the
nonsense statement RELOAD DATABASE
is added
to the SQL output for that incident log event, which causes an
error.
To use this functionality currently requires hand editing of the dump file and handling of each case on an individual basis by a database administrator before applying the output to a server. (Bug#44442)
Replication:
With statement-based logging (SBL), repeatedly calling
statements that are unsafe for SBL caused a warning message to
be written to the error log for each statement, and there was no
way to disable this behavior. Now the server logs messages about
statements that are unsafe for statement-based logging only if
the log_warnings
variable is greater than 0.
(Bug#46265)
The undocumented TRANSACTIONAL
and
PAGE_CHECKSUM
keywords were removed from the
grammar.
(Bug#45829)
The minimum value for
table_open_cache
was increased
from 64 to 400.
(Bug#45475)
mysql_upgrade now displays a message indicating the connection parameters it uses when invoking mysqlcheck. (Bug#44638)
Previously, mysqldump would not dump the
INFORMATION_SCHEMA
database and ignored it if
it was named on the command line. Now,
mysqldump will dump
INFORMATION_SCHEMA
if it is named on the
command line. Currently, this requires that the
--skip-lock-tables
(or --skip-opt
) option be
given.
(Bug#33762)
Previously, SELECT ...
INTO OUTFILE
dumped column values without character
set conversion, which could produce data files that cannot be
imported without error if different columns used different
character sets. A consequence of this is that
mysqldump ignored the
--default-character-set
option
if the --tab
option was given
(which causes SELECT ...
INTO OUTFILE
to be used to dump data.)
INTO OUTFILE
now can be followed by a
CHARACTER SET
clause indicating the character
set to which dumped values should be converted. Also,
mysqldump adds a CHARACTER
SET
clause to the
SELECT ... INTO
OUTFILE
statement used to dump data, so that
--default-character-set
is no
longer ignored if --tab
is
given.
Other changes are that
SELECT ... INTO
OUTFILE
enforces that ENCLOSED BY
and ESCAPED BY
arguments must be a single
character, and SELECT
... INTO OUTFILE
and
LOAD DATA
INFILE
produce warnings if non-ASCII field or line
separators are specified.
(Bug#30946)
The maximum value for
max_binlog_cache_size
has been
increased from 232 – 1 to
264 – 1 (even on 32-bit
platforms), which enables transactions 4GB and larger to be
performed when binary logging is enabled.
(Bug#10206)
Pluggable storage engines now can be built for Windows.
On Linux, the performance of MySQL Server can be improved by
using a different malloc()
implementation,
developed by Google and called tcmalloc
. The
gain is noticeable with a higher number of simultaneous users.
MySQL 5.4.1 was linked against this library, which improved
performance but imposed some restrictions. As a result of these
restrictions, MySQL 5.4.2 uses a different approach:
The server is linked against the default
malloc()
provided by the respective
platform.
The user or administrator can install Google's
tcmalloc
if desired. Some distributions
provide it in a google-perftools
package
or with a similar name, or you can download it from Google
at
http://code.google.com/p/google-perftools/.
If the MySQL server is then started with an environment
variable setting like this (with the correct path name) the
server will use tcmalloc
with no other
change needed:
LD_PRELOAD=/your/local/path/to/
libtcmalloc_minimal.so
The MySQL team is considering whether to modify the start
script mysqld_safe so that it will check
whether tcmalloc
is installed and set the
variable if that shared library is found.
Feedback about this possible change is welcome!
The MySQL euckr
character set now can store
extended codes [81...FE][41..5A,61..7A,81..FE], which makes
euckr
compatible with the Microsoft
cp949
character set.
The optimizer_switch
system
variable is now available to control optimizations that can be
switched on and off. See
Section 7.2.18, “Using optimizer_switch
to Control the
Optimizer”.
Bugs fixed:
Performance:
With InnoDB
tables, MySQL used a
less-selective secondary index to avoid a filesort even if a
prefix of the primary key was much more selective.
The fix for this problem might cause other queries to run more slowly. (Bug#45828)
Performance:
InnoDB
uses random numbers to
generate dives into indexes for calculating index cardinality.
However, under certain conditions, the algorithm did not
generate random numbers, so ANALYZE
TABLE
did not update cardinality estimates properly. A
new algorithm has been introduced with better randomization
properties.
(Bug#43660)
Performance:
The table cache lock (LOCK_open
) is now an
adaptive mutex, which should improve performance in workloads
where this lock is heavily contended.
(Bug#43435)
Partitioning: Security Fix:
Accessing a table having user-defined partitioning when the
server SQL mode included
ONLY_FULL_GROUP_BY
caused the
MySQL server to crash. For example, the following sequence of
statements crashed the server:
DROP TABLE IF EXISTS t1; SET SESSION SQL_MODE='ONLY_FULL_GROUP_BY'; CREATE TABLE t1 (id INT, KEY(id)) PARTITION BY HASH(id) PARTITIONS 2;
Security Fix:
The strxnmov()
library function could write a
null byte after the end of the destination buffer.
(Bug#44834)
Security Fix: Four potential format string vulnerabilities were fixed (discovered by the Veracode code analysis). (Bug#44166)
Incompatible Change:
The server can load plugins under the control of startup
options. For example, many storage engines can be built in
pluggable form and loaded when the server starts. In the
following descriptions, plugin_name
stands for a plugin name such as innodb
.
Previously, plugin options were handled like other boolean options (see Section 4.2.3.2, “Program Option Modifiers”). That is, any of these options enabled the plugin:
--plugin_name
--plugin_name
=1 --enable-plugin_name
And these options disabled the plugin:
--plugin_name
=0 --disable-plugin_name
--skip-plugin_name
However, use of a boolean option for plugin loading did not
provide control over what to do if the plugin failed to start
properly: Should the server exit, or start with the plugin
disabled? The actual behavior has been that the server starts
with the plugin disabled, which can be problematic. For example,
if InnoDB
fails to start, existing
InnoDB
tables become inaccessible, and
attempts to create new InnoDB
tables result
in tables that use the default storage engine unless the
NO_ENGINE_SUBSTITUTION
SQL
mode has been enabled to cause an error to occur instead.
Now, there is a change in the options used to control plugin loading, such that they have a tristate format:
--
plugin_name
=OFF
Do not enable the plugin.
--
plugin_name
[=ON]
Enable the plugin. If plugin initialization fails, start the
server anyway, but with the plugin disabled. Specifying the
option as
--
without a value also enables the plugin.
plugin_name
--
plugin_name
=FORCE
Enable the plugin. If plugin initialization fails, do not start the server. In other words, force the server to run with the plugin or not at all.
The values OFF
, ON
, and
FORCE
are not case sensitive.
Suppose that CSV
and
InnoDB
have been built as pluggable storage
engines and that you want the server to load them at startup,
subject to these conditions: The server is allowed to run if
CSV
initialization fails, but must require
that InnoDB
initialization succeed. To
accomplish that, use these lines in an option file:
[mysqld] csv=ON innodb=FORCE
This change is incompatible with the previous implementation if
you used options of the form
--
or
plugin_name
=0--
,
which should be changed to
plugin_name
=1--
or
plugin_name
=OFF--
,
respectively.
plugin_name
=ON
--enable-
is still supported and is the same as
plugin_name
--
.
plugin_name
=ON--disable-
and
plugin_name
--skip-
are still supported and are the same as
plugin_name
--
.
(Bug#19027)plugin_name
=OFF
See also Bug#45336.
Important Change: Replication:
BEGIN
,
COMMIT
, and
ROLLBACK
statements are no longer affected by
--replicate-do-db
or
--replicate-ignore-db
rules.
(Bug#43263)
Important Change: Replication:
The transactional behavior of STOP
SLAVE
has changed. Formerly, it took effect
immediately, even inside a transaction; now, it waits until the
current replication event group (if any) has finished executing,
or until the user issues a
KILL QUERY
or
KILL CONNECTION
statement.
This was done in order to solve the problem encountered when
replication was stopped while a nontransactional slave was
replicating a transaction on the master. (It was impossible to
roll back a mixed-engines transaction when one of the engines
was nontransactional, which meant that the slave could not
safely re-apply any transaction that had been interrupted by
STOP SLAVE
.)
(Bug#319, Bug#38205)
See also Bug#43217.
Partitioning: Attempting to create a table using an invalid or inconsistent subpartition definition caused the server to crash. An example of such a statement is shown here:
CREATE TABLE t2 (s1 INT, s2 INT) PARTITION BY LIST (s1) SUBPARTITION BY HASH (s2) SUBPARTITIONS 1 ( PARTITION p1 VALUES IN (1), PARTITION p2 VALUES IN (2) (SUBPARTITION p3) );
Partitioning:
A failed RENAME TABLE
operation
on a table with user-defined partitioning left the table in an
unusable state, due to only some of the table files having been
renamed.
(Bug#30102)
Replication:
When a statement that changes a nontransactional table failed,
the transactional cache was flushed, causing a mismatch between
the execution and logging histories. Now we avoid flushing the
transactional cache unless a
COMMIT
or
ROLLBACK
is
issued.
(Bug#46129)
Replication:
For replication of a stored procedure that uses the
gbk
character set, the result on the master
and slave differed.
(Bug#45485)
Replication:
The internal function purge_relay_logs()
did
not propagate an error occurring in another internal function
count_relay_log_space()
.
(Bug#44115)
Replication:
Large transactions and statements could corrupt the binary log
if the size of the cache (as set by
max_binlog_cache_size
) was not
large enough to store the changes.
Now, for transactions that do not fit into the cache, the statement is not logged, and the statement generates an error instead.
For nontransactional changes that do not fit into the cache, the statement is also not logged—an incident event is logged after committing or rolling back any pending transaction, and the statement then raises an error.
If a failure occurs before the incident event is written the binary log, the slave does not stop, and the master does not report any errors.
See also Bug#37148.
Replication:
When using the MIXED
logging format, after
creating a temporary table and performing an update that
switched the logging format to ROW
, the
format switch persisted following the update. This prevented any
subsequent DDL statements on temporary tables from being written
to the binary log until the temporary table was dropped.
(Bug#43046)
See also Bug#40013.
This regression was introduced by Bug#20499.
Replication:
Statements using LIMIT
generated spurious
Statement is not safe to log in statement
format warnings in the error log, causing the log to
grow rapidly in size.
(Bug#42851)
See also Bug#46265, Bug#42415.
This regression was introduced by Bug#34768.
Replication: When using row-based logging, the length of an event for which the field metadata exceeded 255 bytes in size was incorrectly calculated. This could lead to corruption of the binary log, or cause the server to hang. (Bug#42749)
Replication: The warning Statement is not safe to log in statement format, issued in situations when it cannot be determined that a statement or other database event can be written reliably to the binary log using the statement-based format, has been changed to Statement may not be safe to log in statement format. (Bug#42415)
Replication:
The Query_log_event
used by replication to
transfer a query to the slave has been refactored.
Query_log_event
also stores and sends the
error code resulting from the execution since it, in some cases,
is necessary to execute the statement on the slave as well,
which should result in the same error code. The
Query_log_event
constructor previously worked
out for itself the error code using a complex routine, the
result of which was often set aside within the constructor
itself. This was also involved with at least 2 known bugs
relating to invalid errors, and taken as a clear sign that the
constructor was not well-designed and needed to be re-written.
(Bug#41948)
See also Bug#37145.
Replication:
When replicating many temporary tables and inserts into those
tables, executing STOP SLAVE
followed by START SLAVE
could
cause the server to crash. This appeared to be caused by
temporary tables preserving outdated thread references after the
restart.
(Bug#41725)
Replication:
If the
--log-bin-trust-function-creators
option is not enabled,
CREATE
FUNCTION
requires one of the modifiers
DETERMINISTIC
, NO SQL
, or
READS SQL DATA
. When using statement-based
mode, the execution of a stored function should follow the same
rules; however, only functions defined with
DETERMINISTIC
could actually be executed. In
addition, the wrong error was generated
(ER_BINLOG_ROW_RBR_TO_SBR instead of
ER_BINLOG_UNSAFE_ROUTINE).
Now execution of stored functions is compatible with creation in
this regard; when a stored function without one of the modifiers
above is executed in STATEMENT
mode, the
correct error is raised, and functions defined using NO
SQL
, READS SQL DATA
, or both (that
is, without using DETERMINISTIC
) can be
excuted.
(Bug#41166)
Replication: When reading a binary log that was in use by a master or that had not been properly closed (possibly due to a crash), the following message was printed: Warning: this binlog was not closed properly. Most probably mysqld crashed writing it. This message did not take into account the possibility that the file was merely in use by the master, which caused some users concern who were not aware that this could happen.
To make this clear, the original message has been replaced with Warning: this binlog is either is use or was not closed properly. (Bug#34687)
open_binary_frm()
performed a version test
incorrectly, resulting in Valgrind errors.
(Bug#46652)
Concurrent INSERT INTO
... SELECT
statements for an InnoDB
table could cause an AUTO_INCREMENT
assertion
failure.
(Bug#46650)
Incorrect index optimization could lead to incorrect results or server crashes. (Bug#46454)
The server printed warnings at startup about adjusting the value
of the max_join_size
system
variable. (These were harmless, but might be seen by users as
significant.)
(Bug#46385)
mysql did not handle backspace properly for
multi-byte characters. This has been fixed now if
mysql is linked with the
readline
library. It is not fixed if
mysql
is linked with
libedit
, which does not contain the necessary
support for multi-byte character sets.
(Bug#46310)
For InnoDB
tables, an unnecessary table
rebuild for ALTER TABLE
could
sometimes occur if ROW_FORMAT
was specified.
(Bug#46160)
The server crashed if evaluation of
GROUP_CONCAT(... ORDER BY)
required allocation of a sort buffer but allocation failed.
(Bug#46080)
An optimization that moved an item from a subquery to an outer query could cause a server crash. (Bug#46051)
Several Valgrind warnings were corrected. (Bug#46003, Bug#46034, Bug#46042)
CREATE TABLE ...
SELECT
could cause a server crash if no default
database was selected.
(Bug#45998)
When creating tables using the IBMDB2I
storage engine with the
ibmdb2i_create_index_option
option set to 1,
creating an IBMDB2I
table with a primary key
should produce an additional index that uses EBCDIC hexadecimal
sorting, but this index was not created.
(Bug#45983)
The server crashed for attempts to use
REPLACE
or
INSERT ... ON DUPLICATE
KEY UPDATE
with a view defined using a join.
(Bug#45806)
Some collations were causing IBMDB2I
to
report inaccurate key range estimations to the optimizer for
LIKE
clauses that select substrings. This can
be seen by running EXPLAIN
. This
problem primarily affects multi-byte and unicode character sets.
(Bug#45803)
The MySQL Server crashed when performing a
REPLACE
into a MERGE
table
if there was a duplicate.
(Bug#45800)
Inserting data into a table using the macce
character set with the IBMDB2I
storage engine
would fail.
(Bug#45793)
For problems reading SSL files during SSL initialization, the
server wrote error messages to stderr
rather
than to the error log.
(Bug#45770)
There was a race condition when changing
innodb_commit_concurrency
at
runtime to the value DEFAULT
.
(Bug#45749)
See also Bug#42101.
Performing an empty XA transaction caused the server to crash for the next XA transaction. (Bug#45548)
The vendor name change from MySQL AB to Sun Microsystems, Inc. in RPM packages was not handled gracefully when upgrading MySQL using an RPM package. (Bug#45534)
SHOW CREATE TRIGGER
requires the
TRIGGER
privilege but was not
checking privileges.
(Bug#45412)
An assertion failure could occur if InnoDB
tried to unlock a record when the clustered index record was
unknown.
(Bug#45357)
Linker failures with libmysqld
on VC++ 2008
were fixed.
(Bug#45326)
If autocommit
was enabled,
InnoDB
did not roll back
DELETE
or
UPDATE
statements if the
statement was killed.
(Bug#45309)
Compiler warnings on Mac OS X were fixed. (Bug#45286)
The optimizer mishandled “impossible range” conditions and returned empty results due to an uninitialized variable. (Bug#45266)
Use of DECIMAL
constants with
more than 65 digits in
CREATE TABLE ...
SELECT
statements led to spurious errors or assertion
failures.
(Bug#45262)
The mysql client could misinterpret some character sequences as commands under some circumstances. (Bug#45236)
Running a SELECT
query over an
IBMDB2I
table using the
cp1250
character set would produce an error
ibmdb2i error 2027: Error converting single-byte sort sequence to UCS-2
Use of CONVERT()
with an empty
SET
value could cause an
assertion failure.
(Bug#45168)
Use of ROUND()
on a
LONGTEXT
or
LONGBLOB
column of a derived
table could cause a server crash.
(Bug#45152)
A problem of compiler register misallocation on 32-bit Linux was corrected. (Bug#45131)
DROP USER
could fail to drop all
privileges for an account if the
PAD_CHAR_TO_FULL_LENGTH
SQL
mode was enabled.
(Bug#45100)
InnoDB
recovery could hang due to redo
logging of doublewrite buffer pages.
(Bug#45097)
Invalid memory reads could occur using the compressed client/server protocol. (Bug#45031)
Invalid input could cause invalid memory reads by the parser. (Bug#45010)
GROUP BY
on a constant
(single-row) InnoDB
table joined to other
tables caused a server crash.
(Bug#44886)
ALTER TABLE
on a view crashed the
server.
(Bug#44860)
When using partitioning with the IBMDB2I
storage engine, the engine could report that a valid character
set was not supported.
(Bug#44856)
Running queries on tables with the IBMDB2I
storage engine using the utf8
character would
fail when using the 64-bit version of MySQL.
(Bug#44811)
Index Merge followed by a filesort could result in a server
crash if sort_buffer_size
was
not large enough for all sort keys.
(Bug#44810)
See also Bug#40974.
UNCOMPRESSED_LENGTH()
returned a
garbage result when passed a string shorter than 5 bytes. Now
UNCOMPRESSED_LENGTH()
returns
NULL
and generates a warning.
(Bug#44796)
Several Valgrind warnings were silenced. (Bug#44774, Bug#44792)
Selecting
RAND(
function where N
)N
is a column of a
constant
table (table with a single row)
failed with a SIGFPE
signal.
(Bug#44768)
The PASSWORD()
and
OLD_PASSWORD()
functions could
read memory outside of an internal buffer when used with
BLOB
arguments.
(Bug#44767)
Conversion of a string to a different character set could use the same buffer for input and output, leading to incorrect results or warnings. (Bug#44743, Bug#44766)
When reading binary data, the concatenation function for geometry data collections did not rigorously check for available data, leading to invalid reads and server crashes. (Bug#44684)
Some deprecation warning messages indicated feature removal in MySQL 5.2 rather than MySQL 6.0. (Bug#44676)
Code that optimized a read-only XA transaction failed to reset the XID once the transaction was no longer active. (Bug#44672)
During incorporation of a Google patch to
SHOW ENGINE INNODB
STATUS
in MySQL 5.4.0, the
TRANSACTIONS
section of the output was
inadvertently omitted. This section has been restored.
(Bug#44671)
A Valgrind warning related to transaction processing was silenced. (Bug#44664)
If an error occurred during the creation of a table (for
example, the table already existed) having an
AUTO_INCREMENT
column and a
BEFORE
trigger that used the
INSERT ...
SELECT
construct, an internal flag was not reset
properly. This led to a crash the next time the table was opened
again.
(Bug#44653)
Some files in an AIX tar file distribution unpacked with incorrect permissions. (Bug#44647)
When creating tables using the IBMDB2I
storage engine, the RCDFMT
(record format)
that would be applied to the corresponding files within the IBM
i would be set according to the table name. During whole table
operations, the name could get modified to a value inconsistent
with the table name. In addition, the record format would be
inconsistent compared to the file content. The
IBMDB2I
storage engine now adds an explicit
RCDFMT
clause to the CREATE
TABLE
statement passed down to the DB2 storage engine
layer.
(Bug#44610)
Using mysql_stmt_execute()
to
call a stored procedure could cause a server crash.
(Bug#44495)
innochecksum could incorrectly determine the input file name from the arguments. (Bug#44484)
The my-innodb-heavy-4G.cnf
sample option
file contained a setting for the no longer existing
innodb_file_io_threads
system
variable. This has been replaced with settings for the
innodb_write_io_threads
and
innodb_read_io_threads
system
variables with which
innodb_file_io_threads
has been
replaced.
(Bug#44470)
Creating a new instance after previously removing an instance would fail to complete the installation properly because the security settings could not be applied correctly. (Bug#44428)
Incorrect time was reported at the end of mysqldump output. (Bug#44424)
mysqlslap ignored the
--csv
option if it was given
without an argument.
(Bug#44412)
Caching of GROUP BY
expressions could lead to
mismatches between compile-time and runtime calculations and
cause a server crash.
(Bug#44399)
A deprecation warning message tested for an incorrect version number and caused an assertion failure. (Bug#44394)
Lettercase conversion in multibyte cp932
or
sjis
character sequences could produce
incorrect results.
(Bug#44352)
Assertion failure could occur for duplicate-key errors in
INSERT INTO ...
SELECT
statements.
(Bug#44306)
Incomplete cleanup of JOIN_TAB::select
during
the filesort of rows for a GROUP BY
clause
inside a subquery caused a server crash.
(Bug#44290)
Trying to use an unsupported character set on an
IBMDB2I
table would produce DB2 error 2501 or
2511. The error has been updated to produce Error 2504
(Character set is unsupported).
(Bug#44232)
For InnoDB
tables with
ROW_FORMAT = REDUNDANT
,
CHAR
columns should be
fixed-length and allow in-place updates. However, they were
treated as variable-length if they contained
utf8
data or NULL
,
preventing in-place updates.
(Bug#44032)
InnoDB
use of SELECT
MAX(
could
cause a crash when MySQL data dictionaries went out of sync.
(Bug#44030)autoinc_column
)
In some circumstances, when a table is created with the
IBMDB2I
engine, the CREATE
TABLE
statement will return successfully but the table
will not exist.
(Bug#44022)
On 64-bit Windows systems, myisamchk did not
handle key_buffer_size
values larger than
4GB.
(Bug#43940)
For user-defined utf8
collations, attempts to
store values too long for a column could cause a server crash.
(Bug#43827)
Invalidation of query cache entries due to table modifications could cause threads to hang inside the query cache with state “freeing items”. (Bug#43758)
EXPLAIN
EXTENDED
could crash for
UNION
queries in which the last
SELECT
was not parenthesized and
included an ORDER BY
clause.
(Bug#43612)
Enabling the event scheduler from within the file specified by
--init-file
caused a server
crash.
(Bug#43587)
Multiple-table updates for InnoDB
tables
could produce unexpected results.
(Bug#43580)
The server did not always check the return value of calls to the
hash_init()
function.
(Bug#43572)
If the client lost the connection to the MySQL server after
mysql_stmt_prepare()
, the first
call to mysql_stmt_execute()
returned an error (as expected) but consecutive calls to
mysql_stmt_execute()
or
mysql_stmt_close()
crashed the
client.
(Bug#43560)
For InnoDB
tables, overflow in an
AUTO_INCREMENT
column could cause a server
crash.
(Bug#43203)
For DELETE
statements with ORDER BY
, where
var
var
was a global system variable with
a NULL
value, the server could crash.
(Bug#42778)
configure.in
contained references to
literal instances of nm and
libc
, rather than to variables parameterized
for the proper values on the current platform.
(Bug#42721)
For InnoDB
tables, spurious duplicate-key
errors could occur when inserting into an
AUTO_INCREMENT
column.
(Bug#42714)
mysqladmin --count=X
--sleep=Y
incorrectly
delayed Y
seconds after the last
iteration before exiting.
(Bug#42639)
configure.in
did not properly check for the
pthread_setschedprio()
function.
(Bug#42599)
For InnoDB
tables, inserting into
floating-point AUTO_INCREMENT
columns failed.
(Bug#42400)
Builds linked against OpenSSL had a memory leak in association with use of X509 certificates. (Bug#42158)
There was a race condition when changing
innodb_commit_concurrency
at
runtime from zero to nonzero or from nonzero to zero. Now this
variable cannot be changed at runtime from zero to nonzero or
vice versa. The value can still be changed from one nonzero
value to another.
(Bug#42101)
See also Bug#45749.
SELECT ... INTO
@var
could produce values different from
SELECT ...
without the INTO
clause.
(Bug#42009)
A workaround for a Sun Studio bug was instituted. (Bug#41710)
A crash occurred due to a race condition between the merge table
and table_cache
evictions.
00000001403C452F mysqld.exe!memcpy()[memcpy.asm:151] 00000001402A275F mysqld.exe!ha_myisammrg::info()[ha_myisammrg.cc:854] 00000001402A2471 mysqld.exe!ha_myisammrg::attach_children()[ha_myisammrg.cc:488] 00000001402A2788 mysqld.exe!ha_myisammrg::extra()[ha_myisammrg.cc:863] 000000014015FC5D mysqld.exe!attach_merge_children()[sql_base.cc:4135] 000000014016A4C1 mysqld.exe!open_tables()[sql_base.cc:4697] 000000014016A898 mysqld.exe!open_and_lock_tables_derived()[sql_base.cc:4956] 000000014018BB54 mysqld.exe!mysql_insert()[sql_insert.cc:613] 000000014019EDD3 mysqld.exe!mysql_execute_command()[sql_parse.cc:3066] 00000001401A2F06 mysqld.exe!mysql_parse()[sql_parse.cc:5791] 00000001401A3C1A mysqld.exe!dispatch_command()[sql_parse.cc:1202] 00000001401A4CD7 mysqld.exe!do_command()[sql_parse.cc:857] 0000000140246327 mysqld.exe!handle_one_connection()[sql_connect.cc:1115] 00000001402B82C5 mysqld.exe!pthread_start()[my_winthread.c:85] 00000001403CAC37 mysqld.exe!_callthreadstart()[thread.c:295] 00000001403CAD05 mysqld.exe!_threadstart()[thread.c:275] 0000000077D6B69A kernel32.dll!BaseThreadStart() Trying to get some variables. Some pointers may be invalid and cause the dump to abort...
Shared-memory connections did not work in Vista if mysqld was started from the command line. (Bug#41190)
For queries with a sufficient number of subqueries in the
FROM
clause of this form:
SELECT * FROM (SELECT 1) AS t1, (SELECT 2) AS t2, (SELECT 3) AS t3, ...
The query failed with a Too high level of nesting for
select
error, as though the query had this form:
SELECT * FROM (SELECT 1 FROM (SELECT 2 FROM (SELECT 3 FROM ...
For views created with a column list clause, column aliases were
not substituted when selecting through the view using a
HAVING
clause.
(Bug#40825)
Some UPDATE
statements that
affected no rows returned a rows-affected count of one.
(Bug#40565)
mysqladmin did not have enough space
allocated for tracking all variables when using
--vertical
or
--relative
with
extended-status
.
(Bug#40395)
Partitioning a log table caused a server crash. (Bug#40281)
When using quick access methods to search for rows in
UPDATE
and DELETE
statements, there was no check whether a fatal error had already
been sent to the client while evaluating the quick condition.
Consequently, a false OK (following the error) was sent to the
client, causing the error to be incorrectly transformed into a
warning.
(Bug#40113)
A multiple-table DELETE
involving
a table self-join could cause a server crash.
(Bug#39918)
Creating an InnoDB
table with a comment
containing a '#'
character caused foreign key
constraints to be omitted.
(Bug#39793)
ALTER TABLE
neglected to preserve
ROW_FORMAT
information from the original
table, which could cause subsequent ALTER
TABLE
and OPTIMIZE
TABLE
statements to lose the row format for
InnoDB
tables.
(Bug#39200)
The mysql option
--ignore-spaces
was nonfunctional.
(Bug#39101)
The functions listed in Section 11.17.4.2.3, “Creating Geometry Values Using MySQL-Specific Functions”, previously accepted WKB arguments and returned WKB values. They now accept WKB or geometry arguments and return geometry values.
The functions listed in Section 11.17.4.2.2, “Creating Geometry Values Using WKB Functions”, previously accepted WKB arguments and returned geometry values. They now accept WKB or geometry arguments and return geometry values. (Bug#38990)
SHOW PROCESSLIST
could access freed memory of
a stored procedure run in a concurrent session.
(Bug#38816)
During installation on Windows, the MySQL Instance Configuration Wizard window could be opened at a size too small to be usable. (Bug#38723)
make_binary_distribution did not always generate correct distribution names. (Bug#37808)
The server crashed when executing a prepared statement
containing a duplicated MATCH()
function call
in the select list and ORDER BY
clause; for
example, SELECT MATCH(a) AGAINST('test') FROM t1 ORDER
BY MATCH(a) AGAINST('test')
.
(Bug#37740)
The output of mysqldump --tab for views
included a DROP TABLE
statement
without the IF EXISTS
qualifier.
(Bug#37377)
If a query was such as to produce the error 1054
Unknown column '...' in 'field list'
, using
EXPLAIN
EXTENDED
with the query could cause a server crash.
(Bug#37362)
In the mysql client, if the server connection
was lost during repeated status
commands, the
client would fail to detect this and command output would be
inconsistent.
(Bug#37274)
In the mysql client, using a default
character set of binary
caused internal
commands such as DELIMITER
to become case
sensitive.
(Bug#37268)
A Valgrind error during subquery execution was corrected. (Bug#36995)
When invoked to start multiple server instances, mysqld_multi sometimes would fail to start them all due to not changing location into the base directory for each instance. (Bug#36654)
mysql_upgrade silently ignored the
--basedir
and
--datadir
options, which
it accepts for backward compatibility. Now it prints a warning.
(Bug#36558)
For InnoDB
tables, poor cardinality
statistics could result in poor query execution plans.
(Bug#36513)
mysqldump --tab dumped triggers to
stdout
rather than to the
.sql
file for the corresponding table.
(Bug#34861)
If the MYSQL_HISTFILE
environment variable
was set to /dev/null
, the
mysql client overwrote the
/dev/null
device file as a normal file.
(Bug#34224)
Rows written to the slow query log could have an indeterminate
Rows_examined
value due to improper
initialization.
(Bug#34002)
mysqld_safe mishandled certain parameters if they contained spaces. (Bug#33685)
mysqlimport was not always compiled correctly
to enable thread support, which is required for the
--use-threads
option.
(Bug#32991)
mysqladmin kill did not work for thread IDs larger than 32 bits. (Bug#32457)
mysqlcheck failed to fix table names when the
--fix-table-names
and
--all-in-1
options were both
specified.
(Bug#31821)
If the MySQL server was killed without the PID file being removed, attempts to stop the server with mysql.server stop waited 900 seconds before giving up. (Bug#31785)
When performing an installation on Windows using the GUI
installer, the installer would fail to wait long enough during
installation for the MySQL service to be installed, which would
cause the installation to fail and may cause security settings,
such as the root
password to not be applied
correctly.
(Bug#30525)
mysql included extra spaces at the end of some result set lines. (Bug#29622)
Several client programs failed to interpret
--skip-password
as “send no password.”
(Bug#28479)
The mysql client inconsistently handled NUL bytes in column data in various output formats. (Bug#28203)
mysqlimport did not correctly quote and escape table identifiers and file names. (Bug#28071)
Output from mysql --html did not encode the
<
, >
, or
&
characters.
(Bug#27884)
If the mysql client was built with the
readline
library and the
.inputrc
file mapped
Space
to the magic-space
function, it became impossible to enter spaces.
(Bug#27439)
mysql_convert_table_format did not prevent
conversion of tables to MEMORY
or
BLACKHOLE
tables, which could result in data
loss.
(Bug#27149)
Renaming a column that appeared in a foreign key definition did not update the foreign key definition with the new column name. (Bug#21704)
If InnoDB
reached its limit on the number of
concurrent transactions (1023), it wrote a descriptive message
to the error log but returned a misleading error message to the
client, or an assertion failure occurred.
(Bug#18828)
See also Bug#46672.
Release availability:
This release does not differ from 5.4.0 except that binary distributions are available for all MySQL-supported platforms, including Windows binaries with scalability improvements enabled. We expect that the scalability improvements will also benefit users of 64-bit Mac OS X and FreeBSD as well as 64-bit Linux/Solaris/SPARC, and potentially also users of 32-bit versions of these platforms.
Release availability:
MySQL 5.4 is based on MySQL 5.1 but includes small, high-impact changes to enhance scalability and performance in MySQL Server. For details, see Section 1.5, “What Is New in MySQL 5.4”.
Binary MySQL 5.4.0 distributions are available as 64-bit builds for Solaris 10-x86_64, Solaris10-SPARC, and Linux x86_64-glibc23.
If you use a source distribution, the
BUILD/build_mccge.sh script can be used to
configure and build MySQL 5.4.0. Run this script with the
--help
option to see the available options.
Functionality added or changed:
Incompatible Change:
The following InnoDB
system
variable changes were made:
innodb_file_io_threads
:
Removed (replaced by
innodb_read_io_threads
and
innodb_write_io_threads
).
If you upgrade from MySQL 5.1 from MySQL 5.4 and previously
explicitly set
innodb_file_io_threads
at
server startup, you must change your configuration.
innodb_read_io_threads
and
innodb_write_io_threads
can
be used instead.
innodb_read_io_threads
and
innodb_write_io_threads
:
Default changed from 1 to 8.
innodb_buffer_pool_size
:
Default increased from 8 MB to 1GB. Minimum increased from
1MB to 64MB.
innodb_additional_mem_pool_size
:
Default increased from 1MB to 8MB. Minimum increased from
512KB to 2MB.
innodb_max_dirty_pages_pct
:
Default decreased from 90 to 75. Maximum decreased from 100
to 99 to never allow a completely dirty buffer pool.
innodb_log_buffer_size
:
Default increased from 1MB to 16MB. Minimum increased from
256KB to 2MB.
innodb_log_file_size
:
Default increased from 5MB to 128MB. Minimum increased from
1MB to 32MB.
innodb_log_files_in_group
:
Default increased from 2 to 3.
innodb_io_capacity
: Default
increased from 100 to 200.
innodb_autoextend_increment
:
Default increased from 8MB to 64MB.
Incompatible Change:
If you upgrade to MySQL 5.4.0 from MySQL 5.1, the server may
fail to start due to InnoDB
log
file configuration changes. MySQL 5.4.0 increases the default
value of
innodb_log_files_in_group
from
2 to 3. It also increases the default value of
innodb_log_file_size
from 5MB
to 128MB and the minimum value of
innodb_log_file_size
from 1MB
to 32MB.
For an upgrade, it is necessary to account for these changes. To
do so, discard the old InnoDB
log
files and let MySQL 5.4.0 create new ones. It is necessary to
shut down your current server cleanly so that no outstanding
transaction information remains in the log. The procedure to use
depends on the value of
innodb_fast_shutdown
used in
your current server:
If innodb_fast_shutdown
is
not set to 2: Stop your current MySQL server and make sure
that it shuts down without errors (to ensure that there is
no information for outstanding transactions in the log).
Copy the old log files into a safe place in case something
went wrong during the shutdown and you need them to recover
the tablespace. Delete the old log files and edit
my.cnf
if necessary to specify the
desired log file configuration. Then upgrade to MySQL 5.4.0
and start the new server. mysqld sees
that no InnoDB
log files exist
at startup and creates new ones.
If innodb_fast_shutdown
is
set to 2: Shut down your current server, set
innodb_fast_shutdown
to 1,
and restart the server. The server should be allowed to
recover. Then you should shut down the server again and
follow the procedure described in the preceding item to
change InnoDB
log file size.
Set innodb_fast_shutdown
back to 2 and start the MySQL 5.4.0 server.
The Instance Manager (mysqlmanager) has been discontinued and is no longer provided in MySQL releases.
Bugs fixed:
Performance:
The server unnecessarily acquired a query cache mutex even with
the query cache disabled, resulting in a small performance
decrement which could show up as threads often in state
“invalidating query cache entries (table)”,
particularly on a replication slave with row-based replication.
Now if the server is started with
query_cache_type
set to 0, it does not
acquire the query cache mutex. This has the implication that the
query cache cannot be enabled at runtime.
(Bug#38551)
Important Change:
When using the MySQL Instance Configuration Wizard with a
configuration where you already have an existing installation
with a custom datadir
, the wizard could reset
the data to the default data directory. When performing an
upgrade installation in this situation, you must re-specify your
custom settings, including the datadir
, to
ensure that your configuration file is not reset to the default
values.
(Bug#37534)
Important Change:
Uninstalling MySQL using the MySQL installer on Windows would
delete the my.ini
file. The file is no longer
deleted. In addition, when a new installation is conducted, any
existing cofiguration file will be renamed to
myDATETIME.ini.bak
during configuration.
(Bug#36493)
Important Change: When installing MySQL on Windows, it was possible to install multiple editions (Complete, and Essential, for example) of the same version of MySQL, leading to two separate entries in the installed packages which were impossible to isolate. This could lead to problems with installation and uninstallation. The MySQL installer on Windows no longers allow multiple installations of the same version of MySQL on a single machine. (Bug#4217)
The MySQL Instance Configuration Wizard would fail to start correctly on Windows Vista. (Bug#42386)
When running the MySQL Instance Configuration Wizard in
command-line only mode, the service name would be ignored
(effectively creating all instances with the default
MySQL
service name), irrespective of the name
specified on the command line. However, the wizard would attempt
to start the service with the specified name, and would fail.
(Bug#38379)
When using the MySQL MSI Installer on Windows and selecting Bug#37294)
after a choosing Repair, you would be returned to the Fresh Install section of the installer. You are now correctly returned to the Install, Repair, Modify screen. (This appendix lists the changes to the MySQL Enterprise Monitor, beginning with the most recent release. Each release section covers added or changed functionality, bug fixes, and known issues, if applicable. All bug fixes are referenced by bug number and include a link to the bug database. Bugs are listed in order of resolution. To find a bug quickly, search by bug number.
This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.1.1.
Bugs fixed:
Security Fix: A number of cross-site request forging issues have been identified and resolved. (Bug#52888, Bug#52910, Bug#52905, Bug#52897)
MySQL Enterprise Service Manager would crash during initial startup on Solaris SPARC 64-bit. (Bug#53751)
The MySQL Enterprise Monitor Agent could report data using an old timestamp, or report information for a server that the MySQL Enterprise Monitor Agent can no longer connect to due to a permissions change. (Bug#52839)
The dialog box during installation of MySQL Enterprise Service Manager has been updated to make the process of installing MySQL Enterprise Service Manager when using an existing MySQL server. (Bug#52839)
Scheduling a rule against an instance, and then deleting that
instance, would retain the instance within MySQL Enterprise Dashboard,
identified as Unknown
.
(Bug#51095)
Deleting a server within MySQL Enterprise Dashboard could cause a
foreign key constraint
error.
(Bug#50927)
Deleting a server that had purged all its monitoring data, but still have query analyzer information, would fail. (Bug#50916)
The SSL certificates supplied with MySQL Enterprise Service Manager have been updated.
The certificate shipped with MySQL Enterprise Service Manager is an example certificate that expires after 1 year and that folks should create their own and back it up between MEM service manager updates. For more information on updating the certificate, see Section 15.12.4, “Creating a new SSL KeyStore”. (Bug#50694)
Clicking on a link to a support issue within the dashboard is now configured to open the issue within a new window. (Bug#50651)
Monitoring of a server that had
INFORMATION_SCHEMA
, and a large number of
schemas and/or tables could upset the gathering of monitoring
data.
(Bug#47947)
If you specify an invalid backend proxy address to MySQL Enterprise Monitor Agent, the agent would fail silently. (Bug#46927)
Installation on certain platforms could fail during the generation of a UUID because of a lack of privileges. A separate UUID generation tool, agent-generate-uuid is now used to create the UUID. (Bug#46370)
If a customer was using their own SSL certificate, they entered
that information in the server.xml
file.
However, running the upgrade installer caused
server.xml
, and any custom certificates, to
be replaced.
(Bug#44525)
Starting the agent could lead to an error regarding the
ssh-keygen tool and a missing library
(libcrypto
).
(Bug#43125)
This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.1.0.
Functionality added or changed:
The smallest purge log time interval that could be set in the Dashboard was one week. MySQL Enterprise Monitor was changed to allow setting the smallest purge log time interval to one day. (Bug#46822)
Certain heat chart rules cannot be unscheduled or disabled, this is because they are required for correct operation of MySQL Enterprise Monitor. Should an attempt be made to unschedule or disable one of these heat chart rules, a suitable message is now displayed, explaining this requirement. (Bug#46535)
If you are monitoring one instance of MySQL server mysqld and then upgrade that MySQL server, the correct version of the MySQL server is not displayed in the Dashboard. The agent will now perform a re-synchronization of the inventory if it identifies that the server has gone away and that the monitored MySQL has been upgraded. (Bug#38409)
Bugs fixed:
The MySQL Enterprise Monitor Agent could fail to reconnect to a monitored MySQL instance if the agent was started while the MySQL instance was unavailable. (Bug#50797)
When installing MySQL Enterprise Monitor Agent on a Linux operating system using
the SELinux security environment, the installation would fail if
the allow_execstack
option had been enabled.
(Bug#50515)
It was possible to updated an existing email notification list with two email addresses in the destination without a required comma between the addresses. Addresses are now validated during the editing phase to ensure that this does not occur. (Bug#50161)
The agent could not be installed on Mac OS X Snow Leopard (10.6) due to an incompatibility in the XML libraries used. (Bug#50126)
Deleting users within MySQL Enterprise Service Manager could lead to errors in the repository database that would affect further operations involving the deleted user. (Bug#49896)
When creating a new instance by copying an existing agent
configuration, it is possible to create an orphaned agent. The
recommended advice is to TRUNCATE
the
mysql.inventory
table. However, doing this
could lead to additional errors and an exception when the
scheduled data updates on the now orphaned agent are executed.
(Bug#49882)
Monitoring a MySQL 4.0 server would fail because MySQL 4.0 did not support table-level character set support. (Bug#49082)
The agent installer for Solaris on x64 would fail due to a library linker issue duing the post-installation phase of the installer. (Bug#48336)
Support has been added for SNMPv2 traps in addition to the existing SNMPv1 traps. You can configure the version to use for SNMP traps, see ???.
In addition, support has also been added to send SNMP notifications to two hosts in place of just one host. Notifications are sent to both hosts simultaneously. (Bug#47686, Bug#48955)
Support issues can have a Severity from S1 through S4, but can also have a value of “NS” meaning “No Severity Set”. MySQL Enterprise Monitor was not able to parse this, which resulted in errors such as the following:
2009-09-23 13:53:51,812 ERROR [em-worker-pool-thread-6:monitor.support.DevSpPoller] error consuming successful response java.lang.IllegalArgumentException: No enum const class com.mysql.etools.monitor.support.SpIssue$Severity.NS at java.lang.Enum.valueOf(Enum.java:196) ...
The pagination of errors within MySQL Enterprise Dashboard for MySQL Enterprise Service Manager logging made it difficult to identify the true source of the error. (Bug#47464)
An additional link has been added to the Configure What's New page to link to the relevant documentation. (Bug#47256)
MySQL Enterprise Monitor would fail to install on Miracle Linux4. (Bug#47209)
Some strings in the What's New tab of MySQL Enterprise Dashboard had not been translated from English to Japanese. (Bug#47203)
The diagnostic report file has been updated so that the filename of the report includes the timestamp when the report was generated. (Bug#47164)
When the Configuring and troubleshooting this feed link was clicked it opened the help screen in the current browser window, rather than in a new window.
The link can be found on the What's New tab, at the bottom of the Important Product-Related Announcements section, in the Welcome to the "What's New?" Live Feed! sub-section. (Bug#47145)
The links for further information on the What's New feed were invalid. (Bug#47133)
When the Help link was clicked in the Dashboard, the following script error was generated:
row: 32 char: 5 error: object expected code: 0 URL: http://xxx.yyy.com:38080/Help.action
This only happened when using Internet Explorer. (Bug#47065)
The times used for queries in Query Analyzer would not match the time set for the user's timezone and browser setting. (Bug#47040)
The date format in the configure what's new popup on the What's New? tab did not reflect the locale set in the User Preferences page. (Bug#46901)
Two links in the Agent installer were incorrect.
The link https://enterprise.mysql.com/docs/monitor/2.0/en/mem-install.html#mem-agent-rights should have pointed to https://enterprise.mysql.com/docs/monitor/2.1/en/mem-install.html#mem-agent-rights. Also, the link https://enterprise.mysql.com/docs/monitor/2.1/en/mem-query-analysis.html should have pointed to https://enterprise.mysql.com/docs/monitor/2.1/en/mem-query-analyzer.html. (Bug#46812)
The REPLACE
and CALL
statments did not show a rows graph within the statement popup
graph tab.
(Bug#46796)
When updating your scription after the subscription has expired, the ability to update your advisor bundle was not available. (Bug#46700)
The task message for a given server within the agent would be logged at the incorrect level. Messages are now logged at the message level. (Bug#46681)
Pressing cancel on a popup would cause a page reload, instead of just closing the popup window. (Bug#46604)
The cry for help email included a stack trace, however it was displayed on a single line without any line breaks. (Bug#46458)
If the Last link was clicked on the Infrastructure logs page, the following error was generated:
Error Message fromIndex(400) > toIndex(31)
When using MySQL Enterprise Monitor Agent, if the current configured time went backwards (for example during time correction), then the MySQL Enterprise Monitor Agent would stop reporting data and induce a high load on the machine running MySQL Enterprise Monitor Agent (Bug#46052)
The Windows installers for MySQL Enterprise Service Manager did not include 64-bit versions of the various binary tools. (Bug#45682)
The agent could get into a state where it loop through the resynchronization of the core data, without reporting information to the service manager, causing gaps in the data. (Bug#45382)
The IP address of the agent host on FreeBSD 7 systems would not be reported correctly. (Bug#45079)
This section documents all changes and bug fixes that have been applied since the release of MySQL Enterprise Monitor, version 2.0.6.
Functionality added or changed:
Incompatible Change: The default proxy port used to relay queries when using the Query Analyzer has been changed from port 4040 to 6446.
The Agent did not write its version number to the log on startup or shutdown.
The information is now available by setting log level
“MESSAGE” in the Dashboard. It is also available
when running the Agent from the command line with the command
mysql-monitor-agent
--version
. The Agent also now logs
its version number on startup if the log level is set to
“CRITICAL”.
(Bug#45884)
The Agent did not have a configurable response size.
The response size was hard coded to 65K. However, with large inventories, the customer might need to use a larger response size.
The Agent command line option
--agent-max-response-size
was added which will
set the maximum size (in bytes) of the response the agent will
send to the Service Manager. The default is 65536.
(Bug#45571)
If the Service Manager lost connection to the repository server,
it would shut down after 50 attempts to reconnect or if it was
unable to reconnect within 180 seconds. This behavior has now
been made configurable through parameters in the
config.properties
file. The parameters are:
mysql.max_connect_retries
- default is
50.
mysql.max_connect_timeout_msec
- default
is 180 seconds.
There was no way to force the Agent to resynch with the Service Manager. A link has now been added. The link can be found on the Settings, Manage Servers page - click the context menu next to a server, the menu now contains a Refresh item. (Bug#45461)
When the Agent debug log was examined, it was found to contain XML returned by the Service Manager that did not contain carriage returns. This made the data difficult to read by a human. The Service Manager has been changed to return formatted XML. (Bug#45460)
The version of Enterprise Monitor was not logged on startup.
Enterprise Monitor was changed to log the Monitor and Advisor version number on startup. See also Bug#45884. (Bug#45459)
The ability to customize the text of the email sent for an event was added. The URL to the event can now be added to the email, so that the administrator does not have to search for the action that triggered the email. (Bug#44383)
In large installations it can be desirable to locate the
repository MySQL Server and the Tomcat server on difference
computers to reduce load. However, the script
mysqlmonitorctl.sh
assumed these were
running on the same server.
The script was therefore changed to accommodate the above requirement.
The mysqlmonitorctl.sh
script now checks
for a new configuration file called
mysqlmonitorctl.conf
. This configuration
file is located in a new directory,
etc/defaults
, relative to the install
directory. The configuration file contains 2 variables:
START_MYSQL=yes
START_TOMCAT=yes
The script will then start/stop the MySQL Server and Tomcat accordingly. Defaults for both variables in the file are set to “yes”. The update installers will not overwrite this file. (Bug#44379)
When Replication was configured to use SSL for encrypting the transfer of the binary log, even though replication worked and the dashboard displayed the replication group correctly, the agent still logged the following message (repeatedly):
2009-04-06 16:12:00: (critical) job_collect_mysql.c:698: [mysql] (master-uuid) mysql_real_connect(hostname:port replication:...) to the slave's master failed: Access denied for user 'replication'@'hostname' (using password: YES) (1045)
It was not possible to keep logs for a specific period of more than 52 weeks. The value for purging logs could be set in Settings, Global Settings to values ranging from “Never” to “52 Weeks” using the drop down list boxes.
The interface has now been changed to additionally offer periods of 18 months and 24 months. (Bug#43793)
Events used a GMT timestamp for the event time within email notifications, rather than the local time for the server generating the event.
MySQL Enterprise Monitor has been changed so that it displays the time using the server's locale and GMT. (Bug#43739)
MySQL Enterprise Monitor did not include a graph to show
max_used_connections
versus
max_connections
.
This has now been included with the Silver level advisor bundle. (Bug#43583)
A rule has been added named “Server Restarted” to signal a server restart. This has been added as a Heat Chart advisor to the Silver level advisor bundle. The rule has the following options:
Expression: (%Uptime% < THRESHOLD) Critical Alert: 600 Warning Alert: 600 Info Alert: 600 Variable: %Uptime% Data Item: mysql.status:Uptime Instance: local Default frequency: 5 minutes
In the Enterprise Dashboard, it was possible to change the last
remaining user with a manager role to having an agent role. This
led to a problem whereby when attempting to subsequently login
to the Dashboard, this caused redirection to the
setup.action
page which presents the Create
Administrator facility. However, there was no
button on this page, so it was
not possible to create the administrative account.
The Dashboard has now been changed so that the currently logged in user is not able to change their role. (Bug#42436)
Certain alerts were misleadingly labelled as CRITICAL, and caused people to change settings unnecessarily, thereby adversely affecting their system performace and functionality.
MySQL Enterprise Monitor was changed as follows:
Heat Chart Advisor
MyISAM Key Cache Has Sub-Optimal Hit Rate. Critical threshold removed, Warning set to 75 and Info set to 85.
Query Cache Has Sub-Optimal Hit Rate. Critical threshold removed, Warning set to 40 and Info set to 50.
Temporary Tables To Disk Ratio Excessive. Critical threshold removed, others left unchanged.
Memory Usage Advisor
InnoDB Buffer Cache Has Sub-Optimal Hit Rate. Critical threshold removed, others left unchanged.
Key Buffer Size May Not Be Optimal For Key Cache. Critical threshold removed, others left unchanged.
Key Buffer Size May Not Be Optimal For System RAM. Critical threshold removed, others left unchanged.
Table Cache Not Optimal. Critical threshold removed, Warning set to 60 and Info set to 40.
Thread Cache Size May Not Be Optimal. Critical threshold removed, Warning set to 75 and Info set to 85.
Performance Advisor
Binary Log Usage Exceeding Disk Cache Memory Limits. Critical threshold removed, Warning set to 50 and Info set to 70.
Excessive Disk Temporary Table Usage Detected. Critical threshold removed, others left unchanged.
InnoDB Buffer Pool Writes May Be Performance Bottleneck. Critical threshold removed, Warning set to 99 and Info set to 99.5.
InnoDB Log Waits May Be Performance Bottleneck. Critical threshold removed, Warning set to 1 and Info set to 0.5.
In the Enterprise Dashboard, the Monitor page did not have detailed server meta information. For example, the hostname, datadir, socket and port information were not displayed.
The interface has now been changed to include the following. Hostname, datadir, socket, and port information has been added to the server meta information on the monitor page. The port and datadir information has been added to the Settings, Manage Servers page. Socket and datadir information has been added to the edit server popup. (Bug#40787)
When running multiple instances of the Enterprise Dashboard it could be difficult to determine which instance is currently being logged into.
This was fixed by adding a name for the server on the login page. The name defaults to the hostname but may be changed in the Settings page. (Bug#40642)
The agent should be able to run as a non-root
user. However, the startup scripts always started it as
root
.
The agent chassis now has a new option --user
to drop privileges after being started as
root
. Note, this does not work when not
started as superuser, nor on Windows.
A new dialog box has also been added to the agent installer. The
dialog has the following text: “The agent does not need to
run with root
user privileges. The agent will
switch to the user account provided below when started by the
root
user.”
The dialog also has a text field to allow the entry of the user account.
A new parameter was also added to the
mysql-monitor-agent.ini
file. The parameter
has the format user=xxx
, where xxx is the
user account to be used.
(Bug#33778)
The Advisor rule “InnoDB Redo Logs Not Sized Correctly” has been renamed to “InnoDB Transaction Logs Not Sized Correctly”. The rule's Problem Description and Advice text have also been updated accordingly. (Bug#33528)
You can now configure an individual notification group to be used when sending critical email alerts. You can configure this by selecting the administration checkbox when configuring an individual notification group. For more information, see Section 15.5.5, “Manage Notification Groups”. (Bug#30974)
The Event Log now tracks both the Current and Worst states for individual events.
To enable communication by MySQL Enterprise Service Manager with the MySQL Enterprise website, you can now configure an HTTP Proxy to be used when accessing the Internet. For more information, see Section 15.5.1, “Global Settings”.
The MySQL Enterprise Dashboard now includes a What's New page that incorporates information automatically from the MySQL Enterprise and MySQL Support websites. For more information, see Section 15.6, “The What's New Page”.
Bugs fixed:
The installer for MySQL Enterprise Monitor Agent on Linux 64-bit using glibc-2.3 would fail before the installation had completed properly. (Bug#50289)
The alert for “Connection Usage Excessive”
recommended raising max_connections
. However,
if the users raised max_connections
based
only on the advice of the alert, they could potentially exhaust
all RAM and SWAP.
This alert should have made the proviso that
max_connections
be increased only if
sufficient free RAM is available to support the additional
connections. The alert should also have recommended checking
that all connections are correctly closed, and suggest lowering
the wait_timeout
or
interactive_timeout
settings.
(Bug#46921)
The “Slow Query Log Not Enabled” rule was missing a <value> tag in the <thresholdList> block. This caused a stack trace to be generated when the Service Manager started. (Bug#46899)
Table lock contention rules had inconsistent thresholds.
The rule lock_contention_excessive
(part of
the Basic subscription) contained the following expression:
(%Uptime% > 10800) && (((%Table_locks_waited% / (%Table_locks_immediate% + %Table_locks_waited%)) * 100) > THRESHOLD)
This used thresholds of 1/3/5 (for Info/Warning/Critical).
However, in the rule
table_lock_contention_excessive
(part of the
Platinum subscription), the same expression existed but with
different thresholds:
(%Uptime% > 10800) && (((%Table_locks_waited% / (%Table_locks_immediate% + %Table_locks_waited%)) * 100) > THRESHOLD)
In this case the thresholds were 30/60/95. (Bug#46768)
MySQL Enterprise Monitor 2.1 advisors for Windows suggested using
innodb_flush_method=unbuffered
, which is an
undocumented value. Only documented values should have been
recommended.
(Bug#46709)
When deleting a server within MySQL Enterprise Dashboard where there was a lot of historical data and/or a large number of instances being monitored, the deletion process could take some time and affect the loading of all pages within MySQL Enterprise Dashboard The process should no longer affect the performance UI. (Bug#46632)
The rule names and other content on the Rules page could be displayed without the necessary formatting and translation. (Bug#46608)
You would get a Java NullPointerException
message if you omitted to select a server before using
Add server to group to add a new server to
an existing group.
(Bug#46593)
Initial setup and registration of MySQL Enterprise Monitor could fail on Mac OS X when communicating with the MySQL Enterprise website. (Bug#46571)
The MySQL Enterprise Service Manager would send one email from each agent when agents were no longer able to write information to the repository. You now get one email containing a list of the affected agents. (Bug#46460)
The error message shown in the orange dialog when a Rule could not be scheduled showed the Rule's resource key instead of its name. For example:
U0146 Unable to schedule rule "binary_logging_is_limited.name" due to "mysql.MasterStatus.Binlog_Ignore_DB" data not being collected from server "net-dev2:13306". It may be an unsupported collection for that server.
The length of the MySQL Enterprise Monitor related cookie information caused the web browser to fail with errors such as the following (from Safari 4):
Bad Request Your browser sent a request that this server could not understand. Size of a request header field exceeds server limit. Cookie: __utma=183337658.3685800196369993700.1241092024.1248080652.1248188601.199; __utmc=183337658; __utmz=183337658.1247859315.194.26.ut......
The values reported for the
os.mem.swap_page_out
and
os.mem.swap_page_in
could be identified
incorrectly as delta, instead of absolute, values.
(Bug#46326)
When upgrading an agent that uses SSL to connect to MySQL Enterprise Service Manager using a non-standard SSL port (i.e. not 18443), the upgrade would change the SSL port back to the default value. (Bug#46253)
When upgrading MySQL Enterprise Service Manager any custom properties set within
config.properties
would be lost. Changes are
now retained during an upgrade.
(Bug#46252)
When installing MySQL Enterprise Service Manager the disk space requirements could be calcualted incorrectly, which would cause the remainder of the installation to fail. (Bug#46251)
Installation of MySQL Enterprise Monitor Agent on Solaris 8 or Solaris 9 using the SPARC platform could fail if the latest patches of the SUNW UTF-8 and iconv libraries were not available. This prevented the installer from operating correctly, although the agent would work correctly. The installer for the agent has now been updated to avoid this issue. (Bug#46235)
In the Enterprise Dashboard, the query summary information popup on the BrowseQueries page forced a page reload after any hide. This affected both the user pressing the hide button, as well as the links on the Example and Explain tabs that caused the query summary information popup to be hidden, and the Query Analyzer config popup to be shown instead. (Bug#46230)
The Agent had a memory leak. The memory consumption increased by 35MB every five minutes. (Bug#46222)
The MySQL server embedded with MySQL Enterprise Service Manager has been updated to MySQL 5.1.37. (Bug#46214)
After a Service Manager upgrade, if there were migration errors, the message “Upgrade Status: there were errors in migration (details)” was displayed on the Settings, Manage Servers page. When the details link was clicked the yellow “An Error Occurred” popup was briefly displayed before disappearing, making it impossible to determine the details of the error. (Bug#46181)
When installing a new Advisor JAR, the contents could overwrite localizations in your current installation. (Bug#46169)
The threshold information in email alerts listed the thresholds in a seemingly random order, for example:
Thresholds Warning : 1024 Info : 512 Critical : 10240 Thresholds Info : 70 Critical : 5 Warning : 40 Thresholds Critical : 75 Warning : 85 Info : 95
In the Enterprise Dashboard, the check boxes within the configure what's new panel did not function correctly. When deselecting a check box the accompanying text did not become de-emphasized (“grayed out”) as expected, but only changed when another check box was selected. Further, when the checkbox was subsequently selected, the text did not become emphasized until another check box was selected or deselected. This problem was limited to Internet Explorer 8. (Bug#46104)
In the Enterprise Dashboard, selecting all three checkboxes in the Configure Query Analyzer panel generated an error:
The interval “00:00:00,500” could not be parsed. Intervals must be in hh:mm:ss.msec
format.
The error was due to the default value of Auto-Explain Threshold containing a “,” rather than a “.” character. (Bug#46102)
The MySQL Enterprise Monitor Agent could return a null value for a valid result set, resulting in incorrect results when using Query Analyzer. (Bug#46095)
The Rule “Non-Authorized User Has Server Admin Privileges” in the “Security” Advisor checked for the following:
Create_user_priv = 'Y' File_priv = 'Y' Lock_tables_priv = 'Y' Reload_priv = 'Y' Shutdown_priv = 'Y' Super_priv = 'Y
However, it did not include a check for the condition:
Process_priv = 'Y'
The Query Analyzer Statement Popup history graphs were inconsistent with the other graphs. In particular:
The series colors were not consistent with other graphs.
The graph image was right aligned, but the title was left aligned. When the popup was expanded, unnecessary space was located on the left.
The Y axis did not have a Range Label.
In the Enterprise Dashboard, if a Notification Group was created, and also set to be the “MEM Admin” for cry for help emails, the MEM Admin column showed as "false" in the table overview when the group was saved. However, if the group was then edited and the flag added again, the MEM Admin status was saved. (Bug#46038)
Links in emails generated from the Query Analyzer were not linking to the Query Analyzer tab correctly. (Bug#46036)
When a query was clicked on the Query Analyzer page, the Explain Query tab displayed a potentially incorrect value for the Auto-Explain Threshold. The Threshold can actually be set to a user configurable value in Configure Query Analyzer, but the popup text did not reflect the currently set value, instead displaying a hard-coded default value. (Bug#46035)
The Rule “Server Includes A Root User Account” in the “Security” Advisor had a Recommended Action:
UPDATE user SET user = 'new_name' WHERE user = 'root'; FLUSH PRIVILEGES;
However, three other rules triggered in the case where “user” was not “root” but had administrative grants. This caused the following alerts to be generated:
Non-Authorized User Has DB, Table, Or Index Privileges On All Databases
Non-Authorized User Has GRANT Privileges On All Databases
Non-Authorized User Has Server Admin Privileges
In the Enterprise Dashboard, on the Settings, Manage Servers page, the menu item Configure Query Analyzer generated an unhandled error message if clicked when using the Silver level subscription. Query Analyzer is not available at this subscription level, and the menu option to configure the analyzer should not be shown on this page. (Bug#46016)
If the Agent and monitored server had time settings that were out of sync the Enterprise Dashboard reported the server as “down”. (Bug#45937)
On the What's New? page of the Enterprise Dashboard, multiple messages were generated for the same error. This cluttered the user interface. (Bug#45927)
In the Enterprise Dashboard, when using the Safari web browser, the graph selection displayed on the Query Analyzer tab was sometimes drawn outside the plot area. (Bug#45926)
The Enterprise Monitor log was flooded with ERROR/WARN messages
when the Service Manager was retrying for a
mysqld
connection:
2009-07-02 16:52:23,440 WARN [http-18080-4:com.mysql.sql] java.lang.Exception: MySQL server not running or accepting connections, retrying 30 times or 46 seconds, whichever expires first. Exception was: Communications link failure Last packet sent to the server was 0 ms ago. 2009-07-02 16:52:24,455 WARN [Purger:com.mysql.sql] java.lang.Exception: MySQL server not running or accepting connections, retrying 46 times or 151 seconds, whichever expires first. Exception was: Communications link failure Last packet sent to the server was 0 ms ago. 2009-07-02 16:52:25,471 WARN [http-18080-5:com.mysql.sql] java.lang.Exception: MySQL server not running or accepting connections, retrying 28 times or 34 seconds, whichever expires first. Exception was: Communications link failure Last packet sent to the server was 0 ms ago. 2009-07-02 16:52:26,377 WARN [http-18080-9:com.mysql.sql] java.lang.Exception: MySQL server not running or accepting connections, retrying 33 times or 64 seconds, whichever expires first. Exception was: Communications link failure Last packet sent to the server was 0 ms ago.
In the Enterprise Dashboard the icon file for
event.status.closed
was missing. The problem
manifested differently in different browsers. In Internet
Explorer 8 the UI cell was empty and no text was displayed. In
Firefox 3 the text “event.status.closed” was
displayed in the cell.
(Bug#45872)
If the system time zone was different from that set in the Enterprise Dashboard, then there was inconsistency in the way times were displayed on the Query Analyzer page. Some times were displayed in the time zone of the system and some were displayed using the Dashboard time zone setting. (Bug#45858)
In Enterprise Dashboard, when a range on the graph in the Graphs tab was selected, the following error message was displayed:
Error Message You do not have permissions to access this resource. E0211: PermissionDeniedException: [] com.mysql.merlin.ui.interceptors.AuthenticationInterceptor.intercept(AuthenticationInterce ptor.java:109) com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java :224) com.opensymphony.xwork2.DefaultActionInvocation$2.doProfiling(DefaultActionInvocation.java :1) com.opensymphony.xwork2.util.profiling.UtilTimerStack.profile(UtilTimerStack.java:455) com.opensymphony.xwork2.DefaultActionInvocation.invoke(DefaultActionInvocation.java:221) org.apache.struts2.impl.StrutsActionProxy.execute(StrutsActionProxy.java:50) org.apache.struts2.dispatcher.Dispatcher.serviceAction(Dispatcher.java:507) org.apache.struts2.dispatcher.FilterDispatcher.doFilter(FilterDispatcher.java:421) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja va:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) net.sf.ehcache.constructs.web.filter.GzipFilter.doFilter(GzipFilter.java:81) net.sf.ehcache.constructs.web.filter.Filter.doFilter(Filter.java:92) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja va:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) com.mysql.util.RequestCounterFilter.doFilter(RequestCounterFilter.java:117) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja va:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) com.mysql.merlin.ui.filters.AccessLogFilter.doFilter(AccessLogFilter.java:56) org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.ja va:235) org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:175) org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:128) org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:263) org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:844) org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.jav a:584) org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:447) java.lang.Thread.run(Unknown Source)
If both the View Readme and Launch Monitor in browser check boxes were selected on the last screen of the Monitor installer, the Dashboard was not brought up in a browser until after the window displaying the “readme” information was closed. (Bug#45795)
The Agent did not report all the rows from an explain plan where the plan had more than one row. The Dashboard would display information for the first row, but subsequent rows would display NULL. (Bug#45791)
Custom collections did not override standard collections.
If a custom collection file was defined, and collections specified which were the same as the defaults but with some extensions, the custom collection did not appear to be processed and so did not override the default collection. (Bug#45755)
When the Service Manager was restarted, or if the Service Manager was turned off for a brief period, and then turned back on, some graphs, such as Database Activity, showed an erroneous spike in traffic. (Bug#45688)
Cry for help emails were not sent for events such as the monitored server running out of connections or disk space. In the past these had been sent for any error code < 1026. (Bug#45667)
If custom collection files were created for the Agent, and
references added to the agent-item-files
variable within the mysql-monitor-agent.ini
file, on upgrade the following problems occurred:
The agent-item-files
variable was
overwritten, thereby removing the custom entry.
The custom files were deleted, if they were contained in the
share/
directory.
In the Enterprise Dashboard, when closing single or multiple Events the following exception was generated:
Could not execute JDBC batch update org.hibernate.exception.SQLStateConverter.convert(SQLStateConverter.java:71)
In the Enterprise Dashboard, the icon displayed for each server on the Bug#45564)
, page was incorrectly located. This resulted in fewer servers being displayed per page. (In Enterprise Dashboard, when clicking on configure what's new in the What's New? tab, an error occurred. This only happened when using Internet Explorer 8. (Bug#45478)
After the initial server installation a user may select OpenSSL
native integration with Tomcat. This will modify the
apache-tomcat/lib
directory. However,
subsequently running an upgrade installer overwrote the
apache-tomcat/lib
directory which had been
modified during the OpenSSL native integration.
(Bug#45432)
The query SELECT * FROM 23lk4kj234;
was
reported incorrectly in the Query Analyzer.
(Bug#45431)
When an event was closed a “SUCCESS” SNMP trap was sent, rather than a “CLOSED” SNMP trap. (Bug#45376)
When MySQL Enterprise Monitor 1.3 was upgraded directly to 2.1, and having requested SSL in the upgrade dialog, SSL did not work in the upgraded Monitor. (Bug#45339)
When an event was closed, the row in the event table where the event entry was located had its checkbox disabled, even though the event now in that row was open. This happened regardless of whether the close link were used to close the event. (Bug#45250)
button, or theThe Notifications list in the Schedules or Edit Schedules popups listed the Notification Groups targets in the order in which they were created, not alphabetical order. (Bug#45169)
A small memory leak occurred in the agent when a connection attempt to the dashboard failed. This represented a problem if the agent was unable to connect to the dashboard for a long period of time, as each failure to connect would leak some more memory. (Bug#45164)
When disabling Query Analyzer while the two sub-options remain enabled for an individual agent, the analyzer, explain and other options would be logged by the agent as critical errors. Now, only the disabling of Query Analyzer is logged as a critical error. The Example Query and Example Explain options are reported as info errors. (Bug#45041)
The Agent attempted to obtain the Query Analyzer configuration before the Monitor server has created it. This resulted in the Agent generating the following critical error in the log:
2009-05-21 15:59:42: (critical) network-io.c:255: successfully reconnected to dashboard at http://agent:merlin@127.0.0.1:18080/heartbeat 2009-05-21 15:59:47: (critical) agent_mysqld.c:641: successfully connected to database at 127.0.0.1:13306 as user marcos (with password: YES) 2009-05-21 15:59:52: (critical) network-io.c:807: starting task 2 for mysql::server[8b1294a5-b40b-457c-b8d3-a834848dc1df] 2009-05-21 15:59:52: (critical) job_collect_lua.c:323: ...ql/enterprise/agent/share/mysql-proxy/items/quan.lua:505: GETing quan-config from http://agent:merlin@127.0.0.1:18080/v2/rest/instance/mysql/StatementAnalysisSupport/8b1294 a5-b40b-457c-b8d3-a834848dc1df failed with: 404 8b1294a5-b40b-457c-b8d3-a834848dc1df of type mysql.StatementAnalysisSupport not found 2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:528) setting .analyze_queries for 8b1294a5-b40b-457c-b8d3-a834848dc1df to true 2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:532) setting .auto_explain for 8b1294a5-b40b-457c-b8d3-a834848dc1df to true 2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:536) setting .analyze_worst_queries for 8b1294a5-b40b-457c-b8d3-a834848dc1df to true 2009-05-21 16:00:00: (critical) (share/mysql-proxy/items/quan.lua:540) setting .auto_explain_min_exec_time_us for 8b1294a5-b40b-457c-b8d3-a834848dc1df to 500000
If a migration from 1.3 to 2.0 was initiated and a new server created during the migration, but then deleted before migration was finished, the new server delete operation failed with an Null Pointer Exception (NPE). (Bug#44991)
If you have the environment variable
http_proxy
set within your environment, when
connections from MySQL Enterprise Monitor Agent could be redirected to an
external site, instead of sending them to the configured
MySQL Enterprise Service Manager. You can disable this behavior by adding the
contents of the agent-mgmt-hostname
configuration option for MySQL Enterprise Monitor Agent to the
no_proxy
variable.
(Bug#44893)
The regular expression used to parse the adaptive hash index
section of SHOW INNODB STATUS
for the cell
size/used and node size did not function correctly for versions
of monitored server greater than 5.1.28. This was because the
section of the expression dealing with “cells used”
was removed as part of Bug#36941.
(Bug#44853)
The Rule “InnoDB Buffer Cache Hit Rate Not Optimal” in the “Memory Usage” Advisor did not contain an uptime check. This resulted in premature firing of an info event. (Bug#44770)
Any JAVA_OPTS
configuration changes made in
the catalina.sh
file, such as
-Xmx
, -Xms
, were overwritten
when the upgrade installer was run. These values were used for
customizing larger installations.
(Bug#44740)
In the Advisor “Administration” the Rule “InnoDB Redo Logs Not Sized Correctly” did not fire correctly. The rule contained the expression:
(%have_innodb% == "YES") && ((%innodb_log_file_size% * %innodb_log_files_in_group%) < LEAST(1073741824, (%innodb_buffer_pool_size% / 2)))
This was incorrect and needed to be changed to:
(%have_innodb% == "YES") && ((%innodb_log_file_size% * %innodb_log_files_in_group%) <= LEAST(1073741824, (%innodb_buffer_pool_size% / 2)))
If the Service Manager was set up to use an HTTP proxy, all
traffic attempted to go through the proxy, including the
connection to the mysqld
server running the
repository.
(Bug#44729)
The recommendation for the rule Table Cache Not
Optimal
says:
Recommended Action SET GLOBAL table_cache = (64 + 16);
But an error was generated on executing that query:
mysql> SET GLOBAL table_cache = (64 + 16); ERROR 1193 (HY000): Unknown system variable 'table_cache' mysql> select version(); +------------+ | version() | +------------+ | 5.1.31-log | +------------+ 1 row in set (0.01 sec)
In Enterprise Dashboard, clicking on a query listed on the Query Analyzer page resulted in a delay of around 28 seconds before the popup was displayed. (Bug#44601)
The frequency shown on the Advanced tab of an Event popup was the default frequency for a rule and not the frequency actually scheduled. (Bug#44591)
Any changes made to the config.properties
file, were overwritten by the upgrade installer.
(Bug#44526)
If a customer was using their own SSL certificate, they entered
that information in the server.xml
file.
However, running the upgrade installer caused
server.xml
, and any custom certificates, to
be replaced.
(Bug#44525)
If you edited the server.xml
file inside
the tomcat/conf/
folder, and changed the
Tomcat port, running the upgrade installer did not show you the
new port number, but the one you used at the installation time.
It also did not remember that you had enabled SSL. (Bug#44444)
Editing an Advisor and selecting the Use SNMP Traps checkbox led to confusing behavior. Advisors appeared to be incorrectly enabled or disabled. (Bug#44387)
The Agent failed to correctly determine the state of the
monitored server if the thread-id
, extracted
from the client-server protocol, is greater than 2^32. In the
case with a thread-id
greater than 2^32, the
agent incorrectly determined that it was monitoring a remote
server. High values of thread-id
occur when
the monitored server has many connections, or if it has been
running for an extended period of time.
(Bug#44168)
The Mac OS X version of the Service Manager uses the system JRE.
The system JRE loads the libraries located in
/Library/Java/Extensions
. As libraries in
the extensions directory take precedence over other libraries,
this caused conflicts when user extension libraries were
installed there, as these would be used by the JRE when running
Service Manager, instead of the shipped libraries. This happened
when Java-related products were installed such as Connector/J,
Spring, and Hibernate.
This fix stops user-installed extension libraries from being used when the JRE runs the Service Manager, thus giving a “pristine” environment with no library collisions. (Bug#44157)
The What's New tab can no longer be hidden, as it now provides important information and updates about MySQL and MySQL Enterprise Monitor. (Bug#44107)
In the Enterprise Dashboard, when the frequency for a rule was changed in Bug#44102)
, , , incorrect thresholds were saved, leading to erroneous alerts. (MySQL Enterprise Monitor installation sometimes failed, generating the following error:
Installing Innitializing User accounts. (4/6) Error running /opt/mysql/enterprise/monitor/mysql/bin/mysql --defaults-file=/opt/mysql/enterprise/monitor/mysql/my.cnf -S /opt/mysql/enterprise/monitor/mysql/tmp/mysql.sock -u root -D mysql -e "update user set Password = PASSWORD('service_manager') where User = 'root'; update user set User = 'service_manager' where User = 'root';delete from user where User = '';flush privileges;" : ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/opt/mysql/enterprise/monitor/mysql/tmp/mysql.sock' (2)
After displaying this error, the MySQL Enterprise Monitor installer reported that it had “completed”, but the message displayed contained an error message string:
Report2.SetInstallerVariable.errorsOnSQLStatementsText
In the Enterprise Dashboard, in the Query Analyzer tab, the monitored parameter was not handled correctly during collapse and expansion of the graph. For example, if the graph was monitoring CPU Utilization, and then collapsed and the parameter changed to Database Activity, the monitored parameter reverted to CPU Utilization when the graph was expanded again. (Bug#44029)
The upgrade installer overwrote any custom settings stored in
WEB-INF/config.properties
. For example it
set the database host back to localhost
.
(Bug#44003)
Accessing the Query Analyzer tab caused a full table scan to take place on the MySQL Enterprise Monitor database. (Bug#43989)
Some SNMP managers could not detect “Application Error” SNMP notifications.
This happened because some SNMP managers do not follow the
protocol correctly. Some use the
DisplayString
length of 255 as the maximum
OctetString
, but this is in fact unlimited in
SMIv1 and 64k in SMIv2.
To work around this issue it is possible to override the correct
behavior to allow non-comformant SNMP Managers to detect all
messages. This is achieved by overriding the
OctetString
maximum size by setting a
MySQL Enterprise Monitor server property. This is done by entering SQL such as
the following:
INSERT INTO map_entries VALUES (1,'2048','snmp.octetstring');
In this example the value 2048 will be the maximum SNMP
OctetString
size that would sent in any SNMP
traps. After setting this property the server will need to be
restarted. Note that the value used may need adjusting depending
on the behavior of the SNMP manager.
(Bug#43970)
When updating an Agent from 2.0 to 2.1 the
mysql-monitor-agent.ini
was incorrectly
updated.
This happened if the Agent was configured to use SSL to connect to the Enterprise Dashboard, on a port other than 18443. The update installer caused any value specified for the port to be changed to 18443. This did not happen if the Agent was not using SSL. (Bug#43900)
The Enterprise Dashboard was running abnormally slowly. Clicking on a tab in the Dashboard, or selecting a server from the server tree resulted in a delay of approximately one minute before the results were displayed. (Bug#43866)
The Agent failed on Linux 32-bit systems with the following error:
2009-03-24 16:01:09: (debug) chassis.c:1091: current RLIMIT_NOFILE = 4398046512128 (hard: 577792033385921489) 2009-03-24 16:01:09: (debug) chassis.c:1095: trying to set new RLIMIT_NOFILE = 4398046519296 (hard: 577792033385921489) 2009-03-24 16:01:09: (critical) chassis.c:1097: could not raise RLIMIT_NOFILE to 8192, Invalid argument (22). Current limit still 13811918798715880448. 2009-03-24 16:01:09: (message) MySQL Monitor Agent 2.0.5.7153 started.
This happened with the following environment:
$ ./mysql-monitor-agent -V mysql-proxy 0.7.0 glib2: 2.16.3 libevent: 1.4.6-stable proxy: 0.7.0 monitor: 0.7.0 MySQL Monitor Agent(agent): 2.0.5.7153 admin: 0.7.0 $ cat /etc/redhat-release Red Hat Enterprise Linux ES release 3 (Taroon Update 5) $ uname -a Linux xxxx 2.4.21-32.0.1.ELsmp #1 SMP Tue May 17 17:52:23 EDT 2005 i686 i686 i386 GNU/Linux
The same error also occurred on CentOS 5.2 32-bit systems. (Bug#43821)
The Replication Group was renamed back to its default name after a new topology was discovered. (Bug#43816)
A new topology was not discovered after the previous replication group was renamed. (Bug#43815)
On Unix systems, executing the command:
./mysqlmonitorctl.sh stop
did not make sure that mysqld
was shutdown
before finishing.
This resulted in a situation such as the following:
# /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh stop Using CATALINA_BASE: /opt/mysql/enterprise/monitor/apache-tomcat Using CATALINA_HOME: /opt/mysql/enterprise/monitor/apache-tomcat Using CATALINA_TMPDIR: /opt/mysql/enterprise/monitor/apache-tomcat/temp Using JRE_HOME: /opt/mysql/enterprise/monitor-2.0.0.7092/java Stopping tomcat service ... [ OK ] /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh : mysql stopped
However, running the following command a few minutes later showed that the MySQL server was still running:
# /opt/mysql/enterprise/monitor-2.0.0.7092/mysqlmonitorctl.sh status MySQL Network MySQL is running MySQL Network Tomcat is not running
The MySQL Enterprise Monitor upgrade installer incorrectly
replaced the AdvisorScript.jar
in
<instDir>/apache-tomcat/webapps/ROOT/WEB-INF/lib/
with the default Advisor JAR.
(Bug#43773)
The SNMP trap source IP was always set to 127.0.0.1. (Bug#43738)
The advisor “Replication - Slave Has Login Accounts With Inappropriate Privileges” contained inappropriate advice information.
The advice message generated was:
Server: slave-01 Time: 2009-03-17 12:00:04 GMT Advisor: Replication - Slave Has Login Accounts With Inappropriate Privileges Problem Description Altering and dropping tables on a slave can break replication. Unless the slave also hosts non-replicated tables, there is no need for accounts with these privileges. Advice Revoke the global ALTER and DROP privileges from the following accounts on server slave-01 unless they are absolutely necessary: user_1@localhost, user_2@localhost Recommended Action REVOKE ALTER, DROP ON *.* FROM user_name@host_name; FLUSH PRIVILEGES;
However, the problems with this advice were:
The server was configured read_only
so it
would not be possible to DROP
or
ALTER
tables unless the user had
SUPER
privilege.
MySQL grants were replicated from the master and therefore
appeared on the slave. Also, read_only
ensured the slave could not be changed.
In Enterprise Dashboard, if on the Monitor page the Configure Graphs link was clicked, no changes made, and then the button clicked, then the following error was generated:
U0023 You must provide a non-zero interval
The installer exited with a return code 0
,
even if an error was detected and reported to the user during
the installation.
.../mysqlmonitor-2.1.0.1015-linux-x86-64bit-installer.bin --mode unattended --installdir /data0/merlin/monitoring/2.1.0.1015/host/38080 --tomcatport 38080 --tomcatshutdownport 38503 --tomcatsslport 38443 --dbport 33300 --usessl 1 --adminuser **user** --adminpassword **pwd** Error running /data0/merlin/monitoring/2.1.0.1015/host/38080/mysql/bin/mysql --defaults-file=/data0/merlin/monitoring/2.1.0.1015/host/38080/mysql/my.cnf -S /data0/merlin/monitoring/2.1.0.1015/qa-merlin/38080/mysql/tmp/mysql.sock -u root -D mysql -e "update user set Password = PASSWORD('**pwd**') where User = 'root'; update user set User = '**user**' where User = 'root';delete from user where User = '';flush privileges;" : ERROR 2002 (HY000): Can't connect to local MySQL server through socket '/data0/merlin/monitoring/2.1.0.1015/host/38080/mysql/tmp/mysql.sock' (2)
The Connections graph did not include information from the Thread Cache graph. Connections and Thread Cache were available as separate graphs but it was difficult to compare them. (Bug#43584)
If it was desired to look at MySQL Enterprise Monitor graphs for time spans of over 24 hours, you had to change from Interval to From/To mode, and specify a fixed From and To period. This was inconvenient compared to simply specifying a greater interval. (Bug#43564)
The agent created the mysql.inventory
table
with an engine type of InnoDB, instead of MyISAM, when InnoDB
was specified as the default engine type in
my.cnf
. This happened because the agent did
not explicitly specify the table engine type to be of MyISAM.
(Bug#43551)
When a trailing space, or tab character, was added at the end of
a parameter in the config.properties
file,
MySQL Enterprise Monitor failed to start and generated the
following errors in log:
ERROR [Thread-1:org.springframework.web.context.ContextLoader] Context initialization failed ... Caused by: java.sql.SQLException: Illegal connection port value '13306' ...
Resolving the problem required detailed log analysis because the configuration file did not show any apparent problems. (Bug#43540)
The MySQL Enterprise Monitor installer failed to install correctly due to insufficient disk space, even though the installer calculated there was suffcient disk space for the installation. This was due to the installer having out of date information regarding disk space requirements. (Bug#43538)
After removing enough servers to bring the host count back down to the number covered in the subscription, the Subscription Warnings reflected the new number. However, the warning message displayed:
You are currently monitoring 1 host, however your subscription covers only 1. Your subscription needs to be updated to cover at least 0 additional hosts.
Instead of displaying:
Your subscription is up-to-date You have no warnings at this time.
The former message resulted in confusion. (Bug#43163)
If a host was not a slave during the initial discovery phase, then it would not be displayed in the Replication tab if it subsequently became a slave.
This was because after the initial discovery phase, if a host
did not have slavestatus
present, no
subsequent checks were made to check for the host being a slave.
It was therefore missed for the purposes of replication
discovery and never showed in the Replication tab.
(Bug#42997)
In the Enterprise Dashboard it is only possible to delete monitored servers if they are stopped. Monitored servers can be deleted in Settings, Manage Servers. However, if after stopping the Agent, the Dashboard was not refreshed and the agent was started again, an error was generated saying that the agent was running and could therefore not be deleted. Although correct, this was confusing as the Dashboard showed the Agent as stopped but the delete operation error message showed the Agent as running. (Bug#42983)
Heat Chart rules could not be disabled or unscheduled. (Bug#42932)
There were four columns added to the SHOW SLAVE
STATUS
query in MySQL Server 5.1:
Last_IO_Errno
,
Last_IO_Error
,
Last_SQL_Errno
, and
Last_SQL_Error
.
However, these were not displayed within the Replication tab. (Bug#42811)
Agent IP address was not included in SNMP traps. It was also not possible to set these Agent IP addresses through a configuration, which would have been useful for situations where the Agent could not determine the monitored server IP address, such as when virtual IP addresses were used. (Bug#42703)
The Agent would not reconnect to a monitored database if it was started when the monitored server was down. The agent log contained the following error:
Can't connect to MySQL server on '127.0.0.1' (0) (mysql-errno = 2003)
The agent only sent OS data to the Dashboard. Further, when the monitored server was later started, no attempts to reconnect were logged.
The problem could be worked around by restarting the agent when the monitored server was running again. (Bug#42581)
The installer used to upgrade from version 1.3 corrupted passwords containing the “?” character. (Bug#42452)
Sun multi-core processors caused all cores to be reported on the meta information page.
The larger T-series SPARC processors have 32+ cores. This caused the meta information page in the Dashboard to scroll as it reported each one. (Bug#42355)
The username field for new users was populated by the last username used.
When creating a new user for the second time in Dashboard, the previously created username appeared in the dialog. (Bug#42314)
The Agent shut down if the wrong username/password was given in the Service Manager. This happened on a fresh installation, when running the Service Manager through the Proxy. When Cannot open conection” was displayed. The Agent log also contained the following errors:
was clicked to finish the installation the error “2009-01-20 15:54:16: (critical) <-- received HTTP-status: 401 (failed) for 'http://agent:mysql@127.0.0.1:8080/Monitor2/heartbeat': password are wrong 2009-01-20 15:54:16: (critical) shutting down normally 2009-01-20 15:54:19: (critical) <-- received HTTP-status: 401 (failed) for 'http://agent:mysql@127.0.0.1:8080/Monitor2/heartbeat': password are wrong 2009-01-20 15:54:19: (critical) shutting down normally
The my.cnf
file for the Enterprise Monitor
internal database had the following configuration item:
innodb_autoextend_increment = 50M
This generated the error:
16:36:23 [Warning] option 'innodb_autoextend_increment': unsigned value 52428800 adjusted to 1000
This variable is interpreted as being specified in MB, so 50M would be 50 TB. Such a high value results in the variable being adjusted to 1000 MB.
The value in the configuration file should be:
innodb_autoextend_increment = 50
A number of Advisor rules had advice text that had not been translated into Japanese. The Advisors that contained untranslated rules included Performance, Schema and Security. (Bug#42067)
Using a long interval for the long data collection purging (such
as 6 weeks), and a short interval for the query analysis purging
(such as 1 week) caused the Query Analyzer purge
EXPLAIN
for the INSERT
...
SELECT
into the
temp_dc_ng_*_now
table to perform a full scan
on the dc_ng_*_now.end_time
index. For
example:
explain SELECT instance_attribute_id, end_time, end_time FROM dc_ng_long_now JOIN inventory_instance_attributes USING (instance_attribute_id) JOIN inventory_instances USING (instance_id) WHERE dc_ng_long_now.end_time <= 1230814870074 AND dc_ng_long_now.instance_attribute_id AND type_id in (8, 9, 7, 6) ORDER BY dc_ng_long_now.end_time ASC LIMIT 10000\G *************************** 1. row *************************** id: 1 select_type: SIMPLE table: dc_ng_long_now type: range possible_keys: PRIMARY,end_time key: end_time key_len: 8 ref: NULL rows: 8205369 Extra: Using where; Using index *************************** 2. row *************************** id: 1 select_type: SIMPLE table: inventory_instance_attributes type: eq_ref possible_keys: PRIMARY,instance_id key: PRIMARY key_len: 4 ref: mem.dc_ng_long_now.instance_attribute_id rows: 1 Extra: *************************** 3. row *************************** id: 1 select_type: SIMPLE table: inventory_instances type: eq_ref possible_keys: PRIMARY,FKD4320F5BBDD9C29B key: PRIMARY key_len: 4 ref: mem.inventory_instance_attributes.instance_id rows: 1 Extra: Using where 3 rows in set (0.55 sec)
OM_REFRESH
was not supported by MySQL Proxy,
it caused an abort()
.
shell> ./mysql-proxy --proxy-backend-addresses=192.168.250.3:3306 network-mysqld-proxy.c.3524: COM_(0x07) is not handled Aborted (core dumped) (gdb) bt 0x00b1b402 in ?? () 0x00cbaf30 in raise () from /lib/i686/nosegneg/libc.so.6 0x00cbc811 in abort () from /lib/i686/nosegneg/libc.so.6 0x08061efc in IA__g_logv at gmessages.c:497 0x08061f66 in IA__g_log at gmessages.c:517 0x08054645 in proxy_read_query_result at network-mysqld-proxy.c:3522 0x0804c5f4 in plugin_call at network-mysqld.c:977 0x0804d45a in network_mysqld_con_handle at network-mysqld.c:1520 0x08057cb9 in event_process_active (base=0x978b260) at event.c:331 0x08057e64 in event_base_loop (base=0x978b260, flags=0) at event.c:449 0x08057d1c in event_base_dispatch (event_base=0x978b260) at event.c:351 0x0804d9d0 in network_mysqld_thread (_srv=0x9789008) at network-mysqld.c:1768 0x0804b84a in main (argc=1, argv=0xbfc4fe84) at mysql-proxy.c:615
The MySQL Enterprise Monitor file my.cnf
specified an initial size of 500M for the central tablespace.
However, innodb_file_per_table
was used as well, resulting in approximately 500M of space being
potentially wasted.
(Bug#41967)
It was not possible to change any settings related to Query Analyzer unless at least one MySQL server was already being monitored. (Bug#41875)
The advisor “User Has Rights To Database That Does Not Exist” generated erroneous alerts.
If a database was created with an “_” character in the name, and then user privileges granted to this database using the escaped character sequence “\_” to prevent wildcards, then the advisor generates an error stating there is no database for the privilege.
For example, if the following is carried out on the monitored server:
CREATE DATABASE test_foo; GRANT SELECT ON `test\_foo`.* to testuser@'localhost' identified by 'test';
then the advisor warns that these users have rights to a database that does not exist:
''@'%' on DB test_%, 'test'@'localhost' on DB test_foo, 'testuser'@'localhost' on DB test_foo
In the Enterprise Dashboard, when a new server group was clicked in the main tab an error message was generated. On checking the Monitor log there were many error messages related to lock timeouts and having to retry transactions. This problem occurred after enabling purging of the Repository. (Bug#41461)
Running the Service Manager on Mac OS X and monitoring two servers with two agents for at least 16 hours caused the Java process to use 2.08 GB of memory. (Bug#41438)
After an error was generated due to an incorrect password while trying to create a new user, the following error was obtained when subsequently attempting to create a valid new user:
U0002 You must log in to access the requested resource
SNMP trap messages were sending 127.0.0.1 as the IP address, and there was no feature to allow the user to configure the IP address contained in the SNMP message, which would have been useful for troubleshooting. (Bug#41361)
Allowing the heat chart rules to be set to unscheduled caused the user interface to appear broken. (Bug#41312)
Data in the agent resource usage graphs (CPU, RAM) stopped after a full install of a new agent monitoring the same database was carried out. Usage history was available across agent versions for all graphs except the agent resource usage graphs. (Bug#41249)
Graphs were incorrect for data that did not change. The graphs appeared as if no data had been gathered.
The Hit Ratios graph had gaps in it where there had not been any activity on the parameters being monitored. For instance, if MyISAM tables were not used, then no Key Cache hit ratio series was plotted, even though the variables were still being collected. (Bug#41232)
The generic Linux IA64 glibc2.3 Agent installer was missing from the build. (Bug#41224)
When creating a new Database Administrator user in FireFox 2 the following error message was generated:
U0002 You must log in to access the requested resource.
This occurred in a new installation using the default administrator account. No Query Analysis permissions were given. However, the operation worked correctly using the Safari web browser. (Bug#41032)
The Enterprise Dashboard displayed a blank entry for Disk Space in the Meta Info area. This happened on Open Solaris 2008.05. This problem only occurred when using the ZFS file system. (Bug#40907)
The configuration for Query Analyzer that sets the default for all servers (using the Make this the default for all new servers checkbox) could still applied even when the dialog box was canceled. (Bug#40828)
The Manage Servers page did not refresh in a manner consistent with other pages. This meant that changes to configuration made by others would not be reflected on the page. Also, changes in the status of the servers were not displayed automatically. (Bug#40792)
The agent installer for HP-UX 11.11 would fail to execute correctly. (Bug#40568, Bug#40566, Bug#37508)
The graphs for Thread Cache, Connections and Temporary Tables contained incorrect Japanese translations on their Y axis. The Japanese displayed “total connection time (min)” when it should have displayed something else. For example, the Thread Cache graph should have displayed “total/min”. (Bug#40413)
If the MySQL Enterprise Monitor Agent was unable to execute an
EXPLAIN
on a query, it would report an empty
SQL query. The agent will now report the query hash value, which
can be used to identify the original query by examining the
repository.
(Bug#40353)
The agent installer for Solaris 8 x86 32-bit was missing. (Bug#40248)
Even though Query Analysis was disabled through the user interface, the queries that go through the agent were still being collected.
When Query Analysis was turned back on in the user interface, those queries were then displayed. (Bug#40032)
The Enterprise Dashboard did not display OS data if the Agent was changed from remote to local monitoring. (Bug#39954)
The agent crashed if ssh-keygen
was not
present and if a wireless card was being used instead of an
Ethernet card.
This only affected Unix based systems, it did not affect Microsoft Windows. (Bug#39938)
On Mac OS X when a server had more than 4GB RAM available the memory advisor was still triggered. This appeared to be due to an overflowing value. (Bug#39757)
The Agent received a critical error but did not terminate as expected. The critical error generated was:
2008-09-23 09:35:02: (critical) agent_mysqld.c:139: mysql_real_query() failed: Can't find file: './mysql/inventory.frm' (errno: 13) (errno=1017)
Alerts sent from MySQL Enterprise Monitor used the GMT timezone, for example:
Time: 2008-09-17 19:41:08 GMT
That was not convenient for users, as their timezones may not have been GMT. (Bug#39504)
The Agent running on AIX 5.3 did not report CPU data or RAM size, causing the Enterprise Dashboard to crash with a Null Pointer Exception. (Bug#38001)
The MySQL Enterprise Monitor upgrade installer replaced the
my.cnf
file. This resulted in the loss of
any changes that had been made to the configuration file.
(Bug#36528)
In the Enterprise Dashboard, on the Graphs page, the interface for selecting time intervals was not convenient, and it required multiple clicks to select the desired interval.
This was fixed by adding a selection of pre-determined time intervals. (Bug#34556)
Auto-generated replication group names were not translated into Japanese. (Bug#32155)
If the “On Save send test trap” checkbox was checked when the button was clicked and the locale was set to Japanese, an error occurred. The orange error banner was displayed at the top of the page with the error message in Japanese. (Bug#32069)
The Enterprise Dashboard could communicate with https://enterprise.mysql.com using the customer username and password to download the license key and advisor bundle. However, it could not make use of a proxy to do so. This was a problem as many corporate firewalls required the use of a proxy for all HTTP and HTTPS traffic.
The work around of having to manually download license keys and advisor bundles by hand was inconvenient. (Bug#31507)
The agent log does not include a specific note of when the
monitoring by the agent was started. An entry
AgentMonitoringService started
is now added
to the log.
(Bug#30609)
When the Agent was started as a service on Windows for the first
time, the name in the Task Manager window was
MYSQL-~1.EXE
. This occurred whether the
Agent was started from within the installer or from the Start
Menu.
If the service was restarted, the Agent's name changed to the
correct value, mysql-service-agent.exe
.
(Bug#30166)
When configuring a graph, setting a to date to a value prior to the from date, or the from date to a value after the to date will not automatically switch the dates when Bug#28473)
is pressed. (In the Enterprise Dashboard, the user interface allowed you to close an already closed event. This happened if multiple instances of the Events tab were created. It was possible to close an event with resolution notes in one instance, and then close the same event again with a different set of resolution notes in the other instance. However, on review, the resolution notes and event closure time stamp recorded, were those of the first closure. (Bug#24107)
When upgrading a monitored server, the information and configuration of the server would not be updated, leading to rules not being executed or applied correctly. Server's are now re-inventoried according to the specified schedule. For more information, see Remote Server Inventory Schedule. (Bug#24068)
The Dynamic Link Library (DLL) libxml2.dll
did not contain version resources. This meant version
information was not available to be displayed when the file was
examined in Windows Explorer.
(Bug#23948)
It was not possible to rename a notification group. (Bug#22962)
Failures by MySQL Enterprise Service Manager to send warning emails are now reported both in the logs and in the MySQL Enterprise Dashboard within the Product Info section of the Settings page. For more information, see Section 15.5.7, “The Product Information Screen”. (Bug#20478)
Functionality added or changed:
MySQL Connector/ODBC has been changed to support the
CLIENT_INTERACTIVE
flag.
(Bug#48603)
Bugs fixed:
The SQLColumns
function returned the
incorrect transfer octet length and display size for
DECIMAL
type.
(Bug#53235)
MySQL Connector/ODBC manually added a LIMIT
clause to the
end of certain SQL statements, causing errors for statements
that contained code that should be positioned after the
LIMIT
clause.
(Bug#49726)
If NO_BACKSLASH_ESCAPES
mode was used on a
server, escaping binary data led to server query parsing errors.
(Bug#49029)
Bulk upload operations did not work for queries that used parameters. (Bug#48310)
Describing a view or table caused SQLPrepare to prefetch table data. For large tables this created an intolerable performance hit. (Bug#46411)
If an application was invoked by the root user,
SQLDriverConnect()
was not able to use the
username and password in the connection string to connect to the
database.
(Bug#45378)
Calling SQLColAttribute
on a date column did
not set SQL_DESC_DATETIME_INTERVAL_CODE
.
SQLColAttribute
returned
SQL_SUCCESS
but the integer passed in was not
set to SQL_CODE_DATE
.
(Bug#44576)
Conversions for many types were missing from the file
driver/info.c
.
(Bug#43855)
The SQLTables()
function required
approximately two to four minutes to return the list of 400
tables in a database. The SHOW TABLE STATUS
query used by SQLTables()
was extremely slow
for InnoDB tables with a large number of rows because the query
was calculating the approximate number of rows in each table.
Further, the results could not be cached due to
non-deterministic nature of the result set (the row count was
re-calculated every time), impacting performance further.
(Bug#43664)
SQLDescribeCol
returned incorrect column
definitions for SQLTables
result.
(Bug#37621)
When opening ADO.Recordset
from Microsoft
Access 2003, a run-time error occurred:
ErrNo: -2147467259 ErrMessage: Data provider or other service returned an E_FAIL status.
SQLPrimaryKeysW
returned mangled strings for
table name, column name and primary key name.
(Bug#36441)
On Windows, the SOCKET parameter to the DSN was used as the named pipe name to connect to. This was not exposed in the Windows setup GUI. (Bug#34477)
MySQL Connector/ODBC returned a value of zero for a column with a non-zero
value. This happened when the column had a datatype of
BIT
, and any numeric type was used in
SQLBindCol
.
(Bug#32821)
Option for handling bad dates was not available in the GUI. (Bug#30539)
Functionality added or changed:
In the MySQL Data Source Configuration dialog, an excessive number of tabs were required to navigate to selection of a database. MySQL Connector/ODBC has been changed to make the tab order more practical, thereby allowing faster configuration of a Data Source. (Bug#42905)
Bugs fixed:
An error randomly occurred on Windows 2003 Servers (German language Version) serving classic ASP scripts on IIS6 MDAC version 2.8 SP2 on Windows 2003 SP2. The application connected to MySQL Server 5.0.44-log with a charset of UTF-8 Unicode (utf8). The MySQL server was running on Gentoo Linux.
The script error occurred sporadically on the following line of code:
SET my_conn = Server.CreateObject("ADODB.Connection") my_conn.Open ConnString <- ERROR
The connection was either a DSN or the explicit connection string:
Driver={MySQL ODBC 5.1 Driver};SERVER=abc.abc.abc.abc;DATABASE=dbname;UID=uidname;PWD=pwdname;PORT=3306;OPTION=67108864;
The error occurred on connections established using either a DNS or a connection string.
When IISState and Debug Diagnostic Tool 1.0.0.152 was used to analyse the code, the following crash analysis was generated:
MYODBC5!UTF16TOUTF32+6In 4640-1242788336.dmp the assembly instruction at myodbc5!utf16toutf32+6 in C:\Programme\MySQL\Connector ODBC 5.1\myodbc5.dll from MySQL AB has caused an access violation exception (0xC0000005) when trying to read from memory location 0x194dd000 on thread 33
MySQL Connector/ODBC overwrote the query log. MySQL Connector/ODBC was changed to append the log, rather than overwrite it. (Bug#44965)
MySQL Connector/ODBC failed to build with MySQL 5.1.30 due to incorrect use
of the data type bool
.
(Bug#42120)
Inserting a new record using SQLSetPos
did
not correspond to the database name specified in the
SELECT
statement when querying tables from
databases other than the current one.
SQLSetPos
attempted to do the
INSERT
in the current database, but finished
with a SQL_ERROR
result and “Table does
not exist” message from MySQL Server.
(Bug#41946)
Calling SQLDescribeCol()
with a NULL buffer
and nonzero buffer length caused a crash.
(Bug#41942)
MySQL Connector/ODBC updated some fields with random values, rather than with
NULL
.
(Bug#41256)
When a column of type DECIMAL
containing
NULL
was accessed, MySQL Connector/ODBC returned a 0
rather than a NULL
.
(Bug#41081)
In Access 97, when linking a table containing a
LONGTEXT
or TEXT
field to
a MySQL Connector/ODBC DSN, the fields were shown as
TEXT(255)
in the table structure. Data was
therefore truncated to 255 characters.
(Bug#40932)
Calling SQLDriverConnect()
with a
NULL
pointer for the output buffer caused a
crash if SQL_DRIVER_NOPROMPT
was also
specified:
SQLDriverConnect(dbc, NULL, "DSN=myodbc5", SQL_NTS, NULL, 0, NULL, SQL_DRIVER_NOPROMPT)
Setting the ADO Recordset
decimal field value
to 44.56 resulted in an incorrect value of 445600.0000 being
stored when the record set was updated with the
Update
method.
(Bug#39961)
The SQLTablesW
API gave incorrect results.
For example, table name and table type were returned as
NULL
rather than as the correct values.
(Bug#39957)
MyODBC would crash when a character set was being used on the server that was not supported in the client, for example cp1251:
[MySQL][ODBC 5.1 Driver][mysqld-5.0.27-community-nt]Restricted data type attribute violation
The fix causes MyODBC to return an error message instead of crashing. (Bug#39831)
Binding SQL_C_BIT
to an
INTEGER
column did not work.
The sql_get_data()
function only worked
correctly for BOOLEAN
columns that
corresponded to SQL_C_BIT
buffers.
(Bug#39644)
When the SQLTables
method was called
with NULL
passed as the
tablename
parameter, only one row in the
resultset
, with table name of
NULL
was returned, instead of all tables for
the given database.
(Bug#39561)
The SQLGetInfo()
function returned 0 for
SQL_CATALOG_USAGE
information.
(Bug#39560)
MyODBC Driver 5.1.5 was not able to connect if the connection
string parameters contained spaces or tab symbols. For example,
if the SERVER
parameter was specified as
“SERVER= localhost” instead of
“SERVER=localhost” the following error message will
be displayed:
[MySQL][ODBC 5.1 Driver] Unknown MySQL server host ' localhost' (11001).
The pointer passed to the
SQLDriverConnect
method to retrieve the
output connection string length was one greater than it should
have been due to the inclusion of the NULL terminator.
(Bug#38949)
Data-at-execution parameters were not supported during
positioned update. This meant updating a long text field with a
cursor update would erroneously set the value to null. This
would lead to the error Column 'column_name' cannot be
null
while updating the database, even when
column_name
had been assigned a valid nonnull
string.
(Bug#37649)
The SQLDriverConnect
method truncated
the OutputConnectionString
parameter to 52
characters.
(Bug#37278)
The connection string option Enable
Auto-reconnect
did not work. When the connection
failed, it could not be restored, and the errors generated were
the same as if the option had not been selected.
(Bug#37179)
Insertion of data into a LONGTEXT
table field
did not work. If such an attempt was made the corresponding
field would be found to be empty on examination, or contain
random characters.
(Bug#36071)
No result record was returned for
SQLGetTypeInfo
for the
TIMESTAMP
data type. An application would
receive the result return code 100
(SQL_NO_DATA_FOUND)
.
(Bug#30626)
It was not possible to use MySQL Connector/ODBC to connect to a server using SSL. The following error was generated:
Runtime error '-2147467259 (80004005)': [MySQL][ODBC 3.51 Driver]SSL connection error.
When the recordSet.Update
function was called
to update an adLongVarChar
field, the field
was updated but the recordset was immediately lost. This
happened with driver cursors, whether the cursor was opened in
optimistic or pessimistic mode.
When the next update was called the test code would exit with the following error:
-2147467259 : Query-based update failed because the row to update could not be found.
Microsoft Access was not able to read BIGINT
values properly from a table with just two columns of type
BIGINT
and VARCHAR
.
#DELETE
appeared instead of the correct
values.
(Bug#17679)
Bugs fixed:
ODBC TIMESTAMP
string format is
not handled properly by the MyODBC driver. When passing a
TIMESTAMP
or
DATE
to MyODBC, in the ODBC
format: {d <date>} or {ts <timestamp>}, the string
that represents this is copied once into the SQL statement, and
then added again, as an escaped string.
(Bug#37342)
The connector failed to prompt for additional information required to create a DSN-less connection from an application such as Microsoft Excel. (Bug#37254)
SQLDriverConnect
does not return
SQL_NO_DATA
on cancel. The ODBC documentation
specifies that this method should return
SQL_NO_DATA
when the user cancels the dialog
to connect. The connector, however, returns
SQL_ERROR
.
(Bug#36293)
Assigning a string longer than 67 characters to the
TableType
parameter resulted in a buffer
overrun when the SQLTables()
function was
called.
(Bug#36275)
The ODBC connector randomly uses logon information stored in
odbc-profile
, or prompts the user for
connection information and ignores any settings stored in
odbc-profile
.
(Bug#36203)
After having successfully established a connection, a crash
occurs when calling SQLProcedures()
followed by SQLFreeStmt()
, using the ODBC C
API.
(Bug#36069)
Bugs fixed:
Wrong result obtained when using sum()
on a
decimal(8,2)
field type.
(Bug#35920)
The driver installer could not create a new DSN if many other drivers were already installed. (Bug#35776)
The SQLColAttribute()
function returned
SQL_TRUE
when querying the
SQL_DESC_FIXED_PREC_SCALE (SQL_COLUMN_MONEY)
attribute of a DECIMAL
column.
Previously, the correct value of SQL_FALSE
was returned; this is now again the case.
(Bug#35581)
On Linux, SQLGetDiagRec()
returned
SQL_SUCCESS
in cases when it should have
returned SQL_NO_DATA
.
(Bug#33910)
The driver crashes ODBC Administrator on attempting to add a new DSN. (Bug#32057)
Platform specific notes:
Important Change: You must uninstall previous 5.1.x editions of MySQL Connector/ODBC before installing the new version.
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.
Bugs fixed:
Important Change:
In previous versions, the SSL certificate would automatically be
verified when used as part of the MySQL Connector/ODBC connection. The
default mode is now to ignore the verificate of certificates. To
enforce verification of the SSL certificate during connection,
use the SSLVERIFY
DSN parameter, setting the
value to 1.
(Bug#29955, Bug#34648)
Inserting characters to a UTF8 table using surrogate pairs would fail and insert invalid data. (Bug#34672)
Installation of MySQL Connector/ODBC would fail because it was unable to uninstall a previous installed version. The file being requested would match an older release version than any installed version of the connector. (Bug#34522)
Using SqlGetData
in combination with
SQL_C_WCHAR
would return overlapping data.
(Bug#34429)
Descriptor records were not cleared correctly when calling
SQLFreeStmt(SQL_UNBIND)
.
(Bug#34271)
The dropdown selection for databases on a server when creating a DSN was too small. The list size now automatically adjusts up to a maximum size of 20 potential databases. (Bug#33918)
Microsoft Access would be unable to use
DBEngine.RegisterDatabase
to create a DSN
using the MySQL Connector/ODBC driver.
(Bug#33825)
MySQL Connector/ODBC erroneously reported that it supported the
CAST()
and CONVERT()
ODBC
functions for parsing values in SQL statements, which could lead
to bad SQL generation during a query.
(Bug#33808)
Using a linked table in Access 2003 where the table has a
BIGINT
column as the first column
in the table, and is configured as the primary key, shows
#DELETED
for all rows of the table.
(Bug#24535)
Updating a RecordSet
when the query involves
a BLOB
field would fail.
(Bug#19065)
MySQL Connector/ODBC 5.1.2-beta, a new version of the ODBC driver for the MySQL database management system, has been released. This release is the second 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.
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.
Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.
See also Bug#34571.
Functionality added or changed:
Explicit descriptors are implemented. (Bug#32064)
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.
Changed SQL_ATTR_PARAMSET_SIZE
to return an
error until support for it is implemented.
Disabled MYSQL_OPT_SSL_VERIFY_SERVER_CERT
when using an SSL connection.
SQLForeignKeys
uses
INFORMATION_SCHEMA
when it is available on
the server, which allows more complete information to be
returned.
Bugs fixed:
The SSLCIPHER
option would be incorrectly
recorded within the SSL configuration on Windows.
(Bug#33897)
Within the GUI interface, when connecting to a MySQL server on a nonstandard port, the connection test within the GUI would fail. The issue was related to incorrect parsing of numeric values within the DSN when the option was not configured as the last parameter within the DSN. (Bug#33822)
Specifying a nonexistent database name within the GUI dialog would result in an empty list, not an error. (Bug#33615)
When deleting rows from a static cursor, the cursor position would be incorrectly reported. (Bug#33388)
SQLGetInfo()
reported characters for
SQL_SPECIAL_CHARACTERS
that were not encoded
correctly.
(Bug#33130)
Retrieving data from a BLOB
column would fail within SQLGetData
when the
target data type was SQL_C_WCHAR
due to
incorrect handling of the character buffer.
(Bug#32684)
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)
When accessing column data,
FLAG_COLUMN_SIZE_S32
did not limit the octet
length or display size reported for fields, causing problems
with Microsoft Visual FoxPro.
The list of ODBC functions that could have caused failures in
Microsoft software when retrieving the length of
LONGBLOB
or
LONGTEXT
columns
includes:
SQLColumns
SQLColAttribute
SQLColAttributes
SQLDescribeCol
SQLSpecialColumns
(theoretically can
have the same problem)
Dynamic cursors on statements with parameters were not supported. (Bug#11846)
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.
Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.
See also Bug#34571.
Functionality added or changed:
Incompatible Change: Replaced myodbc3i (now myodbc-installer) with MySQL 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 nonthreadsafe 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 MySQL 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)
MySQL 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.
Due to differences with the installation process used on Windows and potential registry corruption, it is recommended that uninstall any existing versions of MySQL Connector/ODBC 5.1.x before upgrading.
See also Bug#34571.
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.
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 behavior 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.
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
MySQL 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 MySQL Connector/ODBC 3.51 installed before installing this version.
Bugs fixed:
You no longer have to have MySQL Connector/ODBC 3.51 installed before installing this version.
MySQL 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 MySQL 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
Bugs fixed:
SQLColAttribute(...SQL_DESC_CASE_SENSITIVE...)
returned SQL_FALSE
for binary types and
SQL_TRUE
for the rest. It should have
returned SQL_TRUE
for binary types, and
SQL_FALSE
for the rest.
(Bug#54212)
SQLColAttribute
for
SQL_DESC_OCTET_LENGTH
returned length
including terminating null byte. It should not have included the
null byte.
(Bug#54206)
If NO_BACKSLASH_ESCAPES
mode was used on a
server, escaping binary data led to server query parsing errors.
(Bug#49029)
Inserting a new record using SQLSetPos
did
not correspond to the database name specified in the
SELECT
statement when querying tables from
databases other than the current one.
SQLSetPos
attempted to do the
INSERT
in the current database, but finished
with a SQL_ERROR
result and “Table does
not exist” message from MySQL Server.
(Bug#41946)
No result record was returned for
SQLGetTypeInfo
for the
TIMESTAMP
data type. An application would
receive the result return code 100
(SQL_NO_DATA_FOUND)
.
(Bug#30626)
Microsoft Access was not able to read BIGINT
values properly from a table with just two columns of type
BIGINT
and VARCHAR
.
#DELETE
appeared instead of the correct
values.
(Bug#17679)
Bugs fixed:
The client program hung when the network connection to the server was interrupted. (Bug#40407)
The connection string option Enable
Auto-reconnect
did not work. When the connection
failed, it could not be restored, and the errors generated were
the same as if the option had not been selected.
(Bug#37179)
It was not possible to use MySQL Connector/ODBC to connect to a server using SSL. The following error was generated:
Runtime error '-2147467259 (80004005)': [MySQL][ODBC 3.51 Driver]SSL connection error.
Functionality added or changed:
There is a new connection option,
FLAG_NO_BINARY_RESULT
. When set this option
disables charset 63 for columns with an empty
org_table
.
(Bug#29402)
Bugs fixed:
When an ADOConnection
is created and
attempts to open a schema with
ADOConnection.OpenSchema
an access
violation occurs in myodbc3.dll
.
(Bug#30770)
When SHOW CREATE TABLE
was
invoked and then the field values read, the result was truncated
and unusable if the table had many rows and indexes.
(Bug#24131)
Bugs fixed:
The SQLColAttribute()
function returned
SQL_TRUE
when querying the
SQL_DESC_FIXED_PREC_SCALE (SQL_COLUMN_MONEY)
attribute of a DECIMAL
column.
Previously, the correct value of SQL_FALSE
was returned; this is now again the case.
(Bug#35581)
The driver crashes ODBC Administrator on attempting to add a new DSN. (Bug#32057)
When accessing column data,
FLAG_COLUMN_SIZE_S32
did not limit the octet
length or display size reported for fields, causing problems
with Microsoft Visual FoxPro.
The list of ODBC functions that could have caused failures in
Microsoft software when retrieving the length of
LONGBLOB
or
LONGTEXT
columns
includes:
SQLColumns
SQLColAttribute
SQLColAttributes
SQLDescribeCol
SQLSpecialColumns
(theoretically can
have the same problem)
Bugs fixed:
Security Enhancement:
Accessing a parameer with the type of
SQL_C_CHAR
, but with a numeric type and a
length of zero, the parameter marker would get stropped from the
query. In addition, an SQL injection was possible if the
parameter value had a nonzero length and was not numeric, the
text would be inserted verbatim.
(Bug#34575)
Important Change:
In previous versions, the SSL certificate would automatically be
verified when used as part of the MySQL Connector/ODBC connection. The
default mode is now to ignore the verificate of certificates. To
enforce verification of the SSL certificate during connection,
use the SSLVERIFY
DSN parameter, setting the
value to 1.
(Bug#29955, Bug#34648)
When using ADO, the count of parameters in a query would always return zero. (Bug#33298)
Using tables with a single quote or other nonstandard characters in the table or column names through ODBC would fail. (Bug#32989)
When using Crystal Reports, table and column names would be truncated to 21 characters, and truncated columns in tables where the truncated name was the duplicated would lead to only a single column being displayed. (Bug#32864)
SQLExtendedFetch()
and
SQLFetchScroll()
ignored the rowset size if
the Don't cache result
DSN option was set.
(Bug#32420)
When using the ODBC SQL_TXN_READ_COMMITTED
option, 'dirty' records would be read from tables as if the
option had not been applied.
(Bug#31959)
When creating a System DSN using the ODBC Administrator on Mac OS X, a User DSN would be created instead. The root cause is a problem with the iODBC driver manager used on Mac OS X. The fix works around this issue.
ODBC Administrator may still be unable to register a System
DSN unless the /Library/ODBC/odbc.ini
file has the correct permissions. You should ensure that the
file is writable by the admin
group.
Calling SQLFetch
or
SQLFetchScroll
would return negative data
lengths when using SQL_C_WCHAR
.
(Bug#31220)
SQLSetParam()
caused memory allocation errors
due to driver manager's mapping of deprecated functions (buffer
length -1).
(Bug#29871)
Static cursor was unable to be used through ADO when dynamic cursors were enabled. (Bug#27351)
Using connection.Execute
to create a record
set based on a table without declaring the cmd option as
adCmdTable
will fail when communicating with
versions of MySQL 5.0.37 and higher. The issue is related to the
way that SQLSTATE
is returned when ADO tries
to confirm the existence of the target object.
(Bug#27158)
Updating a RecordSet
when the query involves
a BLOB
field would fail.
(Bug#19065)
With some connections to MySQL databases using MySQL Connector/ODBC, the connection would mistakenly report 'user cancelled' for accesses to the database information. (Bug#16653)
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:
MySQL 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)
MySQL 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
. MySQL 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 user name 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.30, “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:
Incompatible Change:
The FLAG_DEBUG
option was removed.
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 MySQL 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)
MySQL 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 user ODBC configuration file
(~/Library/ODBC/odbcinst.ini
) instead of
the system /Library/ODBC/odbcinst.ini
. This
was caused because myodbc3i was not honoring
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)
MySQL 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, MySQL 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, MySQL 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
nonalphanumeric 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:
MySQL 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:
MySQL 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)
MySQL 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 MySQL Connector/ODBC option parameters. (Bug#10910)
Added auto-reconnect option to MySQL 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)
MySQL Connector/ODBC may insert the wrong parameter values when using prepared statements under 64-bit Linux. (Bug#22446)
Using MySQL 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
, MySQL 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, MySQL Connector/ODBC and the embedded MySQL server. (Bug#16535)
The SQLDriverConnect()
ODBC method did not
work with recent MySQL 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)
First Beta release. Fixes bugs since 6.3.2.
Bugs fixed:
The MySqlHelper
object did not have an
overloaded version of the ExecuteReader
method that accepted a MySqlConnection
object.
(Bug#54570)
If MySqlDataAdapter
was used with an
INSERT
command where the
VALUES
clause contained an expression with
parentheses in it, and set the
adapter.UpdateBatchSize
parameter to be
greater than one, then the call to
adpater.Update
either generated an exception
or failed to batch the commands, executing each insert
individually.
(Bug#54386)
The method
MySql.Data.Common.QueryNormalizer.CollapseValueList
generated an ArgumentOutOfRangeException
.
(Bug#54152, Bug#53865)
Garbage Collector disposal of a
MySqlConnection
object caused the following
exception:
System.IO.EndOfStreamException: Attempted to read past the end of the stream. MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset, Int32 count) MySql.Data.MySqlClient.MySqlStream.LoadPacket() Outer Exception Reading from the stream has failed. ...
After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:
[MySqlException (0x80004005): There is already an open DataReader associated with this Connection which must be closed first.] MySql.Data.MySqlClient.MySqlCommand.CheckState() +278 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6 Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323 Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit) in ...:13 Forecast.Page_Load(Object sender, EventArgs e) in ...:70 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
The MySQL Connector/NET installation failed due to
machine.config
files not being present in
configuration folders.
MySQL Connector/NET has been changed to skip over configuration folders that
do not contain a machine.config
file.
(Bug#52352)
When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:
A DataTable named \'Procedure Parameters\' already belongs to this DataSet.
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)
First Beta release. Fixes bugs since 6.3.1.
Functionality added or changed:
Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)
MySQL Connector/NET has been changed to include
MySqlDataReader.GetFieldType(string
columnname)
. Further,
MySqlDataReader.GetOrdinal()
now includes the
name of the column in the exception if the column is not found.
(Bug#47467)
Bugs fixed:
MySQL Connector/NET generated an exception when used to read a
TEXT
column containing more than 32767 bytes.
(Bug#54040)
In MySQL Connector/NET, the MySqlConnection.Abort()
method
contained a try...catch
construct, with an
empty catch
block. This meant that any
exception generated at this point would not be caught.
(Bug#52769)
The procedure cache affected the MySQL Connector/NET performance, reducing it
by around 65%. This was due to unnecessary calls of
String.Format()
, related to debug logging.
Even though the logging was disabled the string was still being
formatted, resulting in impaired performance.
(Bug#52475)
If FunctionsReturnString=true
was used in the
connection string, the decimal separator (according to locale)
was not interpreted.
(Bug#52187)
In MySQL Connector/NET, the LoadCharsetMap()
function of
the CharSetMap
class set the following
incorrect mapping:
mapping.Add("latin1", new CharacterSet("latin1", 1));
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
This is because MySQL's latin1
character set
is the same as the windows-cp1252
character
set and it extends the official ISO 8859-1 or IANA latin1.
(Bug#51927)
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)
When calling ExecuteNonQuery
on a command
object, the following exception occurred:
Index and length must refer to a location within the string. Parameter name: length
MySQL Connector/NET 6.3.1 failed to install. (Bug#51407, Bug#51604)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)
Fixes bugs since 6.3.0.
Functionality added or changed:
Connector/NET was not compatible with Visual Studio wizards that used square brackets to delimit symbols.
Connector/NET has been changed to include a new connection
string option Sql Server mode
that supports
use of square brackets to delimit symbols.
(Bug#35852)
Bugs fixed:
Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:
server=localhost;user=root;compress=;database=test;port=3306;password=123456;
The method Command.TrimSemicolons
used
StringBuilder
, and therefore allocated memory
for the query even if it did not need to be trimmed. This led to
excessive memory consumption when executing a number of large
queries.
(Bug#51149)
MySqlCommand.Parameters.Clear()
did not work.
(Bug#50444)
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)
When the UpdateBatchSize
property was set to
a value greater than 1, only the first row was applied to the
database.
(Bug#50123)
When trying to create stored procedures from a SQL script, a
MySqlException
was thrown when attempting to
redefine the DELIMITER
:
MySql.Data.MySqlClient.MySqlException was unhandled Message="You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DELIMITER' at line 1" Source="MySql.Data" ErrorCode=-2147467259 Number=1064 StackTrace: à MySql.Data.MySqlClient.MySqlStream.ReadPacket() à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64& lastInsertId) à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet() à MySql.Data.MySqlClient.MySqlDataReader.NextResult() à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery() à MySql.Data.MySqlClient.MySqlScript.Execute()
Note: The MySqlScript
class has been fixed to
support the delimiter statement as it is found in SQL scripts.
(Bug#46429)
A connection string set in web.config
could
not be reused after Visual Studio 2008 Professional was shut
down. It continued working for the existing controls, but did
not work for new controls added.
(Bug#41629)
First alpha release of 6.3.
Functionality added or changed:
Nested transaction scopes were not supported. MySQL Connector/NET now
implements nested transaction scopes. A per-thread stack of
scopes is maintained, which is necessary in order to handle
nested scopes with the RequiresNew
or
Suppress
options.
(Bug#45098)
Support for MySQL Server 4.1 has been removed from MySQL Connector/NET starting with version 6.3.0. The connector will now throw an exception if you try to connect to a server of version less than 5.0.
Bugs fixed:
When adding a data set in Visual Studio 2008, the following error was generated:
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)
The method MySqlDataReader.GetSchemaTable()
returned 0 in the NumericPrecision
field for
decimal and newdecimal columns.
(Bug#48171)
This release fixes bugs since 6.2.3.
Functionality added or changed:
Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)
Bugs fixed:
The MySqlHelper
object did not have an
overloaded version of the ExecuteReader
method that accepted a MySqlConnection
object.
(Bug#54570)
If MySqlDataAdapter
was used with an
INSERT
command where the
VALUES
clause contained an expression with
parentheses in it, and set the
adapter.UpdateBatchSize
parameter to be
greater than one, then the call to
adpater.Update
either generated an exception
or failed to batch the commands, executing each insert
individually.
(Bug#54386)
The method
MySql.Data.Common.QueryNormalizer.CollapseValueList
generated an ArgumentOutOfRangeException
.
(Bug#54152, Bug#53865)
Garbage Collector disposal of a
MySqlConnection
object caused the following
exception:
System.IO.EndOfStreamException: Attempted to read past the end of the stream. MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset, Int32 count) MySql.Data.MySqlClient.MySqlStream.LoadPacket() Outer Exception Reading from the stream has failed. ...
After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:
[MySqlException (0x80004005): There is already an open DataReader associated with this Connection which must be closed first.] MySql.Data.MySqlClient.MySqlCommand.CheckState() +278 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6 Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323 Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit) in ...:13 Forecast.Page_Load(Object sender, EventArgs e) in ...:70 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
In MySQL Connector/NET, the MySqlConnection.Abort()
method
contained a try...catch
construct, with an
empty catch
block. This meant that any
exception generated at this point would not be caught.
(Bug#52769)
The procedure cache affected the MySQL Connector/NET performance, reducing it
by around 65%. This was due to unnecessary calls of
String.Format()
, related to debug logging.
Even though the logging was disabled the string was still being
formatted, resulting in impaired performance.
(Bug#52475)
If FunctionsReturnString=true
was used in the
connection string, the decimal separator (according to locale)
was not interpreted.
(Bug#52187)
Periodically the session provider threw an
SqlNullValueException
exception. When this
happened, the row within the
my_aspnet_Sessions
table had
locked
always set to '1'. The locked status
never changed back to '0' and the user experienced the exception
on every page, until their browser was closed and reopened
(recreating a new sessionID), or the locked
value was manually changed to '0'.
(Bug#52175)
In MySQL Connector/NET, the LoadCharsetMap()
function of
the CharSetMap
class set the following
incorrect mapping:
mapping.Add("latin1", new CharacterSet("latin1", 1));
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
This is because MySQL's latin1
character set
is the same as the windows-cp1252
character
set and it extends the official ISO 8859-1 or IANA latin1.
(Bug#51927)
When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:
A DataTable named \'Procedure Parameters\' already belongs to this DataSet.
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)
This release fixes bugs since 6.2.2.
Functionality added or changed:
MySQL Connector/NET has been changed to include
MySqlDataReader.GetFieldType(string
columnname)
. Further,
MySqlDataReader.GetOrdinal()
now includes the
name of the column in the exception if the column is not found.
(Bug#47467)
Bugs fixed:
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)
When calling ExecuteNonQuery
on a command
object, the following exception occurred:
Index and length must refer to a location within the string. Parameter name: length
Specifying a connection string where an option had no value generated an error, rather than the value being set to the default. For example, a connection string such as the following would result in an error:
server=localhost;user=root;compress=;database=test;port=3306;password=123456;
The method Command.TrimSemicolons
used
StringBuilder
, and therefore allocated memory
for the query even if it did not need to be trimmed. This led to
excessive memory consumption when executing a number of large
queries.
(Bug#51149)
MySqlCommand.Parameters.Clear()
did not work.
(Bug#50444)
When the MySqlScript.execute()
method was
called, the following exception was generated:
InvalidOperationException : The CommandText property has not been properly initialized.
When using the Compact Framework the following exception occurred when attempting to connect to a MySQL Server:
System.InvalidOperationException was unhandled Message="Timeouts are not supported on this stream."
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)
When the UpdateBatchSize
property was set to
a value greater than 1, only the first row was applied to the
database.
(Bug#50123)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)
MySqlDataReader.GetUInt64
returned an
incorrect value when reading a BIGINT
UNSIGNED
column containing a value greater than
2147483647.
(Bug#49794)
A FormatException
was generated when an empty
string was returned from a stored function.
(Bug#49642)
When trying to create stored procedures from a SQL script, a
MySqlException
was thrown when attempting to
redefine the DELIMITER
:
MySql.Data.MySqlClient.MySqlException was unhandled Message="You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DELIMITER' at line 1" Source="MySql.Data" ErrorCode=-2147467259 Number=1064 StackTrace: à MySql.Data.MySqlClient.MySqlStream.ReadPacket() à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64& lastInsertId) à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet() à MySql.Data.MySqlClient.MySqlDataReader.NextResult() à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery() à MySql.Data.MySqlClient.MySqlScript.Execute()
Note: The MySqlScript
class has been fixed to
support the delimiter statement as it is found in SQL scripts.
(Bug#46429)
Calling a User Defined Function using Entity SQL in the Entity
Framework caused a NullReferenceException
.
(Bug#45277)
A connection string set in web.config
could
not be reused after Visual Studio 2008 Professional was shut
down. It continued working for the existing controls, but did
not work for new controls added.
(Bug#41629)
First GA release of 6.2. This release fixes bugs since 6.2.1.
Bugs fixed:
When adding a data set in Visual Studio 2008, the following error was generated:
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)
The method MySqlDataReader.GetSchemaTable()
returned 0 in the NumericPrecision
field for
decimal and newdecimal columns.
(Bug#48171)
MySQL Connector/NET generated an invalid operation exception during a transaction rollback:
System.InvalidOperationException: Connection must be valid and open to rollback transaction at MySql.Data.MySqlClient.MySqlTransaction.Rollback() at MySql.Data.MySqlClient.MySqlConnection.CloseFully() at MySql.Data.MySqlClient.MySqlPromotableTransaction.System.Transactions.IPromotableSinglePhaseNotification.Rollback(SinglePhaseEnlistment singlePhaseEnlistment) ...
Connection objects were not garbage collected when not in use. (Bug#31996)
This release fixes bugs since 6.2.0.
Functionality added or changed:
The MySqlParameter
class now has a property
named PossibleValues
. This property is NULL
unless the parameter is created by
MySqlCommandBuilder.DeriveParameters
.
Further, it will be NULL unless the parameter is of type enum or
set - in this case it will be a list of strings that are the
possible values for the column. This feature is designed as an
aid to the developer.
(Bug#48586)
Prior to MySQL Connector/NET 6.2,
MySqlCommand.CommandTimeout
included user
processing time, that is processing time not related to direct
use of the connector. Timeout was implemented through a .NET
Timer, that triggered after CommandTimeout
seconds.
MySQL Connector/NET 6.2 introduced timeouts that are aligned with how
Microsoft handles SqlCommand.CommandTimeout
.
This property is the cumulative timeout for all network reads
and writes during command execution or processing of the
results. A timeout can still occur in the
MySqlReader.Read
method after the first row
is returned, and does not include user processing time, only IO
operations.
Further details on this can be found in the relevant Microsoft documentation.
Starting with MySQL Connector/NET 6.2, there is a background job that runs every three minutes and removes connections from pool that have been idle (unused) for more than three minutes. The pool cleanup frees resources on both client and server side. This is because on the client side every connection uses a socket, and on the server side every connection uses a socket and a thread.
Prior to this change, connections were never removed from the pool, and the pool always contained the peak number of open connections. For example, a web application that peaked at 1000 concurrent database connections would consume 1000 threads and 1000 open sockets at the server, without ever freeing up those resources from the connection pool.
MySQL Connector/NET now supports the processing of certificates when connecting to an SSL-enabled MySQL Server. For further information see the connection string option SSL Mode in the section Section 20.2.6, “Connector/NET Connection String Options Reference” and the tutorial Section 20.2.4.7, “Tutorial: Using SSL with MySQL Connector/NET”.
Bugs fixed:
Cloning of MySqlCommand
was not typesafe. To
clone a MySqlCommand
it was necessary to do:
MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
MySQL Connector/NET was changed so that it was possible to do:
MySqlCommand clone = comm.Clone();
When used, the Encrypt
connection string
option caused a “Keyword not supported” exception
to be generated.
This option is in fact obsolete, and the option SSL Mode should
be used instead. Although the Encrypt
option
has been fixed so that it does not generate an exception, it
will be removed completely in version 6.4.
(Bug#48290)
When building the MySql.Data
project with
.NET Framework 3.5 installed, the following build output was
displayed:
Project file contains ToolsVersion="4.0", which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion="3.5".
The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug#48271)
It was not possible to retrieve a value from a MySQL server
table, if the value was larger than that supported by the .NET
type System.Decimal
.
MySQL Connector/NET was changed to expose the MySqlDecimal
type, along with the supporting method
GetMySqlDecimal
.
(Bug#48100)
An entity model created from a schema containing a table with a
column of type UNSIGNED BIGINT
and a view of
the table did not behave correctly. When an entity was created
and mapped to the view, the column that was of type
UNSIGNED BIGINT
was displayed as
BIGINT
.
(Bug#47872)
MySQL Connector/NET session support did not work with MySQL Server versions
prior to 5.0, as the Session Provider used a call to
TIMESTAMPDIFF
, which was not available on
servers prior to 5.0.
(Bug#47219)
The first alpha release of 6.2.
Bugs fixed:
When using a BINARY(16)
column to represent a
GUID and having specified “old guids = true” in the
connection string, the values were returned correctly until a
null value was encountered in that field. After the null value
was encountered a format exception was thrown with the following
message:
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
The Session Provider created invalid “session expires” on a random basis.
This was due to the fact that the Session Provider was
incorrectly reading from the root
web.config
, rather than from the
application specific web.config
.
(Bug#47815)
When loading the MySQLClient-mono.sln
file
included with the Connector/NET source into Mono Develop, the
following error occurred:
/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22): Unsupported or unrecognized project: '/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'
If the file was modified to remove this problem, then attempting to build the solution generated the following error:
/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46): error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an override but no suitable property found to override
This release fixes bugs since 6.1.4.
Bugs fixed:
The MySqlHelper
object did not have an
overloaded version of the ExecuteReader
method that accepted a MySqlConnection
object.
(Bug#54570)
If MySqlDataAdapter
was used with an
INSERT
command where the
VALUES
clause contained an expression with
parentheses in it, and set the
adapter.UpdateBatchSize
parameter to be
greater than one, then the call to
adpater.Update
either generated an exception
or failed to batch the commands, executing each insert
individually.
(Bug#54386)
The method
MySql.Data.Common.QueryNormalizer.CollapseValueList
generated an ArgumentOutOfRangeException
.
(Bug#54152, Bug#53865)
Garbage Collector disposal of a
MySqlConnection
object caused the following
exception:
System.IO.EndOfStreamException: Attempted to read past the end of the stream. MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset, Int32 count) MySql.Data.MySqlClient.MySqlStream.LoadPacket() Outer Exception Reading from the stream has failed. ...
After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:
[MySqlException (0x80004005): There is already an open DataReader associated with this Connection which must be closed first.] MySql.Data.MySqlClient.MySqlCommand.CheckState() +278 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6 Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323 Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit) in ...:13 Forecast.Page_Load(Object sender, EventArgs e) in ...:70 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:
A DataTable named \'Procedure Parameters\' already belongs to this DataSet.
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)
This release fixes bugs since 6.1.3.
Functionality added or changed:
Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)
MySQL Connector/NET has been changed to include
MySqlDataReader.GetFieldType(string
columnname)
. Further,
MySqlDataReader.GetOrdinal()
now includes the
name of the column in the exception if the column is not found.
(Bug#47467)
Bugs fixed:
In MySQL Connector/NET, the MySqlConnection.Abort()
method
contained a try...catch
construct, with an
empty catch
block. This meant that any
exception generated at this point would not be caught.
(Bug#52769)
If FunctionsReturnString=true
was used in the
connection string, the decimal separator (according to locale)
was not interpreted.
(Bug#52187)
In MySQL Connector/NET, the LoadCharsetMap()
function of
the CharSetMap
class set the following
incorrect mapping:
mapping.Add("latin1", new CharacterSet("latin1", 1));
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
This is because MySQL's latin1
character set
is the same as the windows-cp1252
character
set and it extends the official ISO 8859-1 or IANA latin1.
(Bug#51927)
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)
When calling ExecuteNonQuery
on a command
object, the following exception occurred:
Index and length must refer to a location within the string. Parameter name: length
The method Command.TrimSemicolons
used
StringBuilder
, and therefore allocated memory
for the query even if it did not need to be trimmed. This led to
excessive memory consumption when executing a number of large
queries.
(Bug#51149)
MySqlCommand.Parameters.Clear()
did not work.
(Bug#50444)
When the MySqlScript.execute()
method was
called, the following exception was generated:
InvalidOperationException : The CommandText property has not been properly initialized.
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)
When the UpdateBatchSize
property was set to
a value greater than 1, only the first row was applied to the
database.
(Bug#50123)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)
MySqlDataReader.GetUInt64
returned an
incorrect value when reading a BIGINT
UNSIGNED
column containing a value greater than
2147483647.
(Bug#49794)
A FormatException
was generated when an empty
string was returned from a stored function.
(Bug#49642)
When adding a data set in Visual Studio 2008, the following error was generated:
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)
The method MySqlDataReader.GetSchemaTable()
returned 0 in the NumericPrecision
field for
decimal and newdecimal columns.
(Bug#48171)
When trying to create stored procedures from a SQL script, a
MySqlException
was thrown when attempting to
redefine the DELIMITER
:
MySql.Data.MySqlClient.MySqlException was unhandled Message="You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DELIMITER' at line 1" Source="MySql.Data" ErrorCode=-2147467259 Number=1064 StackTrace: à MySql.Data.MySqlClient.MySqlStream.ReadPacket() à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64& lastInsertId) à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet() à MySql.Data.MySqlClient.MySqlDataReader.NextResult() à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery() à MySql.Data.MySqlClient.MySqlScript.Execute()
Note: The MySqlScript
class has been fixed to
support the delimiter statement as it is found in SQL scripts.
(Bug#46429)
Calling a User Defined Function using Entity SQL in the Entity
Framework caused a NullReferenceException
.
(Bug#45277)
A connection string set in web.config
could
not be reused after Visual Studio 2008 Professional was shut
down. It continued working for the existing controls, but did
not work for new controls added.
(Bug#41629)
This release fixes bugs since 6.1.2.
Bugs fixed:
Cloning of MySqlCommand
was not typesafe. To
clone a MySqlCommand
it was necessary to do:
MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
MySQL Connector/NET was changed so that it was possible to do:
MySqlCommand clone = comm.Clone();
When building the MySql.Data
project with
.NET Framework 3.5 installed, the following build output was
displayed:
Project file contains ToolsVersion="4.0", which is not supported by this version of MSBuild. Treating the project as if it had ToolsVersion="3.5".
The project had been created using the .NET Framework 4.0, which was beta, instead of using the 3.5 framework. (Bug#48271)
If MySqlConnection.GetSchema
was called for
"Indexes" on a table named “b`a`d” as follows:
DataTable schemaPrimaryKeys = connection.GetSchema( "Indexes", new string[] { null, schemaName, "b`a`d"});
Then the following exception was generated:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'a`d`' at line 1
It was not possible to retrieve a value from a MySQL server
table, if the value was larger than that supported by the .NET
type System.Decimal
.
MySQL Connector/NET was changed to expose the MySqlDecimal
type, along with the supporting method
GetMySqlDecimal
.
(Bug#48100)
For some character sets such as UTF-8, a CHAR
column would sometimes be incorrectly interpreted as a
GUID
by MySQL Connector/NET.
MySQL Connector/NET was changed so that a column would only be interpreted as
a GUID
if it had a character length of 36, as
opposed to a byte length of 36.
(Bug#47985)
When using a BINARY(16)
column to represent a
GUID and having specified “old guids = true” in the
connection string, the values were returned correctly until a
null value was encountered in that field. After the null value
was encountered a format exception was thrown with the following
message:
Guid should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx).
An entity model created from a schema containing a table with a
column of type UNSIGNED BIGINT
and a view of
the table did not behave correctly. When an entity was created
and mapped to the view, the column that was of type
UNSIGNED BIGINT
was displayed as
BIGINT
.
(Bug#47872)
The Session Provider created invalid “session expires” on a random basis.
This was due to the fact that the Session Provider was
incorrectly reading from the root
web.config
, rather than from the
application specific web.config
.
(Bug#47815)
Attempting to build MySQL Connector/NET 6.1 MySQL.Data
from source code on Windows failed with the following error:
...\clones\6.1\MySql.Data\Provider\Source\NativeDriver.cs(519,29): error CS0122: 'MySql.Data.MySqlClient.MySqlPacket.MySqlPacket()' is inaccessible due to its protection level
When tables were auto created for the Session State Provider they were set to use the MySQL Server's default collation, rather than the default collation set for the containing database. (Bug#47332)
When loading the MySQLClient-mono.sln
file
included with the Connector/NET source into Mono Develop, the
following error occurred:
/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22): Unsupported or unrecognized project: '/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'
If the file was modified to remove this problem, then attempting to build the solution generated the following error:
/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46): error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an override but no suitable property found to override
This is the first GA release of 6.1.
Bugs fixed:
The MySQL Connector/NET Session State Provider truncated session data to
64KB, due to its column types being set to
BLOB
.
(Bug#47339)
MySQL Connector/NET generated the following exception when using the Session State provider:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MINUTEWHERE SessionId = 'dtmgga55x35oi255nrfrxe45' AND ApplicationId = 1 AND Loc' at line 1 Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code. Exception Details: MySql.Data.MySqlClient.MySqlException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'MINUTEWHERE SessionId = 'dtmgga55x35oi255nrfrxe45' AND ApplicationId = 1 AND Loc' at line 1
If an error occurred during connection to a MySQL Server,
deserializing the error message from the packet buffer caused a
NullReferenceException
to be thrown. When the
method MySqlPacket::ReadString()
attempted to
retrieve the error message, the following line of code threw the
exception:
string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);
This was due to the fact that the encoding field had not been initialized correctly. (Bug#46844)
Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug#44985)
MySQL Connector/NET did not time out correctly. The command timeout was set to 30 secs, but MySQL Connector/NET hung for several hours. (Bug#43761)
This is the first Beta release of 6.1.
Bugs fixed:
In the MySqlDataReader
class the
GetSByte
function returned a
byte
value instead of an
sbyte
value.
(Bug#46620)
The MySQL Connector/NET Profile Provider,
MySql.Web.Profile.MySQLProfileProvider
,
generated an error when running on Mono. When an attempt was
made to save a string in Profile.Name
the
string was not saved to the
my_aspnet_Profiles
table. If an attempt was
made to force the save with Profile.Save()
the following error was generated:
Server Error in '/mono' Application -------------------------------------------------------------------------------- The requested feature is not implemented. Description: HTTP 500. Error processing request. Stack Trace: System.NotImplementedException: The requested feature is not implemented. at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction (System.Transactions.Transaction transaction) [0x00000] at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues (System.Configuration.SettingsContext context, System.Configuration.SettingsPropertyValueCollection collection) [0x00000] -------------------------------------------------------------------------------- Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433
An exception was generated when using
TIMESTAMP
columns with the Entity Framework.
(Bug#46311)
MySQL Connector/NET sometimes hung, without generating an exception. This
happened if a read from a stream failed returning a 0, causing
the code in LoadPacket()
to enter an infinite
loop.
(Bug#46308)
When using MySQL Connector/NET 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:
connection.GetSchema("Columns", ...);
The exception generated was:
'connection.GetSchema("Columns")' threw an exception of type 'System.ArgumentException'System.Data.DataTable {System.ArgumentException} base{"Input string was not in a correct format.Couldn't store <'Select'> in NUMERIC_PRECISION Column. Expected type is UInt64."}System.Exception {System.ArgumentException}
The MySQL Connector/NET method
StoredProcedure.GetParameters(string)
ignored
the programmer's setting of the
UseProcedureBodies
option. This broke any
application for which the application's parameter names did not
match the parameter names in the Stored Procedure, resulting in
an ArgumentException
with the message
“Parameter 'foo' not found in the collection.” and
the following stack trace:
MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C# MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25 bytesC# MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha vior behavior = SequentialAccess) Line 405 + 0xb bytesC# MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC# System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System .Data.CommandBehavior behavior) + 0xb bytes System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) + 0x83 bytes System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command, System.Data.CommandBehavior behavior) + 0x120 bytes System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) + 0x5f bytes
Conversion of MySQL TINYINT(1)
to
boolean
failed.
(Bug#46205, Bug#46359, Bug#41953)
When populating a MySQL database table in Visual Studio using
the Table Editor, if a VARCHAR(10)
column was
changed to a VARCHAR(20)
column an exception
was generated:
SystemArgumentException: DataGridViewComboBoxCell value is not valid. To replace this default dialog please handle the DataError Event.
The Entity Framework provider was not calling
DBSortExpression
correctly when the
Skip
and Take
methods were
used, such as in the following statement:
TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();
This resulted in the data being unsorted. (Bug#45723)
The MySQL Connector/NET 6.0.4 installer failed with an error. The error message generated was:
There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.
When Bug#45474)
was clicked to acknowledge the error the installer exited. (
Calling the Entity Framework SaveChanges()
method of any MySQL ORM Entity with a column type
TIME
, generated an error message:
Unknown PrimitiveKind Time
Insert into two tables failed when using the Entity Framework. The exception generated was:
The value given is not an instance of type 'Edm.Int32'
Errors occurred when using the Entity Framework with cultures
that used a comma as the decimal separator. This was because the
formatting for SINGLE
,
DOUBLE
and DECIMAL
values
was not handled correctly.
(Bug#44455)
When attempting to connect to MySQL using the Compact Framework
version of MySQL Connector/NET, an
IndexOutOfRangeException
exception was
generated on trying to open the connection.
(Bug#43736)
When reading data, such as with a
MySqlDataAdapter
on a
MySqlConnection
, MySQL Connector/NET could potentially
enter an infinite loop in
CompressedStream.ReadNextpacket()
if
compression was enabled.
(Bug#43678)
An error occurred when building MySQL Connector/NET from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.
When an attempt was made to build (for example) the MySQL Connector/NET 5.2 branch using the command:
$ nant -buildfile:Client.build
The following error occurred:
BUILD FAILED Error loading buildfile. Encoding name 'Windows-1252' not supported. Parameter name: name
MySQL Connector/NET CHM documentation stated that MySQL Server 3.23 was supported. (Bug#42110)
In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.
Note: The bugfix introduced a new keepalive
parameter, which prevents disconnects by sending an empty TCP
packet after a specified timeout.
(Bug#40684)
Calling a Stored Procedure with an output parameter through MySQL Connector/NET resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug#36027)
This is the first Alpha release of 6.1.
Functionality added or changed:
Changed GUID type - The backend representation of a guid type
has been changed to be CHAR(36). This is so you can use the
server UUID() function to populate a GUID table. UUID generates
a 36 character string. Developers of older applications can add
old guids=true
to the connection string and
the old BINARY(16) type will be used instead.
Support for native output parameters - This is supported when connected to a server that supports native output parameters. This includes servers as of 5.5.3 and 6.0.8.
Session State Provider - This allows you to store the state of your website in a MySQL server.
Website Configuration Dialog - This is a new wizard that is activated by clicking a button on the toolbar at the top of the Visual Studio Solution Explorer. It works in conjunction with the ASP.Net administration pages, making it easier to activate and set advanced options for the different MySQL web providers included.
Fixes bugs since 6.0.6.
Bugs fixed:
The MySqlHelper
object did not have an
overloaded version of the ExecuteReader
method that accepted a MySqlConnection
object.
(Bug#54570)
If MySqlDataAdapter
was used with an
INSERT
command where the
VALUES
clause contained an expression with
parentheses in it, and set the
adapter.UpdateBatchSize
parameter to be
greater than one, then the call to
adpater.Update
either generated an exception
or failed to batch the commands, executing each insert
individually.
(Bug#54386)
The method
MySql.Data.Common.QueryNormalizer.CollapseValueList
generated an ArgumentOutOfRangeException
.
(Bug#54152, Bug#53865)
Garbage Collector disposal of a
MySqlConnection
object caused the following
exception:
System.IO.EndOfStreamException: Attempted to read past the end of the stream. MySql.Data.MySqlClient.MySqlStream.ReadFully(Stream stream, Byte[] buffer, Int32 offset, Int32 count) MySql.Data.MySqlClient.MySqlStream.LoadPacket() Outer Exception Reading from the stream has failed. ...
After a timeout exception, if an attempt was made to reuse a connection returned to the connection pool the following exception was generated:
[MySqlException (0x80004005): There is already an open DataReader associated with this Connection which must be closed first.] MySql.Data.MySqlClient.MySqlCommand.CheckState() +278 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) +43 MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() +6 Controls.SimpleCommand.ExecuteReader(String SQL) in ...:323 Albums.GetImagesByAlbum(SimpleCommand Cmd, Int32 iAlbum, String Order, String Limit) in ...:13 Forecast.Page_Load(Object sender, EventArgs e) in ...:70 System.Web.UI.Control.OnLoad(EventArgs e) +99 System.Web.UI.Control.LoadRecursive() +50 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +627
When an application was subjected to increased concurrent load, MySQL Connector/NET generated the following error when calling stored procedures:
A DataTable named \'Procedure Parameters\' already belongs to this DataSet.
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)
Fixes bugs since 6.0.5.
Functionality added or changed:
Procedure cacheing had a problem whereby if you created a procedure, dropped it, and recreated it with a different number of parameters an exception was generated.
MySQL Connector/NET has been changed so that if the procedure is recreated with a different number of parameters, it will still be recognized. (Bug#52562)
MySQL Connector/NET has been changed to include
MySqlDataReader.GetFieldType(string
columnname)
. Further,
MySqlDataReader.GetOrdinal()
now includes the
name of the column in the exception if the column is not found.
(Bug#47467)
Bugs fixed:
In MySQL Connector/NET, the MySqlConnection.Abort()
method
contained a try...catch
construct, with an
empty catch
block. This meant that any
exception generated at this point would not be caught.
(Bug#52769)
If FunctionsReturnString=true
was used in the
connection string, the decimal separator (according to locale)
was not interpreted.
(Bug#52187)
In MySQL Connector/NET, the LoadCharsetMap()
function of
the CharSetMap
class set the following
incorrect mapping:
mapping.Add("latin1", new CharacterSet("latin1", 1));
This meant that, for example, the Euro sign was not handled correctly.
The correct mapping should have been:
mapping.Add("latin1", new CharacterSet("windows-1252", 1));
This is because MySQL's latin1
character set
is the same as the windows-cp1252
character
set and it extends the official ISO 8859-1 or IANA latin1.
(Bug#51927)
A non-terminated string in SQL threw a CLR exception rather than a syntax exception. (Bug#51788)
When calling ExecuteNonQuery
on a command
object, the following exception occurred:
Index and length must refer to a location within the string. Parameter name: length
The method Command.TrimSemicolons
used
StringBuilder
, and therefore allocated memory
for the query even if it did not need to be trimmed. This led to
excessive memory consumption when executing a number of large
queries.
(Bug#51149)
MySqlCommand.Parameters.Clear()
did not work.
(Bug#50444)
When the MySqlScript.execute()
method was
called, the following exception was generated:
InvalidOperationException : The CommandText property has not been properly initialized.
Binary Columns were not displayed in the Query Builder of Visual Studio. (Bug#50171)
When the UpdateBatchSize
property was set to
a value greater than 1, only the first row was applied to the
database.
(Bug#50123)
When using table per type inheritance and listing the contents of the parent table, the result of the query was a list of child objects, even though there was no related child record with the same parent Id. (Bug#49850)
MySqlDataReader.GetUInt64
returned an
incorrect value when reading a BIGINT
UNSIGNED
column containing a value greater than
2147483647.
(Bug#49794)
A FormatException
was generated when an empty
string was returned from a stored function.
(Bug#49642)
When adding a data set in Visual Studio 2008, the following error was generated:
Relations couldn't be addded. Column 'REFERENCED_TABLE_CATALOG' does not belong to table.
This was due to a 'REFERENCED_TABLE_CATALOG' column not being included in the foreign keys collection. (Bug#48974)
Attempting to execute a load data local infile on a file where the user did not have write permissions, or the file was open in an editor gave an access denied error. (Bug#48944)
The method MySqlDataReader.GetSchemaTable()
returned 0 in the NumericPrecision
field for
decimal and newdecimal columns.
(Bug#48171)
When trying to create stored procedures from a SQL script, a
MySqlException
was thrown when attempting to
redefine the DELIMITER
:
MySql.Data.MySqlClient.MySqlException was unhandled Message="You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DELIMITER' at line 1" Source="MySql.Data" ErrorCode=-2147467259 Number=1064 StackTrace: à MySql.Data.MySqlClient.MySqlStream.ReadPacket() à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64& lastInsertId) à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet() à MySql.Data.MySqlClient.MySqlDataReader.NextResult() à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery() à MySql.Data.MySqlClient.MySqlScript.Execute()
Note: The MySqlScript
class has been fixed to
support the delimiter statement as it is found in SQL scripts.
(Bug#46429)
Calling a User Defined Function using Entity SQL in the Entity
Framework caused a NullReferenceException
.
(Bug#45277)
A connection string set in web.config
could
not be reused after Visual Studio 2008 Professional was shut
down. It continued working for the existing controls, but did
not work for new controls added.
(Bug#41629)
This is a new release, fixing recently discovered bugs.
Bugs fixed:
Cloning of MySqlCommand
was not typesafe. To
clone a MySqlCommand
it was necessary to do:
MySqlCommand clone = (MySqlCommand)((ICloneable)comm).Clone();
MySQL Connector/NET was changed so that it was possible to do:
MySqlCommand clone = comm.Clone();
If MySqlConnection.GetSchema
was called for
"Indexes" on a table named “b`a`d” as follows:
DataTable schemaPrimaryKeys = connection.GetSchema( "Indexes", new string[] { null, schemaName, "b`a`d"});
Then the following exception was generated:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'a`d`' at line 1
It was not possible to retrieve a value from a MySQL server
table, if the value was larger than that supported by the .NET
type System.Decimal
.
MySQL Connector/NET was changed to expose the MySqlDecimal
type, along with the supporting method
GetMySqlDecimal
.
(Bug#48100)
An entity model created from a schema containing a table with a
column of type UNSIGNED BIGINT
and a view of
the table did not behave correctly. When an entity was created
and mapped to the view, the column that was of type
UNSIGNED BIGINT
was displayed as
BIGINT
.
(Bug#47872)
When loading the MySQLClient-mono.sln
file
included with the Connector/NET source into Mono Develop, the
following error occurred:
/home/tbedford/connector-net-src/6.1/MySQLClient-mono.sln(22): Unsupported or unrecognized project: '/home/tbedford/connector-net-src/6.1/Installer/Installer.wixproj'
If the file was modified to remove this problem, then attempting to build the solution generated the following error:
/home/tbedford/connector-net-src/6.1/MySql.Data/Provider/Source/Connection.cs(280,46): error CS0115: `MySql.Data.MySqlClient.MySqlConnection.DbProviderFactory' is marked as an override but no suitable property found to override
If an error occurred during connection to a MySQL Server,
deserializing the error message from the packet buffer caused a
NullReferenceException
to be thrown. When the
method MySqlPacket::ReadString()
attempted to
retrieve the error message, the following line of code threw the
exception:
string s = encoding.GetString(bits, (int)buffer.Position, end - (int)buffer.Position);
This was due to the fact that the encoding field had not been initialized correctly. (Bug#46844)
In the MySqlDataReader
class the
GetSByte
function returned a
byte
value instead of an
sbyte
value.
(Bug#46620)
The MySQL Connector/NET Profile Provider,
MySql.Web.Profile.MySQLProfileProvider
,
generated an error when running on Mono. When an attempt was
made to save a string in Profile.Name
the
string was not saved to the
my_aspnet_Profiles
table. If an attempt was
made to force the save with Profile.Save()
the following error was generated:
Server Error in '/mono' Application -------------------------------------------------------------------------------- The requested feature is not implemented. Description: HTTP 500. Error processing request. Stack Trace: System.NotImplementedException: The requested feature is not implemented. at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction (System.Transactions.Transaction transaction) [0x00000] at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues (System.Configuration.SettingsContext context, System.Configuration.SettingsPropertyValueCollection collection) [0x00000] -------------------------------------------------------------------------------- Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433
An exception was generated when using
TIMESTAMP
columns with the Entity Framework.
(Bug#46311)
MySQL Connector/NET sometimes hung, without generating an exception. This
happened if a read from a stream failed returning a 0, causing
the code in LoadPacket()
to enter an infinite
loop.
(Bug#46308)
When using MySQL Connector/NET 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:
connection.GetSchema("Columns", ...);
The exception generated was:
'connection.GetSchema("Columns")' threw an exception of type 'System.ArgumentException'System.Data.DataTable {System.ArgumentException} base{"Input string was not in a correct format.Couldn't store <'Select'> in NUMERIC_PRECISION Column. Expected type is UInt64."}System.Exception {System.ArgumentException}
The MySQL Connector/NET method
StoredProcedure.GetParameters(string)
ignored
the programmer's setting of the
UseProcedureBodies
option. This broke any
application for which the application's parameter names did not
match the parameter names in the Stored Procedure, resulting in
an ArgumentException
with the message
“Parameter 'foo' not found in the collection.” and
the following stack trace:
MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C# MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25 bytesC# MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha vior behavior = SequentialAccess) Line 405 + 0xb bytesC# MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC# System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System .Data.CommandBehavior behavior) + 0xb bytes System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) + 0x83 bytes System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command, System.Data.CommandBehavior behavior) + 0x120 bytes System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) + 0x5f bytes
Conversion of MySQL TINYINT(1)
to
boolean
failed.
(Bug#46205, Bug#46359, Bug#41953)
When populating a MySQL database table in Visual Studio using
the Table Editor, if a VARCHAR(10)
column was
changed to a VARCHAR(20)
column an exception
was generated:
SystemArgumentException: DataGridViewComboBoxCell value is not valid. To replace this default dialog please handle the DataError Event.
In MySQL Connector/NET 6.0.4 using GetProcData
generated
an error because the parameters
data table
was only created if MySQL Server was at least version 6.0.6, or
if the UseProcedureBodies
connection string
option was set to true.
Also the DeriveParameters
command generated a
null reference exception. This was because the
parameters
data table, which was null, was
used in a for each
loop.
(Bug#45952)
The Entity Framework provider was not calling
DBSortExpression
correctly when the
Skip
and Take
methods were
used, such as in the following statement:
TestModel.tblquarantine.OrderByDescending(q => q.MsgDate).Skip(100).Take(100).ToList();
This resulted in the data being unsorted. (Bug#45723)
The EscapeString
code carried out escaping by
calling string.Replace
multiple times. This
resulted in a performance bottleneck, as for every line a new
string was allocated and another was disposed of by the garbage
collector.
(Bug#45699)
Adding the Allow Batch=False
option to the
connection string caused MySQL Connector/NET to generate the error:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'SET character_set_results=NULL' at line 1
The MySQL Connector/NET 6.0.4 installer failed with an error. The error message generated was:
There is a problem with this Windows Installer package. A DLL required for this install to complete could not be run. Contact your support personnel or package vendor.
When Bug#45474)
was clicked to acknowledge the error the installer exited. (
A MySQL Connector/NET test program that connected to MySQL Server using the
connection string option compress=true
crashed, but only when running on Mono. The program worked as
expected when running on Microsoft Windows.
This was due to a bug in Mono. MySQL Connector/NET was modified to avoid
using WeakReferences
in the
Compressed
stream class, which was causing
the crash.
(Bug#45463)
Calling the Entity Framework SaveChanges()
method of any MySQL ORM Entity with a column type
TIME
, generated an error message:
Unknown PrimitiveKind Time
Insert into two tables failed when using the Entity Framework. The exception generated was:
The value given is not an instance of type 'Edm.Int32'
Input parameters were missing from Stored Procedures when using them with ADO.NET Data Entities. (Bug#44985)
Errors occurred when using the Entity Framework with cultures
that used a comma as the decimal separator. This was because the
formatting for SINGLE
,
DOUBLE
and DECIMAL
values
was not handled correctly.
(Bug#44455)
When attempting to connect to MySQL using the Compact Framework
version of MySQL Connector/NET, an
IndexOutOfRangeException
exception was
generated on trying to open the connection.
(Bug#43736)
When reading data, such as with a
MySqlDataAdapter
on a
MySqlConnection
, MySQL Connector/NET could potentially
enter an infinite loop in
CompressedStream.ReadNextpacket()
if
compression was enabled.
(Bug#43678)
An error occurred when building MySQL Connector/NET from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.
When an attempt was made to build (for example) the MySQL Connector/NET 5.2 branch using the command:
$ nant -buildfile:Client.build
The following error occurred:
BUILD FAILED Error loading buildfile. Encoding name 'Windows-1252' not supported. Parameter name: name
After a Reference to "C:\Program Files\MySQL\MySQL Connector Net 5.2.4\Compact Framework\MySql.Data.CF.dll" was added to a Windows Mobile 5.0 project, the project then failed to build, generating a Microsoft Visual C# compiler error.
The error generated was:
Error 2 The type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute' has no constructors defined MysqlTest Error 3 Internal Compiler Error (0xc0000005 at address 5A7E3714): likely culprit is 'COMPILE'.
MySQL Connector/NET CHM documentation stated that MySQL Server 3.23 was supported. (Bug#42110)
In the case of long network inactivity, especially when connection pooling was used, connections were sometimes dropped, for example, by firewalls.
Note: The bugfix introduced a new keepalive
parameter, which prevents disconnects by sending an empty TCP
packet after a specified timeout.
(Bug#40684)
MySQL Connector/NET generated the following exception:
System.NullReferenceException: Object reference not set to an instance of an object. bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject) bei System.Threading._TimerCallback.TimerCallback_Context(Object state) bei System.Threading.ExecutionContext.runTryCode(Object userData) bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading._TimerCallback.PerformTimerCallback(Object state)
Calling a Stored Procedure with an output parameter through MySQL Connector/NET resulted in a memory leak. Calling the same Stored Procedure without an output parameter did not result in a memory leak. (Bug#36027)
Using a DataAdapter
with a linked
MySqlCommandBuilder
the following exception
was thrown when trying to call da.Update(DataRow[]
rows)
:
Connection must be valid and open
This is the first post-GA release, fixing recently discovered bugs.
Bugs fixed:
If a certain socket exception occurred when trying to establish a MySQL database connection, MySQL Connector/NET displayed an exception message that appeared to be unrelated to the underlying problem. This masked the problem and made diagnosing problems more difficult.
For example, if, when establishing a database connection via TCP/IP, Windows on the local machine allocated an ephemeral port that conflicted with a socket address still in use, then Windows/.NET would throw a socket exception with the following error text:
Only one usage of each socket address (protocol/network address/port) is normally
permitted IP ADDRESS/PORT
.
However, MySQL Connector/NET masked this socket exception and displayed an exception with the following text:
Unable to connect to any of the specified MySQL hosts.
A SQL query string containing an escaped backslash caused an exception to be generated:
Index and length must refer to a location within the string. Parameter name: length at System.String.InternalSubStringWithChecks(Int32 startIndex, Int32 length, Boolean fAlwaysCopy) at MySql.Data.MySqlClient.MySqlTokenizer.NextParameter() at MySql.Data.MySqlClient.Statement.InternalBindParameters(String sql, MySqlParameterCollection parameters, MySqlPacket packet) at MySql.Data.MySqlClient.Statement.BindParameters() at MySql.Data.MySqlClient.PreparableStatement.Execute() at MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) at MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery()
The Microsoft Visual Studio solution file
MySQL-VS2005.sln
was invalid. Several
projects could not be loaded and thus it was not possible to
build MySQL Connector/NET from source.
(Bug#44822)
The Data Set editor generated an error when attempts were made to modify insert, update or delete commands:
Error in WHERE clause near '@'. Unable to parse query text.
The DataReader in MySQL Connector/NET 6.0.3 considered a BINARY(16) field as a GUID with a length of 16. (Bug#44507)
When creating a new DataSet the following error was generated:
Failed to open a connection to database. Cannot load type with name 'MySQL.Data.VisualStudio.StoredProcedureColumnEnumerator'
The MySQL Connector/NET MySQLRoleProvider reported that there were no roles, even when roles existed. (Bug#44414)
MySQL Connector/NET was missing the capability to validate the server's certificate when using encryption. This made it possible to conduct a man-in-the-middle attack against the connection, which defeated the security provided by SSL. (Bug#38700)
First GA release.
Functionality added or changed:
The MySqlTokenizer
failed to split fieldnames
from values if they were not separated by a space. This also
happened if the string contained certain characters. As a result
MySqlCommand.ExecuteNonQuery
raised an index
out of range exception.
The resulting errors are illustrated by the following examples.
Note, the example statements do not have delimiting spaces
around the =
operator.
INSERT INTO anytable SET Text='test--test';
The tokenizer incorrectly interpreted the value as containing a comment.
UPDATE anytable SET Project='123-456',Text='Can you explain this ?',Duration=15 WHERE ID=4711;'
A MySqlException
was generated, as the
?
in the value was interpreted by the
tokenizer as a parameter sign. The error message generated was:
Fatal error encountered during command execution. EXCEPTION: MySqlException - Parameter '?'' must be defined.
Bugs fixed:
MySQL.Data
was not displayed as a Reference
inside Microsoft Visual Studio 2008 Professional.
When a new C# project was created in Microsoft Visual Studio
2008 Professional, MySQL.Data
was not
displayed when , was selected.
(Bug#44141)
Column types for SchemaProvider
and
ISSchemaProvider
did not match.
When the source code in SchemaProvider.cs
and ISSchemaProvider.cs
were compared it
was apparent that they were not using the same column types. The
base provider used SQL such as SHOW CREATE
TABLE
, while ISSchemaProvider
used
the schema information tables. Column types used by the base
class were INT64
and the column types used by
ISSchemaProvider
were
UNSIGNED
.
(Bug#44123)
This is a new development release, fixing recently discovered bugs.
Bugs fixed:
MySQL Connector/NET 6.0.1 did not load in Microsoft Visual Studio 2008 and Visual Studio 2005 Pro.
The following error message was generated:
.NET Framework Data Provider for MySQL: The data provider object factory service was not found.
This is a new Beta development release, fixing recently discovered bugs.
Bugs fixed:
An insert and update error was generated by the decimal data type in the Entity Framework, when a German collation was used. (Bug#43574)
Generating an Entity Data Model (EDM) schema with a table
containing columns with data types MEDIUMTEXT
and LONGTEXT
generated a runtime error
message “Max value too long or too short for
Int32”.
(Bug#43480)
This is a new Alpha development release.
Bugs fixed:
A null reference exception was generated when
MySqlConnection.ClearPool(connection)
was
called.
(Bug#42801)
Bugs fixed:
The Web Provider did not work at all on a remote host, and did
not create a database when using
autogenerateschema="true"
.
(Bug#39072)
The MySQL Connector/NET installer program ended prematurely without reporting the specific error. (Bug#39019)
When called with an incorrect password the
MembershipProvider.GetPassword()
method
threw a
MySQLException
instead of a
MembershipPasswordException
.
(Bug#38939)
Possible overflow in
MySqlPacket.ReadLong()
.
(Bug#36997)
The TokenizeSql
method was adding query
overhead and causing high CPU utilization for larger queries.
(Bug#36836)
Bugs fixed:
If MySqlConnection.GetSchema
was called for
"Indexes" on a table named “b`a`d” as follows:
DataTable schemaPrimaryKeys = connection.GetSchema( "Indexes", new string[] { null, schemaName, "b`a`d"});
Then the following exception was generated:
You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'a`d`' at line 1
When the connection string option “Connection Reset = True” was used, a connection reset used the previously used encoding for the subsequent authentication operation. This failed, for example, if UCS2 was used to read the last column before the reset. (Bug#47153)
In the MySqlDataReader
class the
GetSByte
function returned a
byte
value instead of an
sbyte
value.
(Bug#46620)
When trying to create stored procedures from a SQL script, a
MySqlException
was thrown when attempting to
redefine the DELIMITER
:
MySql.Data.MySqlClient.MySqlException was unhandled Message="You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'DELIMITER' at line 1" Source="MySql.Data" ErrorCode=-2147467259 Number=1064 StackTrace: à MySql.Data.MySqlClient.MySqlStream.ReadPacket() à MySql.Data.MySqlClient.NativeDriver.ReadResult(UInt64& affectedRows, Int64& lastInsertId) à MySql.Data.MySqlClient.MySqlDataReader.GetResultSet() à MySql.Data.MySqlClient.MySqlDataReader.NextResult() à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(CommandBehavior behavior) à MySql.Data.MySqlClient.MySqlCommand.ExecuteReader() à MySql.Data.MySqlClient.MySqlCommand.ExecuteNonQuery() à MySql.Data.MySqlClient.MySqlScript.Execute()
Note: The MySqlScript
class has been fixed to
support the delimiter statement as it is found in SQL scripts.
(Bug#46429)
The MySQL Connector/NET Profile Provider,
MySql.Web.Profile.MySQLProfileProvider
,
generated an error when running on Mono. When an attempt was
made to save a string in Profile.Name
the
string was not saved to the
my_aspnet_Profiles
table. If an attempt was
made to force the save with Profile.Save()
the following error was generated:
Server Error in '/mono' Application -------------------------------------------------------------------------------- The requested feature is not implemented. Description: HTTP 500. Error processing request. Stack Trace: System.NotImplementedException: The requested feature is not implemented. at MySql.Data.MySqlClient.MySqlConnection.EnlistTransaction (System.Transactions.Transaction transaction) [0x00000] at MySql.Data.MySqlClient.MySqlConnection.Open () [0x00000] at MySql.Web.Profile.MySQLProfileProvider.SetPropertyValues (System.Configuration.SettingsContext context, System.Configuration.SettingsPropertyValueCollection collection) [0x00000] -------------------------------------------------------------------------------- Version information: Mono Version: 2.0.50727.1433; ASP.NET Version: 2.0.50727.1433
When using MySQL Connector/NET 6.0.4 and a MySQL Server 4.1 an exception was generated when trying to execute:
connection.GetSchema("Columns", ...);
The exception generated was:
'connection.GetSchema("Columns")' threw an exception of type 'System.ArgumentException'System.Data.DataTable {System.ArgumentException} base{"Input string was not in a correct format.Couldn't store <'Select'> in NUMERIC_PRECISION Column. Expected type is UInt64."}System.Exception {System.ArgumentException}
The MySQL Connector/NET method
StoredProcedure.GetParameters(string)
ignored
the programmer's setting of the
UseProcedureBodies
option. This broke any
application for which the application's parameter names did not
match the parameter names in the Stored Procedure, resulting in
an ArgumentException
with the message
“Parameter 'foo' not found in the collection.” and
the following stack trace:
MySql.Data.dll!MySql.Data.MySqlClient.MySqlParameterCollection.GetParameterFlexible(stri ng parameterName = "pStart", bool throwOnNotFound = true) Line 459C# MySql.Data.dll!MySql.Data.MySqlClient.StoredProcedure.Resolve() Line 157 + 0x25 bytesC# MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteReader(System.Data.CommandBeha vior behavior = SequentialAccess) Line 405 + 0xb bytesC# MySql.Data.dll!MySql.Data.MySqlClient.MySqlCommand.ExecuteDbDataReader(System.Data.Comma ndBehavior behavior = SequentialAccess) Line 884 + 0xb bytesC# System.Data.dll!System.Data.Common.DbCommand.System.Data.IDbCommand.ExecuteReader(System .Data.CommandBehavior behavior) + 0xb bytes System.Data.dll!System.Data.Common.DbDataAdapter.FillInternal(System.Data.DataSet dataset = {System.Data.DataSet}, System.Data.DataTable[] datatables = null, int startRecord = 0, int maxRecords = 0, string srcTable = "Table", System.Data.IDbCommand command = {MySql.Data.MySqlClient.MySqlCommand}, System.Data.CommandBehavior behavior) + 0x83 bytes System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet, int startRecord, int maxRecords, string srcTable, System.Data.IDbCommand command, System.Data.CommandBehavior behavior) + 0x120 bytes System.Data.dll!System.Data.Common.DbDataAdapter.Fill(System.Data.DataSet dataSet) + 0x5f bytes
Conversion of MySQL TINYINT(1)
to
boolean
failed.
(Bug#46205, Bug#46359, Bug#41953)
If the application slept for longer than the specified
net_write_timeout
, and then resumed
Read
operations on a connection, then the
application failed silently.
(Bug#45978)
When reading data, such as with a
MySqlDataAdapter
on a
MySqlConnection
, MySQL Connector/NET could potentially
enter an infinite loop in
CompressedStream.ReadNextpacket()
if
compression was enabled.
(Bug#43678)
An error occurred when building MySQL Connector/NET from source code checked out from the public SVN repository. This happened on Linux using Mono and Nant. The Mono JIT compiler version was 1.2.6.0. The Nant version was 0.85.
When an attempt was made to build (for example) the MySQL Connector/NET 5.2 branch using the command:
$ nant -buildfile:Client.build
The following error occurred:
BUILD FAILED Error loading buildfile. Encoding name 'Windows-1252' not supported. Parameter name: name
MySQL Connector/NET CHM documentation stated that MySQL Server 3.23 was supported. (Bug#42110)
Using a DataAdapter
with a linked
MySqlCommandBuilder
the following exception
was thrown when trying to call da.Update(DataRow[]
rows)
:
Connection must be valid and open
Bugs fixed:
The EscapeString
code carried out escaping by
calling string.Replace
multiple times. This
resulted in a performance bottleneck, as for every line a new
string was allocated and another was disposed of by the garbage
collector.
(Bug#45699)
A MySQL Connector/NET test program that connected to MySQL Server using the
connection string option compress=true
crashed, but only when running on Mono. The program worked as
expected when running on Microsoft Windows.
This was due to a bug in Mono. MySQL Connector/NET was modified to avoid
using WeakReferences
in the
Compressed
stream class, which was causing
the crash.
(Bug#45463)
If a certain socket exception occurred when trying to establish a MySQL database connection, MySQL Connector/NET displayed an exception message that appeared to be unrelated to the underlying problem. This masked the problem and made diagnosing problems more difficult.
For example, if, when establishing a database connection via TCP/IP, Windows on the local machine allocated an ephemeral port that conflicted with a socket address still in use, then Windows/.NET would throw a socket exception with the following error text:
Only one usage of each socket address (protocol/network address/port) is normally
permitted IP ADDRESS/PORT
.
However, MySQL Connector/NET masked this socket exception and displayed an exception with the following text:
Unable to connect to any of the specified MySQL hosts.
The Microsoft Visual Studio solution file
MySQL-VS2005.sln
was invalid. Several
projects could not be loaded and thus it was not possible to
build MySQL Connector/NET from source.
(Bug#44822)
The MySQL Connector/NET MySQLRoleProvider reported that there were no roles, even when roles existed. (Bug#44414)
After a Reference to "C:\Program Files\MySQL\MySQL Connector Net 5.2.4\Compact Framework\MySql.Data.CF.dll" was added to a Windows Mobile 5.0 project, the project then failed to build, generating a Microsoft Visual C# compiler error.
The error generated was:
Error 2 The type 'System.Runtime.CompilerServices.CompilerGeneratedAttribute' has no constructors defined MysqlTest Error 3 Internal Compiler Error (0xc0000005 at address 5A7E3714): likely culprit is 'COMPILE'.
MySQL Connector/NET generated the following exception:
System.NullReferenceException: Object reference not set to an instance of an object. bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject) bei System.Threading._TimerCallback.TimerCallback_Context(Object state) bei System.Threading.ExecutionContext.runTryCode(Object userData) bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading._TimerCallback.PerformTimerCallback(Object state)
When a TableAdapter was created on a DataSet, it was not possible to use a stored procedure with variables. The following error was generated:
The method or operation is not implemented
Functionality added or changed:
A new connection string option has been added: use
affected rows
. When true
the
connection will report changed rows instead of found rows.
(Bug#44194)
Bugs fixed:
Calling GetSchema()
on
Indexes
or IndexColumns
failed where index or column names were restricted.
In SchemaProvider.cs
, methods
GetIndexes()
and
GetIndexColumns()
passed their restrictions
directly to GetTables()
. This only worked if
the restrictions were no more specific than
schemaName
and tableName
.
If IndexName
was given, this was passed to
GetTables()
where it was treated as
TableType
. As a result no tables were
returned, unless the index name happened to be BASE
TABLE
or VIEW
. This meant that both
methods failed to return any rows.
(Bug#43991)
GetSchema("MetaDataCollections")
should have
returned a table with a column named
“NumberOfRestrictions” not
“NumberOfRestriction”.
This can be confirmed by referencing the Microsoft Documentation. (Bug#43990)
Requests sent to the MySQL Connector/NET role provider to remove a user from
a role failed. The query log showed the query was correctly
executed within a transaction which was immediately rolled back.
The rollback was caused by a missing call to the
Complete
method of the transaction.
(Bug#43553)
When using MySqlBulkLoader.Load()
, the text
file is opened by
NativeDriver.SendFileToServer
. If it
encountered a problem opening the file as a stream, an exception
was generated and caught. An attempt to clean up resources was
then made in the finally{}
clause by calling
fs.Close()
, but since the stream was never
successfully opened, this was an attempt to execute a method of
a null reference.
(Bug#43332)
A null reference exception was generated when
MySqlConnection.ClearPool(connection)
was
called.
(Bug#42801)
MySQLMembershipProvider.ValidateUser
only
used the userId
to validate. However, it
should also use the applicationId
to perform
the validation correctly.
The generated query was, for example:
SELECT Password, PasswordKey, PasswordFormat, IsApproved, Islockedout FROM my_aspnet_Membership WHERE userId=13
Note that applicationId
is not used.
(Bug#42574)
There was an error in the ProfileProvider
class in the private ProfileInfoCollection
GetProfiles()
function. The column of the final table
was named “lastUpdatdDate” ('e' is
missing) instead of the correct “lastUpdatedDate”.
(Bug#41654)
The GetGuid()
method of
MySqlDataReader
did not treat
BINARY(16)
column data as a GUID. When
operating on such a column a FormatException
exception was generated.
(Bug#41452)
When ASP.NET membership was configured to not require password
question and answer using
requiresQuestionAndAnswer="false"
, a
SqlNullValueException
was generated when
using MembershipUser.ResetPassword()
to reset
the user password.
(Bug#41408)
If a Stored Procedure
contained spaces in its
parameter list, and was then called from MySQL Connector/NET, an exception
was generated. However, the same Stored
Procedure
called from the MySQL Query Analyzer or the
MySQL Client worked correctly.
The exception generated was:
Parameter '0' not found in the collection.
The DATETIME
format contained an erroneous
space.
(Bug#41021)
When MySql.Web.Profile.MySQLProfileProvider
was configured, it was not possible to assign a name other than
the default name MySQLProfileProvider
.
If the name SCC_MySQLProfileProvider
was
assigned, an exception was generated when attempting to use
Page.Context.Profile['custom prop']
.
The exception generated was:
The profile default provider was not found.
Note that the exception stated: 'the profile default provider...', even though a different name was explicitly requested. (Bug#40871)
When ExecuteNonQuery
was called with a
command type of Stored Procedure
it worked
for one user but resulted in a hang for another user with the
same database permissions.
However, if CALL
was used in the
command text and ExecuteNonQuery
was used
with a command type of Text
, the call worked
for both users.
(Bug#40139)
Bugs fixed:
Visual Studio 2008 displayed the following error three times on start-up:
"Package Load Failure Package 'MySql.Data.VisualStudio.MySqlDataProviderPackage, MySql.VisualStudio, Version=5.2.4, Culture=neutral, PublicKeyTopen=null' has failed to load properly (GUID = {79A115C9-B133-4891-9E7B-242509DAD272}). Please contact the package vendor for assistance. Application restart is recommended, due to possible environment corruption. Would you like to disable loading the package in the future? You may use 'devenve/resetskippkgs' to re-enable package loading."
Bugs fixed:
MySqlDataReader
did not feature a
GetSByte
method.
(Bug#40571)
When working with stored procedures MySQL Connector/NET generated an
exception Unknown "table parameters" in
information_schema
.
(Bug#40382)
GetDefaultCollation
and
GetMaxLength
were not thread safe. These
functions called the database to get a set of parameters and
cached them in two static dictionaries in the function
InitCollections
. However, if many threads
called them they would try to insert the same keys in the
collections resulting in duplicate key exceptions.
(Bug#40231)
If connection pooling was not set explicitly in the connection
string, MySQL Connector/NET added “;Pooling=False” to the end of
the connection string when
MySqlCommand.ExecuteReader()
was called.
If connection pooling was explicitly set in the connection
string, when MySqlConnection.Open()
was
called it converted “Pooling=True” to
“pooling=True”.
If MySqlCommand.ExecuteReader()
was
subsequently called, it concatenated
“;Pooling=False” to the end of the connection
string. The resulting connection string was thus terminated with
“pooling=True;Pooling=False”. This disabled
connection pooling completely.
(Bug#40091)
The connection string option Functions Return
String
did not set the correct encoding for the result
string. Even though the connection string option
Functions Return String=true;
is set, the
result of SELECT DES_DECRYPT()
contained
“??” instead of the correct national character
symbols.
(Bug#40076)
If, when using the MySqlTransaction
transaction object, an exception was thrown, the transaction
object was not disposed of and the transaction was not rolled
back.
(Bug#39817)
After the ConnectionString
property was
initialized via the public setter of
DbConnectionStringBuilder
, the
GetConnectionString
method of
MySqlConnectionStringBuilder
incorrectly
returned null
when true
was assigned to the includePass
parameter.
(Bug#39728)
When using ProfileProvider
, attempting to
update a previously saved property failed.
(Bug#39330)
Reading a negative time value greater than -01:00:00 returned the absolute value of the original time value. (Bug#39294)
Inserting a negative time value (negative
TimeSpan
) into a Time
column through the use of MySqlParameter
caused
MySqlException
to be thrown.
(Bug#39275)
When a data connection was created in the server explorer of Visual Studio 2008 Team, an error was generated when trying to expand stored procedures that had parameters.
Also, if TableAdapter was right-clicked and then , , selected, if you then attempted to select a stored procedure, the window would close and no error message would be displayed. (Bug#39252)
The Web Provider did not work at all on a remote host, and did
not create a database when using
autogenerateschema="true"
.
(Bug#39072)
MySQL Connector/NET called hashed password methods not supported in Mono 2.0 Preview 2. (Bug#38895)
Functionality added or changed:
Error string was returned after a 28000 second
wait_timeout
. This has been
changed to generate a ConnectionState.Closed
event.
(Bug#38119)
Changed how the procedure schema collection is retrieved. If the
connection string contains “use procedure
bodies=true
” then a
SELECT
is performed on the
mysql.proc
table directly, as this is up to
50 times faster than the current Information Schema
implementation. If the connection string contains
“use procedure bodies=false
”,
then the Information Schema collection is queried.
(Bug#36694)
Changed how the procedure schema collection is retrieved. If
use procedure bodies=true
then the
mysql.proc
table is selected directly as this
is up to 50 times faster than the current
information_schema
implementation. If
use procedure bodies=false
, then the
information_schema
collection is queried.
(Bug#36694)
String escaping functionality has been moved from the
MySqlString
class to the
MySqlHelper
class, where it can be
accessed by the EscapeString
method.
(Bug#36205)
Bugs fixed:
The GetOrdinal()
method failed to
return the ordinal if the column name string contained an
accent.
(Bug#38721)
MySQL Connector/NET uninstaller did not clean up all installed files. (Bug#38534)
There was a short circuit evaluation error in the
MySqlCommand.CheckState()
method. When
the statement connection == null
was true a
NullReferenceException
was thrown and not
the expected InvalidOperationException
.
(Bug#38276)
The provider did not silently create the user if the user did not exist. (Bug#38243)
Executing a command that resulted in a fatal exception did not close the connection. (Bug#37991)
When a prepared insert query is run that contains an
UNSIGNED TINYINT
in the parameter list, the
complete query and data that should be inserted is corrupted and
no error is thrown.
(Bug#37968)
In a .NET application MySQL Connector/NET modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.
The original connection string:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25; auto enlist=false;pooling=false;
The connection string after closing
MySqlDataReader
:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25;auto enlist=false;pooling=false; Allow User Variables=True;Allow User Variables=False; Allow User Variables=True;Allow User Variables=False;
Unnecessary network traffic was generated for the normal case where the web provider schema was up to date. (Bug#37469)
MySqlReader.GetOrdinal()
performance
enhancements break existing functionality.
(Bug#37239)
The autogenerateschema
option produced tables
with incorrect collations.
(Bug#36444)
GetSchema
did not work correctly when
querying for a collection, if using a non-English locale.
(Bug#35459)
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug#33322)
Using the MySQL Visual Studio plugin and a MySQL 4.1 server,
certain field types (ENUM
) would
not be identified correctly. Also, when looking for tables, the
plugin would list all tables matching a wildcard pattern of the
database name supplied in the connection string, instead of only
tables within the specified database.
(Bug#30603)
Bugs fixed:
Product documentation incorrectly stated '?' is the preferred parameter marker. (Bug#37349)
An incorrect value for a bit field would returned in a multi-row
query if a preceding value for the field returned
NULL
.
(Bug#36313)
Tables with GEOMETRY
field types would return
an unknown datatype exception.
(Bug#36081)
When using the MySQLProfileProvider
, setting
profile details and then reading back saved data would result in
the default values being returned instead of the updated values.
(Bug#36000)
When creating a connection, setting the
ConnectionString
property of
MySqlConnection
to NULL
would throw an exception.
(Bug#35619)
The DbCommandBuilder.QuoteIdentifer
method was not implemented.
(Bug#35492)
When using encrypted passwords, the
GetPassword()
function would return the wrong
string.
(Bug#35336)
An error would be raised when calling
GetPassword()
with a NULL
value.
(Bug#35332)
When retreiving data where a field has been identified as
containing a GUID value, the incorrect value would be returned
when a previous row contained a NULL
value
for that field.
(Bug#35041)
Using the TableAdapter Wizard
would fail when
generating commands that used stored procedures due to the
change in supported parameter characters.
(Bug#34941)
When creating a new stored procedured, the new parameter code
which allows the use of the @
symbol would
interfere with the specification of a
DEFINER
.
(Bug#34940)
When using SqlDataSource
to open a
connection, the connection would not automatically be closed
when access had completed.
(Bug#34460)
There was a high level of contention in the connection pooling code that could lead to delays when opening connections and submitting queries. The connection pooling code has been modified to try and limit the effects of the contention issue. (Bug#34001)
Using the TableAdaptor
wizard in combination
with a suitable SELECT
statement,
only the associated INSERT
statement would also be created, rather than the required
DELETE
and
UPDATE
statements.
(Bug#31338)
Fixed problem in datagrid code related to creating a new table. This problem may have been introduced with .NET 2.0 SP1.
Fixed profile provider that would throw an exception if you were updating a profile that already existed.
Bugs fixed:
When using the provider to generate or update users and passwords, the password checking algorithm would not validate the password strength or requirements correctly. (Bug#34792)
When executing statements that used stored procedures and functions, the new parameter code could fail to identify the correct parameter format. (Bug#34699)
The installer would fail to the DDEX provider binary if the Visual Studio 2005 component was not selected. The result would lead to MySQL Connector/NET not loading properly when using the interface to a MySQL server within Visual Studio. (Bug#34674)
A number issues were identified in the case, connection and
scema areas of the code for
MembershipProvider
,
RoleProvider
,
ProfileProvider
.
(Bug#34495)
When using web providers, the MySQL Connector/NET would check the schema and cache the application id, even when the connection string had been set. The effect would be to break the memvership provider list. (Bug#34451)
Attempting to use an isolation level other than the default with a transaction scope would use the default isolation level. (Bug#34448)
When altering a stored procedure within Visual Studio, the parameters to the procedure could be lost. (Bug#34359)
A race condition could occur within the procedure cache resulting the cache contents overflowing beyond the configured cache size. (Bug#34338)
Fixed problem with Visual Studio 2008 integration that caused pop-up menus on server explorer nodes to not function
The provider code has been updated to fix a number of outstanding issues.
Functionality added or changed:
Performing GetValue()
on a field
TINYINT(1)
returned a
BOOLEAN
. While not a bug, this
caused problems in software that expected an
INT
to be returned. A new
connection string option Treat Tiny As
Boolean
has been added with a default value of
true
. If set to false
the
provider will treat TINYINT(1)
as
INT
.
(Bug#34052)
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:
Some speed improvements have been implemented in the
TokenizeSql
process used to identify elements
of SQL statements.
(Bug#34220)
When accessing tables from different databases within the same
TransactionScope
, the same user/password
combination would be used for each database connection. MySQL Connector/NET
does not handle multiple connections within the same transaction
scope. An error is now returned if you attempt this process,
instead of using the incorrect authorization information.
(Bug#34204)
The status of connections reported through the state change handler was not being updated correctly. (Bug#34082)
Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug#34000)
In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug#33909)
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 MySQL 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:
Calling GetSchema()
on
Indexes
or IndexColumns
failed where index or column names were restricted.
In SchemaProvider.cs
, methods
GetIndexes()
and
GetIndexColumns()
passed their restrictions
directly to GetTables()
. This only worked if
the restrictions were no more specific than
schemaName
and tableName
.
If IndexName
was given, this was passed to
GetTables()
where it was treated as
TableType
. As a result no tables were
returned, unless the index name happened to be BASE
TABLE
or VIEW
. This meant that both
methods failed to return any rows.
(Bug#43991)
The DATETIME
format contained an erroneous
space.
(Bug#41021)
If connection pooling was not set explicitly in the connection
string, MySQL Connector/NET added “;Pooling=False” to the end of
the connection string when
MySqlCommand.ExecuteReader()
was called.
If connection pooling was explicitly set in the connection
string, when MySqlConnection.Open()
was
called it converted “Pooling=True” to
“pooling=True”.
If MySqlCommand.ExecuteReader()
was
subsequently called, it concatenated
“;Pooling=False” to the end of the connection
string. The resulting connection string was thus terminated with
“pooling=True;Pooling=False”. This disabled
connection pooling completely.
(Bug#40091)
MySQL Connector/NET generated the following exception:
System.NullReferenceException: Object reference not set to an instance of an object. bei MySql.Data.MySqlClient.MySqlCommand.TimeoutExpired(Object commandObject) bei System.Threading._TimerCallback.TimerCallback_Context(Object state) bei System.Threading.ExecutionContext.runTryCode(Object userData) bei System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData) bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state) bei System.Threading._TimerCallback.PerformTimerCallback(Object state)
If, when using the MySqlTransaction
transaction object, an exception was thrown, the transaction
object was not disposed of and the transaction was not rolled
back.
(Bug#39817)
When a prepared insert query is run that contains an
UNSIGNED TINYINT
in the parameter list, the
complete query and data that should be inserted is corrupted and
no error is thrown.
(Bug#37968)
Calling MySqlDataAdapter.FillSchema
on a
SELECT
statement that referred to a table
that did not exist left the connection in a bad state. After
this call, all SELECT
statements returned an
empty result set. If the SELECT
statement
referred to a table that did exist then everything worked as
expected.
(Bug#30518)
Bugs fixed:
There was a short circuit evaluation error in the
MySqlCommand.CheckState()
method. When
the statement connection == null
was true a
NullReferenceException
was thrown and not
the expected InvalidOperationException
.
(Bug#38276)
Executing a command that resulted in a fatal exception did not close the connection. (Bug#37991)
In a .NET application MySQL Connector/NET modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.
The original connection string:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25; auto enlist=false;pooling=false;
The connection string after closing
MySqlDataReader
:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25;auto enlist=false;pooling=false; Allow User Variables=True;Allow User Variables=False; Allow User Variables=True;Allow User Variables=False;
As MySqlDbType.DateTime
is not available
in VB.Net
the warning The datetime
enum value is obsolete was always shown during
compilation.
(Bug#37406)
An unknown MySqlErrorCode
was encountered
when opening a connection with an incorrect password.
(Bug#37398)
Documentation incorrectly stated that “the DataColumn class in .NET 1.0 and 1.1 does not allow columns with type of UInt16, UInt32, or UInt64 to be autoincrement columns”. (Bug#37350)
SemaphoreFullException
is generated when
application is closed.
(Bug#36688)
GetSchema
did not work correctly when
querying for a collection, if using a non-English locale.
(Bug#35459)
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug#33322)
Using the MySQL Visual Studio plugin and a MySQL 4.1 server,
certain field types (ENUM
) would
not be identified correctly. Also, when looking for tables, the
plugin would list all tables matching a wildcard pattern of the
database name supplied in the connection string, instead of only
tables within the specified database.
(Bug#30603)
Bugs fixed:
When creating a connection pool, specifying an invalid IP address will cause the entire application to crash, instead of providing an exception. (Bug#36432)
An incorrect value for a bit field would returned in a multi-row
query if a preceding value for the field returned
NULL
.
(Bug#36313)
The MembershipProvider
will raise an
exception when the connection string is configured with
enablePasswordRetrival = true
and
RequireQuestionAndAnswer = false
.
(Bug#36159)
When calling GetNumberOfUsersOnline
an
exception is raised on the submitted query due to a missing
parameter.
(Bug#36157)
Tables with GEOMETRY
field types would return
an unknown datatype exception.
(Bug#36081)
When creating a connection, setting the
ConnectionString
property of
MySqlConnection
to NULL
would throw an exception.
(Bug#35619)
The DbCommandBuilder.QuoteIdentifer
method was not implemented.
(Bug#35492)
When using SqlDataSource
to open a
connection, the connection would not automatically be closed
when access had completed.
(Bug#34460)
Attempting to use an isolation level other than the default with a transaction scope would use the default isolation level. (Bug#34448)
When altering a stored procedure within Visual Studio, the parameters to the procedure could be lost. (Bug#34359)
A race condition could occur within the procedure cache resulting the cache contents overflowing beyond the configured cache size. (Bug#34338)
Using the TableAdaptor
wizard in combination
with a suitable SELECT
statement,
only the associated INSERT
statement would also be created, rather than the required
DELETE
and
UPDATE
statements.
(Bug#31338)
Functionality added or changed:
Performing GetValue()
on a field
TINYINT(1)
returned a
BOOLEAN
. While not a bug, this
caused problems in software that expected an
INT
to be returned. A new
connection string option Treat Tiny As
Boolean
has been added with a default value of
true
. If set to false
the
provider will treat TINYINT(1)
as
INT
.
(Bug#34052)
Bugs fixed:
Some speed improvements have been implemented in the
TokenizeSql
process used to identify elements
of SQL statements.
(Bug#34220)
When accessing tables from different databases within the same
TransactionScope
, the same user/password
combination would be used for each database connection. MySQL Connector/NET
does not handle multiple connections within the same transaction
scope. An error is now returned if you attempt this process,
instead of using the incorrect authorization information.
(Bug#34204)
The status of connections reported through the state change handler was not being updated correctly. (Bug#34082)
Incorporated some connection string cache optimizations sent to us by Maxim Mass. (Bug#34000)
In an open connection where the server had disconnected unexpectedly, the status information of the connection would not be updated properly. (Bug#33909)
MySQL Connector/NET would fail to compile properly with nant. (Bug#33508)
Problem with membership provider would mean that
FindUserByEmail
would fail with a
MySqlException
because it was trying to add a
second parameter with the same name as the first.
(Bug#33347)
Using compression in the MySQL connection with MySQL Connector/NET would be slower than using native (uncompressed) communication. (Bug#27865)
Bugs fixed:
Setting the size of a string parameter after the value could cause an exception. (Bug#32094)
Creation of parameter objects with noninput 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)
MySQL 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 MySQL 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 MySQL Connector/NET on Windows would fail if VisualStudio had not already been installed. (Bug#28260)
MySQL 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 performance. (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:
If, when using the MySqlTransaction
transaction object, an exception was thrown, the transaction
object was not disposed of and the transaction was not rolled
back.
(Bug#39817)
Executing a command that resulted in a fatal exception did not close the connection. (Bug#37991)
When a prepared insert query is run that contains an
UNSIGNED TINYINT
in the parameter list, the
complete query and data that should be inserted is corrupted and
no error is thrown.
(Bug#37968)
In a .NET application MySQL Connector/NET modifies the connection string so that it contains several occurrences of the same option with different values. This is illustrated by the example that follows.
The original connection string:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25; auto enlist=false;pooling=false;
The connection string after closing
MySqlDataReader
:
host=localhost;database=test;uid=*****;pwd=*****; connect timeout=25;auto enlist=false;pooling=false; Allow User Variables=True;Allow User Variables=False; Allow User Variables=True;Allow User Variables=False;
When creating a connection pool, specifying an invalid IP address will cause the entire application to crash, instead of providing an exception. (Bug#36432)
GetSchema
did not work correctly when
querying for a collection, if using a non-English locale.
(Bug#35459)
When reading back a stored double or single value using the .NET provider, the value had less precision than the one stored. (Bug#33322)
Bugs fixed:
The DbCommandBuilder.QuoteIdentifer
method was not implemented.
(Bug#35492)
Setting the size of a string parameter after the value could cause an exception. (Bug#32094)
Creation of parameter objects with noninput 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 MySQL 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 MySQL 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 performance. (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 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 MySQL 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)
MySQL Connector/NET would fail to install under Windows Vista. (Bug#26430)
Opening a connection would be slow due to host name 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 host name 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)
MySQL 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, MySQL 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, MySQL Connector/NET would incorrectly resolve host names. (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 MySQL Connector/NET 5.0.2 must be installed. (Bug#23071)
Using Windows Vista (RC2) as a nonprivileged 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)
MySQL Connector/NET did not work as a data source for the
SqlDataSource
object used by ASP.NET 2.0.
(Bug#16126)
Bugs fixed:
MySQL 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 MySQL 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 MySQL 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:
Attempting to utilize MySQL Connector .Net version 1.0.10 throws a fatal exception under Mono when pooling is enabled. (Bug#33682)
Setting the size of a string parameter after the value could cause an exception. (Bug#32094)
Creation of parameter objects with noninput 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 MySQL Connector/NET
incorrectly identifying BLOB
fields as binary, rather than text.
(Bug#30233)
Using compression in the MySQL connection with MySQL 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, MySQL 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 host name 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, MySQL Connector/NET would incorrectly resolve host names. (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:
MySQL 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 MySQL 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 MySQL 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 nonnull 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 quotation marks 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:
MySQL 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 MySQL Connector/NET 1.0.5 installer would not install alongside MySQL Connector/NET 1.0.4. (Bug#12835)
Bugs fixed:
MySQL Connector/NET could not connect to MySQL 4.1.14. (Bug#12771)
With multiple hosts in the connection string, MySQL 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)
MySQL Connector/NET interpreted the new decimal data type as a byte array. (Bug#11294)
Added support to call a stored function from MySQL 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)
MySQL 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 do not 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
do not work
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 user
name 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 quotation marks 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 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"/>
Fixes bugs found since release 5.1.12.
Functionality added or changed:
Connector/J did not support utf8mb4
for
servers 5.5.2 and newer.
Connector/J now auto-detects servers configured with
character_set_server=utf8mb4
or treats the
Java encoding utf-8
passed via
characterEncoding=...
as
utf8mb4
in the SET NAMES=
calls it makes when establishing the connection.
(Bug#54175)
Bugs fixed:
The method unSafeStatementInterceptors()
contained an erroneous line of code, which resulted in the
interceptor being called, but the result being thrown away.
(Bug#53041)
There was a performance regression of roughly 25% between r906 and r907, which appeared to be caused by pushing the Proxy down to the I/O layer. (Bug#52534)
Logic in implementations of
LoadBalancingConnectionProxy
and
LoadBalanceStrategy
behaved differently as to
which SQLException
s trigger failover to a new
host. The former looked at the first two characters of the
SQLState:
if (sqlState.startsWith("08")) ...
The latter used a different test:
if (sqlEx instanceof CommunicationsException || "08S01".equals(sqlEx.getSQLState())) { ...
This meant it was possible for a new
Connection
object to throw an
Exception
when the first selected host was
unavailable. This happened because
MySqlIO.createNewIO()
could throw an
SQLException
with a
SQLState
of “08001”, which did
not trigger the “try another host” logic in the
LoadBalanceStrategy
implementations, so an
Exception
was thrown after having only
attempted connecting to a single host.
(Bug#52231)
In the file DatabaseMetadata.java
, the
function private void
getCallStmtParameterTypes
failed if the parameter was
defined over more than one line by using the '\n' character.
(Bug#52167)
The catalog parameter, PARAM_CAT
, was not
correctly processed when calling for metadata with
getMetaData()
on stored procedures. This was
because PARAM_CAT
was hardcoded in the code
to NULL
. In the case where
nullcatalogmeanscurrent
was
true
, which is its default value, a crash did
not occur, but the meta data returned was for the stored
procedures from the catalog currently attached to. If, however,
nullcatalogmeanscurrent
was set to
false
then a crash resulted.
Connector/J has been changed so that when
NULL
is passed as
PARAM_CAT
it will not crash when
nullcatalogmeanscurrent
is
false
, but rather iterate all catalogs in
search of stored procedures. This means that
PARAM_CAT
is no longer hardcoded to
NULL
(see Bug#51904).
(Bug#51912)
A load balanced Connection
object with
multiple open underlying physical connections rebalanced on
commit()
, rollback()
, or
on a communication exception, without validating the existing
connection. This caused a problem when there was no pinging of
the physical connections, using queries starting with “/*
ping */”, to ensure they remained alive. This meant that
calls to Connection.commit()
could throw a
SQLException
. This did not occur when the
transaction was actually committed; it occurred when the new
connection was chosen and the driver attempted to set the
auto-commit or transaction isolation state on the newly chosen
physical connection.
(Bug#51783)
The rollback()
method could fail to rethrow a
SQLException
if the server became unavailable
during a rollback. The errant code only rethrew when
ignoreNonTxTables
was true and the exception
did not have the error code 1196,
SQLError.ER_WARNING_NOT_COMPLETE_ROLLBACK
.
(Bug#51776)
When the allowMultiQueries
connection string
option was set to true
, a call to
Statement.executeBatch()
scanned the query
for escape codes, even though
setEscapeProcessing(false)
had been called
previously.
(Bug#51704)
When a StatementInterceptor
was used and an
alternate ResultSet
was returned from
preProcess()
, the original statement was
still executed.
(Bug#51666)
Objects created by ConnectionImpl
, such as
prepared statements, hold a reference to the
ConnectionImpl
that created them. However,
when the load balancer picked a new connection, it did not
update the reference contained in, for example, the
PreparedStatement
. This resulted in inserts
and updates being directed to invalid connections, while commits
were directed to the new connection. This resulted in silent
data loss.
(Bug#51643)
jdbc:mysql:loadbalance://
would connect to
the same host, even though
loadBalanceStrategy
was set to a value of
random
, and multiple hosts were specified.
(Bug#51266)
An unexpected exception when trying to register
OUT
parameters in
CallableStatement
.
Sometimes Connector/J was not able to register
OUT
parameters for
CallableStatements
.
(Bug#43576)
Fixes bugs found since release 5.1.11.
Bugs fixed:
The catalog parameter was ignored in the
DatabaseMetaData.getProcedure()
method. It
returned all procedures in all databases.
(Bug#51022)
A call to DatabaseMetaData.getDriverVersion()
returned the revision as mysql-connector-java-5.1.11 (
Revision: ${svn.Revision} )
. The variable
${svn.Revision}
was not replaced by the SVN
revision number.
(Bug#50288)
Fixes bugs found since release 5.1.10.
Functionality added or changed:
Replication connections, those with URLs that start with
jdbc:mysql:replication, now use a jdbc:mysql:loadbalance
connection for the slave pool. This means that it is possible to
set load balancing properties such as
loadBalanceBlacklistTimeout
and
loadBalanceStrategy
in order to choose a
mechanism for balancing the load, and failover or fault
tolerance strategy for the slave pool.
(Bug#49537)
Bugs fixed:
NullPointerException
sometimes occurred in
invalidateCurrentConnection()
for
load-balanced connections.
(Bug#50288)
The deleteRow
method caused a full table
scan, when using an updatable cursor and a multibyte character
set.
(Bug#49745)
For pooled connections, Connector/J did not process the session
variable time_zone
when set via the URL,
resulting in incorrect timestamp values being stored.
(Bug#49700)
The ExceptionInterceptor
class did not
provide a Connection
context.
(Bug#49607)
Ping left closed connections in the liveConnections map, causing subsequent Exceptions when that connection was used. (Bug#48605)
Using MysqlConnectionPoolDataSource
with a
load-balanced URL generated exceptions of type
ClassCastException
:
ClassCastException in MysqlConnectionPoolDataSource Caused by: java.lang.ClassCastException: $Proxy0 at com.mysql.jdbc.jdbc2.optional.MysqlConnectionPoolDataSource.getPooledConnection(MysqlConne ctionPoolDataSource.java:80)
java.lang.ClassCastException: $Proxy2 at com.mysql.jdbc.jdbc2.optional.StatementWrapper.executeQuery(StatementWrapper.java:744)
The implementation for load-balanced
Connection
used a proxy, which delegated
method calls, including equals()
and
hashCode()
, to underlying
Connection
objects. This meant that
successive calls to hashCode()
on the same
object potentially returned different values, if the proxy state
had changed such that it was utilizing a different underlying
connection.
(Bug#48442)
The batch rewrite functionality attempted to identify the start
of the VALUES
list by looking for
“VALUES ” (with trailing space). However, valid
MySQL syntax allows for VALUES
to be followed
by whitespace or an opening parenthesis:
INSERT INTO tbl VALUES (1); INSERT INTO tbl VALUES(1);
Queries written with the above formats did not therefore gain the performance benefits of the batch rewrite. (Bug#48172)
A PermGen memory leaked was caused by the Connector/J statement
cancellation timer (java.util.Timer
). When
the application was unloaded the cancellation timer did not
terminate, preventing the ClassLoader from being garbage
collected.
(Bug#36565)
With the connection string option
noDatetimeStringSync
set to
true
, and server-side prepared statements
enabled, the following exception was generated if an attempt was
made to obtain, using ResultSet.getString()
,
a datetime value containing all zero components:
java.sql.SQLException: Value '0000-00-00' can not be represented as java.sql.Date
Fixes bugs found since release 5.1.9.
Bugs fixed:
The DriverManager.getConnection()
method
ignored a non-standard port if it was specified in the JDBC
connection string. Connector/J always used the standard port
3306 for connection creation. For example, if the string was
jdbc:mysql://localhost:6777
, Connector/J
would attempt to connect to port 3306, rather than 6777.
(Bug#47494)
Bugs fixed:
In the class
com.mysql.jdbc.jdbc2.optional.SuspendableXAConnection
,
which is used when
pinGlobalTxToPhysicalConnection=true
, there
is a static map (XIDS_TO_PHYSICAL_CONNECTIONS) that tracks the
Xid with the XAConnection, however this map was not populated.
The effect was that the
SuspendableXAConnection
was never pinned to
the real XA connection. Instead it created new connections on
calls to start
, end
,
resume
, and prepare
.
(Bug#46925)
When using the ON DUPLICATE KEY UPDATE functionality together with the rewriteBatchedStatements option set to true, an exception was generated when trying to execute the prepared statement:
INSERT INTO config_table (modified,id_) VALUES (?,?) ON DUPLICATE KEY UPDATE modified=?
The exception generated was:
java.sql.SQLException: Parameter index out of range (3 > number of parameters, which is 2). at com.sag.etl.job.processors.JdbcInsertProcessor.flush(JdbcInsertProcessor.java:135) ...... Caused by: java.sql.SQLException: Parameter index out of range (3 > number of parameters, which is 2). at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:926) at com.mysql.jdbc.PreparedStatement.checkBounds(PreparedStatement.java:3657) at com.mysql.jdbc.PreparedStatement.setInternal(PreparedStatement.java:3641) at com.mysql.jdbc.PreparedStatement.setBytesNoEscapeNoQuotes(PreparedStatement.java:3391) at com.mysql.jdbc.PreparedStatement.setOneBatchedParameterSet(PreparedStatement.java:4203) at com.mysql.jdbc.PreparedStatement.executeBatchedInserts(PreparedStatement.java:1759) at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1441) at com.sag.etl.job.processors.JdbcInsertProcessor.flush(JdbcInsertProcessor.java:131) ... 16 more
When Connector/J encountered an error condition that caused it
to create a CommunicationsException
, it tried
to build a friendly error message that helped diagnose what was
wrong. However, if there had been no network packets received
from the server, the error message contained the following
incorrect text:
The last packet successfully received from the server was 1,249,932,468,916 milliseconds ago. The last packet sent successfully to the server was 0 milliseconds ago.
The getSuperTypes
method returned a result
set with incorrect names for the first two columns. The name of
the first column in the result set was expected to be
TYPE_CAT
and that of the second column
TYPE_SCHEM
. The method however returned the
names as TABLE_CAT
and
TABLE_SCHEM
for first and second column
respectively.
(Bug#44508)
SQLException for data truncation error gave the error code as 0 instead of 1265. (Bug#44324)
Calling ResultSet.deleteRow()
on a table with
a primary key of type BINARY(8)
silently
failed to delete the row, but only in some repeatable cases. The
generated DELETE
statement generated
corrupted part of the primary key data. Specifically, one of the
bytes was changed from 0x90 to 0x9D, although the corruption
appeared to be different depending on whether the application
was run on Windows or Linux.
(Bug#43759)
Accessing result set columns by name after the result set had been closed resulted in a NullPointerException instead of a SQLException. (Bug#41484)
QueryTimeout
did not work for batch
statements waiting on a locked table.
When a batch statement was issued to the server and was forced to wait because of a locked table, Connector/J only terminated the first statement in the batch when the timeout was exceeded, leaving the rest hanging. (Bug#34555)
The parseURL
method in class
com.mysql.jdbc.Driver
did not work as
expected. When given a URL such as
“jdbc:mysql://www.mysql.com:12345/my_database” to
parse, the property PORT_PROPERTY_KEY
was
found to be null
and the
HOST_PROPERTY_KEY
property was found to be
“www.mysql.com:12345”.
Connector/J has been fixed so that it will now always fill in
the PORT
property (using 3306 if not
specified), and the HOST
property (using
localhost
if not specified) when
parseURL()
is called. The driver also
parses a list of hosts into HOST.n
and
PORT.n
properties as well as adding a
property NUM_HOSTS
for the number of hosts
it has found. If a list of hosts is passed to the driver,
HOST
and PORT
will be
set to the values given by HOST.1
and
PORT.1
respectively. This change has
centralized and cleaned up a large section of code used to
generate lists of hosts, both for load-balanced and fault
tolerant connections and their tests.
Attempting to delete rows using
ResultSet.deleteRow()
did not delete rows
correctly.
(Bug#27431)
The setDate
method silently ignored the
Calendar parameter. The code was implemented as follows:
public void setDate(int parameterIndex, java.sql.Date x, Calendar cal) throws SQLException { setDate(parameterIndex, x); }
From reviewing the code it was apparent that the Calendar
parameter cal
was ignored.
(Bug#23584)
Bugs fixed:
The reported milliseconds since the last server packets were received/sent was incorrect by a factor of 1000. For example, the following method call:
SQLError.createLinkFailureMessageBasedOnHeuristics( (ConnectionImpl) this.conn, System.currentTimeMillis() - 1000, System.currentTimeMillis() - 2000, e, false);
returned the following string:
The last packet successfully received from the server was 2 milliseconds ago. The last packet sent successfully to the server was 1 milliseconds ago.
Calling Connection.serverPrepareStatement()
variants that do not take result set type or concurrency
arguments returned statements that produced result sets with
incorrect defaults, namely
TYPE_SCROLL_SENSITIVE
.
(Bug#45171)
The result set returned by getIndexInfo()
did
not have the format defined in the JDBC API specifications. The
fourth column, DATA_TYPE
, of the result set
should be of type BOOLEAN
. Connector/J
however returns CHAR
.
(Bug#44869)
The result set returned by getTypeInfo()
did
not have the format defined in the JDBC API specifications. The
second column, DATA_TYPE
, of the result set
should be of type INTEGER
. Connector/J
however returns SMALLINT
.
(Bug#44868)
The DEFERRABILITY
column in database metadata
result sets was expected to be of type SHORT
.
However, Connector/J returned it as INTEGER
.
This affected the following methods:
getImportedKeys()
,
getExportedKeys()
,
getCrossReference()
.
(Bug#44867)
The result set returned by getColumns()
did
not have the format defined in the JDBC API specifications. The
fifth column, DATA_TYPE
, of the result set
should be of type INTEGER
. Connector/J
however returns SMALLINT
.
(Bug#44865)
The result set returned by
getVersionColumns()
did not have the format
defined in the JDBC API specifications. The third column,
DATA_TYPE
, of the result set should be of
type INTEGER
. Connector/J however returns
SMALLINT
.
(Bug#44863)
The result set returned by
getBestRowIdentifier()
did not have the
format defined in the JDBC API specifications. The third column,
DATA_TYPE
, of the result set should be of
type INTEGER
. Connector/J however returns
SMALLINT
.
(Bug#44862)
Connector/J contains logic to generate a message text
specifically for streaming result sets when there are
CommunicationsException
exceptions generated.
However, this code was never reached.
In the CommunicationsException
code:
private boolean streamingResultSetInPlay = false; public CommunicationsException(ConnectionImpl conn, long lastPacketSentTimeMs, long lastPacketReceivedTimeMs, Exception underlyingException) { this.exceptionMessage = SQLError.createLinkFailureMessageBasedOnHeuristics(conn, lastPacketSentTimeMs, lastPacketReceivedTimeMs, underlyingException, this.streamingResultSetInPlay);
streamingResultSetInPlay
was always false,
which in the following code in
SQLError.createLinkFailureMessageBasedOnHeuristics()
never being executed:
if (streamingResultSetInPlay) { exceptionMessageBuf.append( Messages.getString("CommunicationsException.ClientWasStreaming")); //$NON-NLS-1$ } else { ...
The
SQLError.createLinkFailureMessageBasedOnHeuristics()
method created a message text for communication link failures.
When certain conditions were met, this message included both
“last packet sent” and “last packet
received” information, but when those conditions were not
met, only “last packet sent” information was
provided.
Information about when the last packet was successfully received should be provided in all cases. (Bug#44587)
Statement.getGeneratedKeys()
retained result
set instances until the statement was closed. This caused memory
leaks for long-lived statements, or statements used in tight
loops.
(Bug#44056)
Using useInformationSchema
with
DatabaseMetaData.getExportedKeys()
generated
the following exception:
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Column 'REFERENCED_TABLE_NAME' in where clause is ambiguous ... at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1772) at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1923) at com.mysql.jdbc.DatabaseMetaDataUsingInfoSchema.executeMetadataQuery( DatabaseMetaDataUsingInfoSchema.java:50) at com.mysql.jdbc.DatabaseMetaDataUsingInfoSchema.getExportedKeys( DatabaseMetaDataUsingInfoSchema.java:603)
LoadBalancingConnectionProxy.doPing()
did not
have blacklist awareness.
LoadBalancingConnectionProxy
implemented
doPing()
to ping all underlying connections,
but it threw any exceptions it encountered during this process.
With the global blacklist enabled, it catches these exceptions, adds the host to the global blacklist, and only throws an exception if all hosts are down. (Bug#43421)
The method Statement.getGeneratedKeys()
did
not return values for UNSIGNED BIGINTS
with
values greater than Long.MAX_VALUE
.
Unfortunately, because the server does not tell clients what
TYPE the auto increment value is, the driver cannot consistently
return BigIntegers for the result set returned from
getGeneratedKeys()
, it will only return them
if the value is greater than Long.MAX_VALUE
.
If your application needs this consistency, it will need to
check the class of the return value from
.getObject()
on the ResultSet returned by
Statement.getGeneratedKeys()
and if it is not
a BigInteger, create one based on the
java.lang.Long
that is returned.
(Bug#43196)
When the MySQL Server was upgraded from 4.0 to 5.0, the Connector/J application then failed to connect to the server. This was because authentication failed when the application ran from EBCDIC platforms such as z/OS. (Bug#43071)
When connecting with traceProtocol=true
, no
trace data was generated for the server greeting or login
request.
(Bug#43070)
Connector/J generated an unhandled
StringIndexOutOfBoundsException
:
java.lang.StringIndexOutOfBoundsException: String index out of range: -1 at java.lang.String.substring(String.java:1938) at com.mysql.jdbc.EscapeProcessor.processTimeToken(EscapeProcessor.java:353) at com.mysql.jdbc.EscapeProcessor.escapeSQL(EscapeProcessor.java:257) at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1546) at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1524)
A ConcurrentModificationException
was
generated in LoadBalancingConnectionProxy
:
java.util.ConcurrentModificationException at java.util.HashMap$HashIterator.nextEntry(Unknown Source) at java.util.HashMap$KeyIterator.next(Unknown Source) at com.mysql.jdbc.LoadBalancingConnectionProxy.getGlobalBlacklist(LoadBalancingConnectionProxy.java:520) at com.mysql.jdbc.RandomBalanceStrategy.pickConnection(RandomBalanceStrategy.java:55) at com.mysql.jdbc.LoadBalancingConnectionProxy.pickNewConnection(LoadBalancingConnectionProxy.java:414) at com.mysql.jdbc.LoadBalancingConnectionProxy.invoke(LoadBalancingConnectionProxy.java:390)
SQL injection was possible when using a string containing U+00A5 in a client-side prepared statement, and the character set being used was SJIS/Windows-31J. (Bug#41730)
If there was an apostrophe in a comment in a statement that was
being sent through Connector/J, the apostrophe was still
recognized as a quote and put the state machine in
EscapeTokenizer
into the
inQuotes
state. This led to further parse
errors.
For example, consider the following statement:
String sql = "-- Customer's zip code will be fixed\n" + "update address set zip_code = 99999\n" + "where not regexp '^[0-9]{5}([[.-.]])?([0-9]{4})?$'";
When passed through Connector/J, the
EscapeTokenizer
did not recognize that the
first apostrophe was in a comment and thus set
inQuotes
to true. When that happened, the
quote count was incorrect and thus the regular expression did
not appear to be in quotation marks. With the parser not
detecting that the regular expression was in quotation marks,
the curly braces were recognized as escape sequences and were
removed from the regular expression, breaking it. The server
thus received SQL such as:
-- Customer's zip code will be fixed update address set zip_code = '99999' where not regexp '^[0-9]([[.-.]])?([0-9])?$'
MySQL Connector/J 5.1.7 was slower than previous versions when
the rewriteBatchedStatements
option was set
to true
.
The performance regression in
indexOfIgnoreCaseRespectMarker()
has been
fixed. It has also been made possible for the driver to
rewrite INSERT
statements with ON
DUPLICATE KEY UPDATE
clauses in them, as long as the
UPDATE
clause contains no reference to
LAST_INSERT_ID()
, as that would cause the
driver to return bogus values for
getGeneratedKeys()
invocations. This has
resulted in improved performance over version 5.1.7.
When accessing a result set column by name using
ResultSetImpl.findColumn()
an exception was
generated:
java.lang.NullPointerException at com.mysql.jdbc.ResultSetImpl.findColumn(ResultSetImpl.java:1103) at com.mysql.jdbc.ResultSetImpl.getShort(ResultSetImpl.java:5415) at org.apache.commons.dbcp.DelegatingResultSet.getShort(DelegatingResultSet.java:219) at com.zimbra.cs.db.DbVolume.constructVolume(DbVolume.java:297) at com.zimbra.cs.db.DbVolume.get(DbVolume.java:197) at com.zimbra.cs.db.DbVolume.create(DbVolume.java:95) at com.zimbra.cs.store.Volume.create(Volume.java:227) at com.zimbra.cs.store.Volume.create(Volume.java:189) at com.zimbra.cs.service.admin.CreateVolume.handle(CreateVolume.java:48) at com.zimbra.soap.SoapEngine.dispatchRequest(SoapEngine.java:428) at com.zimbra.soap.SoapEngine.dispatch(SoapEngine.java:285)
The RETURN_GENERATED_KEYS
flag was being
ignored. For example, in the following code the
RETURN_GENERATED_KEYS
flag was ignored:
PreparedStatement ps = connection.prepareStatement("INSERT INTO table values(?,?)",PreparedStatement.RETURN_GENERATED_KEYS);
When using Connector/J 5.1.7 to connect to MySQL Server 4.1.18 the following error message was generated:
Thu Dec 11 17:38:21 PST 2008 WARN: Invalid value {1} for server variable named {0}, falling back to sane default of {2}
This occurred with MySQL Server version that did not support
auto_increment_increment
. The error message
should not have been generated.
(Bug#41416)
When DatabaseMetaData.getProcedureColumns()
was called, the value for LENGTH
was always
returned as 65535, regardless of the column type (fixed or
variable) or the actual length of the column.
However, if you obtained the PRECISION
value,
this was correct for both fixed and variable length columns.
(Bug#41269)
PreparedStatement.addBatch()
did not check
for all parameters being set, which led to inconsistent behavior
in executeBatch()
, especially when rewriting
batched statements into multi-value INSERT
s.
(Bug#41161)
Error message strings contained variable values that were not expanded. For example:
Mon Nov 17 11:43:18 JST 2008 WARN: Invalid value {1} for server variable named {0}, falling back to sane default of {2}
When using rewriteBatchedStatements=true
with:
INSERT INTO table_name_values (...) VALUES (...)
Query rewriting failed because “values” at the end of the table name was mistaken for the reserved keyword. The error generated was as follows:
testBug40439(testsuite.simple.TestBug40439)java.sql.BatchUpdateException: You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'values (2,'toto',2),(id,data, ordr) values (3,'toto',3),(id,data, ordr) values (' at line 1 at com.mysql.jdbc.PreparedStatement.executeBatchedInserts(PreparedStatement.java:1495) at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1097) at testsuite.simple.TestBug40439.testBug40439(TestBug40439.java:42) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at testsuite.simple.TestBug40439.main(TestBug40439.java:57)
A statement interceptor received the incorrect parameters when used with a batched statement. (Bug#39426)
Using Connector/J 5.1.6 the method
ResultSet.getObject
returned a
BYTE[]
for following:
SELECT TRIM(rowid) FROM tbl
Where rowid
had a type of INT(11)
PRIMARY KEY AUTO_INCREMENT
.
The expected return type was one of CHAR
,
VARCHAR
, CLOB
, however, a
BYTE[]
was returned.
Further, adding
functionsNeverReturnBlobs=true
to the
connection string did not have any effect on the return type.
(Bug#38387)
Functionality added or changed:
When statements include ON DUPLICATE UPDATE
,
and rewriteBatchedStatements
is set to true,
batched statements are not rewritten into the form
INSERT INTO table VALUES (), (), ()
, instead
the statements are executed sequentially.
Bugs fixed:
Statement.getGeneratedKeys()
returned two
keys when using ON DUPLICATE KEY UPDATE
and
the row was updated, not inserted.
(Bug#42309)
When using the replication driver with
autoReconnect=true
, Connector/J checks in
PreparedStatement.execute
(also called by
CallableStatement.execute
) to determine if
the first character of the statement is an “S”, in
an attempt to block all statements that are not read-only-safe,
for example non-SELECT
statements. However, this also blocked
CALL
s to stored procedures, even
if the stored procedures were defined as SQL READ
DATA
or NO SQL
.
(Bug#40031)
With large result sets ResultSet.findColumn
became a performance bottleneck.
(Bug#39962)
Connector/J ignored the value of the MySQL Server variable
auto_increment_increment
.
(Bug#39956)
Connector/J failed to parse
TIMESTAMP
strings for nanos
correctly.
(Bug#39911)
When the LoadBalancingConnectionProxy
handles
a SQLException
with SQL state starting with
“08”, it calls
invalidateCurrentConnection
, which in turn
removes that Connection
from
liveConnections
and the
connectionsToHostsMap
, but it did not add the
host to the new global blacklist, if the global blacklist was
enabled.
There was also the possibility of a
NullPointerException
when trying to update
stats, where
connectionsToHostsMap.get(this.currentConn)
was called:
int hostIndex = ((Integer) this.hostsToListIndexMap.get(this.connectionsToHostsMap.get(this.currentConn))).intValue();
This could happen if a client tried to issue a rollback after
catching a SQLException
caused by a
connection failure.
(Bug#39784)
When configuring the Java Replication Driver the last slave specified was never used. (Bug#39611)
When an INSERT ON DUPLICATE KEY UPDATE
was
performed, and the key already existed, the
affected-rows
value was returned as 1 instead
of 0.
(Bug#39352)
When using the random load balancing strategy and starting with
two servers that were both unavailable, an
IndexOutOfBoundsException
was generated when
removing a server from the whiteList
.
(Bug#38782)
Connector/J threw the following exception when using a read-only connection:
java.sql.SQLException: Connection is read-only. Queries leading to data modification are not allowed.
Connector/J was unable to connect when using a
non-latin1
password.
(Bug#37570)
The useOldAliasMetadataBehavior
connection
property was ignored.
(Bug#35753)
Incorrect result is returned from
isAfterLast()
in streaming
ResultSet
when using
setFetchSize(Integer.MIN_VALUE)
.
(Bug#35170)
When getGeneratedKeys()
was called on a
statement that had not been created with
RETURN_GENERATED_KEYS
, no exception was
thrown, and batched executions then returned erroneous values.
(Bug#34185)
The loadBalance
bestResponseTime
blacklists did not have a
global state.
(Bug#33861)
Functionality added or changed:
Multiple result sets were not supported when using streaming
mode to return data. Both normal statements and the resul sets
from stored procedures now return multiple results sets, with
the exception of result sets using registered
OUTPUT
paramaters.
(Bug#33678)
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 nonverifying trust store and the
"default" key store.
Bugs fixed:
DatabaseMetaData.getColumns()
returns
incorrect COLUMN_SIZE
value for
SET
column.
(Bug#36830)
When trying to read Time
values like
“00:00:00” with
ResultSet.getTime(int)
an exception is
thrown.
(Bug#36051)
JDBC connection URL parameters is ignored when using
MysqlConnectionPoolDataSource
.
(Bug#35810)
When useServerPrepStmts=true
and slow query
logging is enabled, the connector throws a
NullPointerException
when it encounters a
slow query.
(Bug#35666)
When using the keyword “loadbalance” in the connection string and trying to perform load balancing between two databases, the driver appears to hang. (Bug#35660)
JDBC data type getter method was changed to accept only column name, whereas previously it accepted column label. (Bug#35610)
Prepared statements from pooled connections caused a
NullPointerException
when
closed()
under JDBC-4.0.
(Bug#35489)
In calling a stored function returning a
bigint
, an exception is encountered
beginning:
java.sql.SQLException: java.lang.NumberFormatException: For input string:
followed by the text of the stored function starting after the argument list. (Bug#35199)
The JDBC driver uses a different method for evaluating column
names in
resultsetmetadata.getColumnName()
and
when looking for a column in
resultset.getObject(columnName)
. This
causes Hibernate to fail in queries where the two methods yield
different results, for example in queries that use alias names:
SELECT column AS aliasName from table
MysqlConnectionPoolDataSource
does not
support ReplicationConnection
. Notice that we
implemented com.mysql.jdbc.Connection
for
ReplicationConnection
, however, only
accessors from ConnectionProperties are implemented (not the
mutators), and they return values from the currently active
connection. All other methods from
com.mysql.jdbc.Connection
are implemented,
and operate on the currently active connection, with the
exception of resetServerState()
and
changeUser()
.
(Bug#34937)
ResultSet.getTimestamp()
returns incorrect
values for month/day of
TIMESTAMP
s when using server-side
prepared statements (not enabled by default).
(Bug#34913)
RowDataStatic
does't always set the
metadata in ResultSetRow
, which can lead
to failures when unpacking DATE
,
TIME
,
DATETIME
and
TIMESTAMP
types when using
absolute, relative, and previous result set navigation methods.
(Bug#34762)
When calling isValid()
on an active
connection, if the timeout is nonzero then the
Connection
is invalidated even if the
Connection
is valid.
(Bug#34703)
It was not possible to truncate a
BLOB
using
Blog.truncate()
when using 0 as an argument.
(Bug#34677)
When using a cursor fetch for a statement, the internal prepared statement could cause a memory leak until the connection was closed. The internal prepared statement is now deleted when the corresponding result set is closed. (Bug#34518)
When retrieving the column type name of a geometry field, the
driver would return UNKNOWN
instead of
GEOMETRY
.
(Bug#34194)
Statements with batched values do not return correct values for
getGeneratedKeys()
when
rewriteBatchedStatements
is set to
true
, and the statement has an ON
DUPLICATE KEY UPDATE
clause.
(Bug#34093)
The internal class
ResultSetInternalMethods
referenced the
nonpublic class
com.mysql.jdbc.CachedResultSetMetaData
.
(Bug#33823)
A NullPointerException
could be raised when
using client-side prepared statements and enabled the prepared
statement cache using the cachePrepStmts
.
(Bug#33734)
Using server side cursors and cursor fetch, the table metadata information would return the data type name instead of the column name. (Bug#33594)
ResultSet.getTimestamp()
would throw a
NullPointerException
instead of a
SQLException
when called on an empty
ResultSet
.
(Bug#33162)
Load balancing connection using best response time would incorrectly "stick" to hosts that were down when the connection was first created.
We solve this problem with a black list that is used during the
picking of new hosts. If the black list ends up including all
configured hosts, the driver will retry for a configurable
number of times (the retriesAllDown
configuration property, with a default of 120 times), sleeping
250ms between attempts to pick a new connection.
We've also went ahead and made the balancing strategy
extensible. To create a new strategy, implement the interface
com.mysql.jdbc.BalanceStrategy
(which
also includes our standard "extension" interface), and tell the
driver to use it by passing in the class name via the
loadBalanceStrategy
configuration property.
(Bug#32877)
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" (that is, 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)
Retrieving the server version information for an active connection could return invalid information if the default character encoding on the host was not ASCII compatible. (Bug#31192)
Further fixes have been made to this bug in the event that a node is nonresponsive. Connector/J will now try a different random node instead of waiting for the node to recover before continuing. (Bug#31053)
ResultSet
returned by
Statement.getGeneratedKeys()
is not closed
automatically when statement that created it is closed.
(Bug#30508)
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
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)
When calling setTimestamp
on a prepared
statement, the timezone information stored in the calendar
object was ignored. This resulted in the incorrect
DATETIME
information being stored. The
following example illustrates this:
Timestamp t = new Timestamp( cal.getTimeInMillis() ); ps.setTimestamp( N, t, cal );
The following features are new, compared to the 5.0 series of Connector/J
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 is 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 to 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 (that is, without SELECT
or
ON DUPLICATE KEY UPDATE
clauses)
INSERT
or
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 is 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 is 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 to 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 nonzero
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 is 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 nonserver-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 is now
configurable via logXaCommands
property
(defaults to false
).
Added configuration property
localSocketAddress
, which is the host name 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 is 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-to-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 is 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 is 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 is 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 quotation marks 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)
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 is 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 is
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 is 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 quotation marks 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 quotation marks. (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 quotation marks 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 is 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)
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 is available,
Then JDK1.4 logging,
Then fallback to our STDERR
logging.
(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 nonstring 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 file systems.
(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 nonrounding
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 nonwell-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 nonnumerical 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 is
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, nonnegative) 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 nonwritable 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
nonnumeric types (should return max length in chars for
nonbinary 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)
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 nonescaped 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 file names 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 nonstatic.
Use nonaliased 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 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 host names, ports, or user names), 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 available). (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 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 quotation marks 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 do not.
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 quotation marks.
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()
Functionality added or changed:
The embedded MySQL binaries have been updated to MySQL 5.1.40 for GPL releases and MySQL 5.1.40 for Commercial releases.
The contents of the directory used for bootstrapping the MySQL
databases is now configurable by using the
windows-share-dir-jar
property. You should
supply the name of a jar containing the files you want to use.
The embedded Aspect/J class has been removed.
The default timeout for the kill delay within the embedded test suite has been increased from 10 to 30 seconds.
Bugs fixed:
On startup Connector/MXJ generated an exception on Windows 7:
Exception in thread “Thread-3” java.util.MissingResourceException?: Resource ‘5-0-51a/Windows_7-x86/mysqld-nt.exe’ not found at com.mysql.management.util.Streams.getResourceAsStream(Streams.java:133) at com.mysql.management.util.Streams.getResourceAsStream(Streams.java:107) at com.mysql.management.util.Streams$1.inner(Streams.java:149) at com.mysql.management.util.Exceptions$VoidBlock?.exec(Exceptions.java:128) at com.mysql.management.util.Streams.createFileFromResource(Streams.java:162) at com.mysql.management.MysqldResource?.makeMysqld(MysqldResource?.java:533) at com.mysql.management.MysqldResource?.deployFiles(MysqldResource?.java:518) at com.mysql.management.MysqldResource?.exec(MysqldResource?.java:495) at com.mysql.management.MysqldResource?.start(MysqldResource?.java:216) at com.mysql.management.MysqldResource?.start(MysqldResource?.java:166)
The default platform-map.properties
file,
which maps platforms to the supplied binary bundles, has been
updated with additional platforms, including Windows 7, Windows
Server 2008, amd64
and
sparcv9
for Solaris, and Mac OS X 64-bit.
(Bug#48298)
This was an internal only release.
Functionality added or changed:
The embedded MySQL has been updated to the MySQL 5.1 series. The embedded MySQL binaries have been updated to MySQL 5.1.33 for GPL releases and MySQL 5.1.34 for Commercial releases.
The MySQL binary for Windows targets has been updated to be
configurable through the
windows-mysqld-command
property. This is to
handle the move in MySQL 5.1.33 from
mysqld-nt.exe to
mysqld.exe. The default value is
mysqld.exe.
Functionality added or changed:
The port used in the
ConnectorMXJUrlTestExample
and
ConnectorMXJObjectTestExample
port is no
longer hard coded. Instead, the code uses the
x-mxj_test_port
property a default value of
3336
The utility used to kill MySQL on Windows
(kill.exe
) has been configured to be loaded
from the kill.exe
property, instead of being
hard-coded. The corresponding timeout,
KILL_DELAY
has also been moved to the
properties file and defaults to 5 minutes.
The embedded MySQL binaries have been updated to MySQL 5.0.51a for GPL releases and MySQL 5.0.54 for Commercial releases.
The timeout for kill operations in the embedded test suite has been set to a default of 10 seconds.
Functionality added or changed:
The embedded documentation has been updated so that it now points to the main MySQL documentation pages in the MySQL reference manual.
The embedded MySQL binaries have been updated to MySQL 5.0.45 for GPL releases and MySQL 5.0.46 for Commercial releases.
Functionality added or changed:
Updated the jar filename to be consistent with the Connector/J
jar filename. Files are now formatted as
mysql-connector-mxj-
.
mxj-version
The ConnectorMXJUrlTestExample
and
ConnectorMXJObjectTestExammple
have been
updated to include an example of initializing the user/password
and creating an initial database. The
InitializePasswordExample
example class has
now been removed.
The PatchedStandardSocketFactory
class has
been removed, because it fixed an issue in Connector/J that was
corrected in Connector/J 5.0.6.
The embedded MySQL binaries have been updated to MySQL 5.0.41 for GPL releases and MySQL 5.0.42 for Commercial releases.
Bugs fixed:
Added a null-check to deal with class loaders where
getClassLoader()
returns null.
Functionality added or changed:
Updated internal jar file names to include version information
and be more consistent with Connector/J jar naming. For example,
connector-mxj.jar
is now
mysql-connector-mxj-${mxj-version}.jar
.
Updated commercial license files.
Added copyright notices to some classes which were missing them.
Added InitializeUser
and
QueryUtil
classes to support new feature.
Added new tests for initial-user & expanded some existing tests.
ConnectorMXJUrlTestExample
and
ConnectorMXJObjectTestExample
now
demonstrate the initialization of user/password and creating the
initial database (rather than using "test").
Added new connection property initialize-user
which, if set to true
will remove the
default, un-passworded anonymous and root users, and create the
user/password from the connection url.
Removed obsolete field
SimpleMysqldDynamicMBean.lastInvocation
.
Clarified code in DefaultsMap.entrySet()
.
Removed obsolete
PatchedStandardSocketFactory
java file.
Added main(String[])
to
com/mysql/management/AllTestsSuite.java
.
Errors reading portFile
are now reported
using stacktrace(err)
, previously
System.err
was used.
portFile
now contains a new-line to be
consistent with pidFile
.
Fixed where versionString.trim()
was
ignored.
Removed references to File.deleteOnExit
,
a warning is printed instead.
Bugs fixed:
Changed tests to shutdown mysqld prior to deleting files.
Fixed port file to always be written 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.
Added null-check to deal with C/MXJ being loaded by the
bootstrap classloaders with JVMs for which
getClassLoader()
returns null.
Added robustness around reading portfile.
Removed PatchedStandardSocketFactory
(fixed
in Connetor/J 5.0.6).
Refactored duplication from tests and examples to
QueryUtil
.
Removed obsolete
InitializePasswordExample
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 a 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 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.
This fixes bugs since the first GA release 1.0.5 and introduces new features.
Functionality added or changed:
Incompatible Change:
API incompatible change: ConnectPropertyVal
is no longer a struct
by a typedef that uses
boost::variant
. Code such as:
sql::ConnectPropertyVal tmp; tmp.str.val=passwd.c_str(); tmp.str.len=passwd.length(); connection_properties["password"] = tmp;
Should be changed to:
connection_properties["password"] = sql::ConnectPropertyVal(passwd);
Instances of std::auto_ptr
have been changed
to boost::scoped_ptr
. Scoped array instances
now use boost::scoped_array. Further,
boost::shared_ptr
and
boost::weak_ptr
are now used for guarding
access around result sets.
LDFLAGS
, CXXFLAGS
and
CPPFLAGS
are now checked from the environment
for every binary generated.
Connection map property OPT_RECONNECT
was
changed to be of type boolean
from
long
long
.
get_driver_instance()
is now only available
in dynamic library builds - static builds do not have this
symbol. This was done to accommodate loading the DLL with
LoadLibrary
or dlopen
. If
you do not use CMake for building the source code you will need
to define mysqlcppconn_EXPORTS
if you are
loading dynamically and want to use the
get_driver_instance()
entry point.
Connection::getClientOption(const sql::SQLString &
optionName, void * optionValue)
now accepts the
optionName
values
metadataUseInfoSchema
,
defaultStatementResultType
,
defaultPreparedStatementResultType
, and
characterSetResults
. In the previous version
only metadataUseInfoSchema
was allowed. The
same options are avalable for
Connection::setClientOption()
.
Bugs fixed:
Certain header files were incorrectly present in the source distribution. The fix excludes dynamically generated and platform specific header files from source packages generated using CPack. (Bug#45846)
CMake generated an error if configuring an out of source build, that is when CMake not called from the source root directory. (Bug#45843)
Using Prepared Statements caused corruption of the heap. (Bug#45048)
Missing includes when using GCC 4.4. Note that GCC 4.4 is not yet in use for any official MySQL Connector/C++ builds. (Bug#44931)
A bug was fixed in Prepared Statements. The bug occurred when a stored procedure was prepared without any parameters. This led to an exception. (Bug#44931)
Fixed a Prepared Statements performance issue. Reading large result sets was slow.
Fixed bug in ResultSetMetaData
for statements
and prepared statements, getScale
and
getPrecision
returned incorrect results.
This is the first Generally Available (GA) release.
Functionality added or changed:
The interface of sql::ConnectionMetaData
,
sql::ResultSetMetaData
and
sql::ParameterMetaData
was modified to have a
protected destructor. As a result the client code has no need to
destruct the metadata objects returned by the connector. MySQL Connector/C++
handles the required destruction. This enables statements such
as:
connection->getMetaData->getSchema();
This avoids potential memory leaks that could occur as a result
of losing the pointer returned by
getMetaData()
.
Improved memory management. Potential memory leak situations are handled more robustly.
Changed the interface of sql::Driver
and
sql::Connection
so they accept the options
map by alias instead of by value.
Changed the return type of
sql::SQLException::getSQLState()
from
std::string
to const char
*
to be consistent with
std::exception::what()
.
Implemented getResultSetType()
and
setResultSetType()
for
Statement
. Uses
TYPE_FORWARD_ONLY
, which means unbuffered
result set and TYPE_SCROLL_INSENSITIVE
, which
means buffered result set.
Implemented getResultSetType()
for
PreparedStatement
. The setter is not
implemented because currently
PreparedStatement
cannot do refetching.
Storing the result means the bind buffers will be correct.
Added the option defaultStatementResultType
to MySQL_Connection::setClientOption()
. Also,
the method now returns sql::Connection *
.
Added Result::getType()
. Implemented for the
three result set classes.
Enabled tracing functionality when building with Microsoft Visual C++ 8 and later, which corresponds to Microsoft Visual Studio 2005 and later.
Added better support for named pipes, on Windows. Use
pipe://
and add the path to the pipe. Shared
memory connections are currently not supported.
Bugs fixed:
A bug was fixed in
MySQL_Connection::setSessionVariable()
, which
had been causing exceptions to be thrown.
Functionality added or changed:
An installer was added for the Windows operating system.
Minimum CMake version required was changed from 2.4.2 to 2.6.2. The latest version is required for building on Windows.
metadataUseInfoSchema
was added to the
connection property map, which allows control of the
INFORMATION_SCHEMA
for meta data.
Implemented
MySQL_ConnectionMetaData::supportsConvert(from,
to)
.
Added support for MySQL Connector/C.
Introduced ResultSetMetaData::isZerofill()
,
which is not in the JDBC specification.
Bugs fixed:
A bug was fixed in all implementations of
ResultSet::relative()
which was giving a
wrong return value although positioning was working correctly.
A leak was fixed in MySQL_PreparedResultSet
,
which occurred when the result contained a
BLOB
column.
Functionality added or changed:
Added new tests in test/unit/classes
. Those
tests are mostly about code coverage. Most of the actual
functionality of the driver is tested by the tests found in
test/CJUnitPort
.
New data types added to the list returned by
DatabaseMetaData::getTypeInfo()
are
FLOAT UNSIGED
, DECIMAL
UNSIGNED
, DOUBLE UNSIGNED
. Those
tests may not be in the JDBC specification. However, due to the
change you should be able to look up every type and type name
returned by, for example,
ResultSetMetaData::getColumnTypeName()
.
MySQL_Driver::getPatchVersion
introduced.
Major performance improvements due to new buffered
ResultSet
implementation.
Addition of test/unit/README
with
instructions for writing bug and regression tests.
Experimental support for STLPort. This feature may be removed
again at any time later without prior warning! Type
cmake -L
for configuration
instructions.
Added properties enabled methods for connecting, which add many
connect options. This uses a dictionary (map) of key value
pairs. Methods added are
Driver::connect(map)
, and
Connection::Connection(map)
.
New BLOB implementation. sql::Blob
was
removed in favor of std::istream
. C++'s
IOStream
library is very powerful, similar to
PHP's streams. It makes no sense to reinvent the wheel. For
example, you can pass a std::istringstream
object to setBlob()
if the data is in memory,
or just open a file std::fstream
and let it
stream to the DB, or write its own stream. This is also true for
getBlob()
where you can just copy data (if a
buffered result set), or stream data (if implemented).
Implemented ResultSet::getBlob()
which
returns std::stream
.
Fixed
MySQL_DatabaseMetaData::getTablePrivileges()
.
Test cases were added in the first unit testing framework.
Implemented
MySQL_Connection::setSessionVariable()
for
setting variables like sql_mode
.
Implemented
MySQL_DatabaseMetaData::getColumnPrivileges()
.
cppconn/datatype.h
has changed and is now
used again. Reimplemented the type subsystem to be more usable -
more types for binary and nonbinary strings.
Implementation for
MySQL_DatabaseMetaData::getImportedKeys()
for
MySQL versions before 5.1.16 using SHOW
, and
above using INFORMATION_SCHEMA
.
Implemented
MySQL_ConnectionMetaData::getProcedureColumns()
.
make package_source now packs with bzip2.
Re-added getTypeInfo()
with information about
all types supported by MySQL and the
sql::DataType
.
Changed the implementation of
MySQL_ConstructedResultSet
to use the more
efficient O(1) access method. This should improve the speed with
which the metadata result sets are used. Also, there is less
copying during the construction of the result set, which means
that all result sets returned from the meta data functions will
be faster.
Introduced, internally, sql::mysql::MyVal
which has implicit constructors. Used in
mysql_metadata.cpp
to create result sets
with native data instead of always string (varchar).
Renamed ResultSet::getLong()
to
ResultSet::getInt64()
.
resultset.h
includes typdefs for Windows to
be able to use int64_t
.
Introduced ResultSet::getUInt()
and
ResultSet::getUInt64()
.
Improved the implementation for
ResultSetMetaData::isReadOnly()
. Values
generated from views are read only. These generated values don't
have db
in MYSQL_FIELD
set, while all normal columns do have.
Implemented
MySQL_DatabaseMetaData::getExportedKeys()
.
Implemented
MySQL_DatabaseMetaData::getCrossReference()
.
Bugs fixed:
Bug fixed in
MySQL_PreparedResultSet::getString()
.
Returned string that had real data but the length was random.
Now, the string is initialized with the correct length and thus
is binary safe.
Corrected handling of unsigned server types. Now returning correct values.
Fixed handling of numeric columns in
ResultSetMetaData::isCaseSensitive
to return
false
.
Functionality added or changed:
Implemented getScale()
,
getPrecision()
and
getColumnDisplaySize()
for
MySQL_ResultSetMetaData
and
MySQL_Prepared_ResultSetMetaData
.
Changed ResultSetMetaData
methods
getColumnDisplaySize()
,
getPrecision()
, getScale()
to return unsigned int
instead of
signed int
.
DATE
, DATETIME
and
TIME
are now being handled when calling the
MySQL_PreparedResultSet
methods
getString()
, getDouble()
,
getInt()
, getLong()
,
getBoolean()
.
Reverted implementation of
MySQL_DatabaseMetaData::getTypeInfo()
. Now
unimplemented. In addition, removed
cppconn/datatype.h
for now, until a more
robust implementation of the types can be developed.
Implemented
MySQL_PreparedStatement::setNull()
.
Implemented
MySQL_PreparedStatement::clearParameters()
.
Added PHP script
examples/cpp_trace_analyzer.php
to filter
the output of the debug trace. Please see the inline comments
for documentation. This script is unsupported.
Implemented
MySQL_ResultSetMetaData::getPrecision()
and
MySQL_Prepared_ResultSetMetaData::getPrecision()
,
updating example.
Added new unit test framework for JDBC compliance and regression testing.
Added test/unit
as a basis for general unit
tests using the new test framework, see
test/unit/example
for basic usage examples.
Bugs fixed:
Fixed
MySQL_PreparedStatementResultSet::getDouble()
to return the correct value when the underlying type is
MYSQL_TYPE_FLOAT
.
Fixed bug in
MySQL_ConnectionMetaData::getIndexInfo()
. The
method did not work because the schema name wasn't included in
the query sent to the server.
Fixed a bug in
MySQL_ConnectionMetaData::getColumns()
which
was performing a cartesian product of the columns in the table
times the columns matching columnNamePattern
.
The example
example/connection_meta_schemaobj.cpp
was
extended to cover the function.
Fixed bugs in MySQL_DatabaseMetaData
. All
supportsCatalogXXXXX
methods were incorrectly
returning true
and all
supportsSchemaXXXX
methods were incorrectly
returning false
. Now
supportsCatalogXXXXX
returns
false
and
supportsSchemaXXXXX
returns
true
.
Fixed bugs in the MySQL_PreparedStatements
methods setBigInt()
and
setDatetime()
. They decremented the internal
column index before forwarding the request. This resulted in a
double-decrement and therefore the wrong internal column index.
The error message generated was:
setString() ... invalid "parameterIndex"
Fixed a bug in getString()
.
getString()
is now binary safe. A new example
was also added.
Fixed bug in FLOAT
handling.
Fixed MySQL_PreparedStatement::setBlob()
. In
the tests there is a simple example of a class implementing
sql::Blob
.
Functionality added or changed:
sql::mysql::MySQL_SQLException
was removed.
The distinction between server and client (connector) errors,
based on the type of the exception, has been removed. However,
the error code can still be checked in order to evaluate the
error type.
Support for (n)make install was added. You can change the default installation path. Carefully read the messages displayed after executing cmake. The following are installed:
Static and the dynamic version of the library,
libmysqlcppconn
.
Generic interface, cppconn
.
Two MySQL specific headers:
mysql_driver.h
, use this if you want to
get your connections from the driver instead of
instantiating a MySQL_Connection
object.
This makes your code portable when using the common
interface.
mysql_connection.h
, use this if you
intend to link directly to the
MySQL_Connection
class and use its
specifics not found in sql::Connection
.
However, you can make your application fully abstract by using the generic interface rather than these two headers.
Driver Manager was removed.
Added ConnectionMetaData::getSchemas()
and
Connection::setSchema()
.
ConnectionMetaData::getCatalogTerm()
returns
not applicable, there is no counterpart to catalog in MySQL Connector/C++.
Added experimental GCov support, cmake
-DMYSQLCPPCONN_GCOV_ENABLE:BOOL=1
All examples can be given optional connection parameters on the command line, for example:
examples/connect tcp://host:port user pass database
or
examples/connect unix:///path/to/mysql.sock user pass database
Renamed ConnectionMetaData::getTables:
TABLE_COMMENT
to REMARKS
.
Renamed ConnectionMetaData::getProcedures:
PROCEDURE_SCHEMA
to
PROCEDURE_SCHEM
.
Renamed ConnectionMetaData::getPrimaryKeys():
COLUMN
to COLUMN_NAME
,
SEQUENCE
to KEY_SEQ
, and
INDEX_NAME
to PK_NAME
.
Renamed ConnectionMetaData::getImportedKeys():
PKTABLE_CATALOG
to PKTABLE_CAT
,
PKTABLE_SCHEMA
to
PKTABLE_SCHEM
,
FKTABLE_CATALOG
to
FKTABLE_CAT
,
FKTABLE_SCHEMA
to
FKTABLE_SCHEM
.
Changed metadata column name TABLE_CATALOG
to
TABLE_CAT
and TABLE_SCHEMA
to TABLE_SCHEM
to ensure JDBC compliance.
Introduced experimental CPack support, see make help.
All tests changed to create TAP compliant output.
Renamed sql::DbcMethodNotImplemented
to
sql::MethodNotImplementedException
Renamed sql::DbcInvalidArgument
to
sql::InvalidArgumentException
Changed sql::DbcException
to implement the
interface of JDBC's SQLException
. Renamed to
sql::SQLException
.
Converted Connector/J tests added.
MySQL Workbench 5.1 changed to use MySQL Connector/C++ for its database connectivity.
New directory layout.
Functionality added or changed:
network_address_set_address()->network_address_set_address_ip()
called gethostbyname()
which was not
reentrant. This meant that an mt-plugin needed to guard all
calls to network_address_set_address()
with a
mutex. network_address_set_address()
has been
modified to be thread safe.
(Bug#49099)
The hard-limit was fixed for the case where the fdlimit was set. (Bug#48120)
Allow interception of LOAD DATA and SHOW ERROR commands.
An unused
network_mysqld_com_query_result_track_state()
state was deprecated.
chassis_set_fdlimit()
was deprecated in favor
of chassis_fdlimit_set()
.
Shutdown hooks were added to free the global memory of third
party libraries such as openssl
.
con->in_load_data_local
has been removed.
Bugs fixed:
The admin plugin had an undocumented default value for
--admin-password
.
(Bug#53429)
Use of LOAD DATA LOCAL INFILE caused the connection between the client and MySQL Proxy to abort. (Bug#51864)
When using the MySQL Proxy, if the backend MySQL server went down, and then the clock on the MySQL Proxy host went back in time (for example, during daylight savings time adjustments), the MySQL Proxy would stop sending queries to the configured backend. (Bug#50806)
Proxy returned an error message with a non-standard SQLState when all backends were down:
"#07000(proxy) all backends are down"
This caused issues for clients with "retry" logic, as they did not have the facility to handle these "custom" SQL States. (Bug#45417)
When running configure to build, the error
message relating to the lua
libraries could
be misleading. The wording and build advice have now been
updated.
Bugs fixed:
A memory leak could occur in MySQL Proxy if MySQL v4.0 or earlier clients connected to the proxy. (Bug#50993)
mysql-proxy would cause a segmentation fault if a connection was made from a client using the MySQL protocol 4.0 or earlier. (Bug#48641)
MySQL Proxy would load a configuration file with unsafe permissions, which could allow password information to be exposed through the configuration file. MySQL Proxy now refuses to load a file with unsafe permissions. (Bug#47589)
The supplied script ro-balance.lua
had not
been updated to use the resultset_is_needed
and updated proxy.connection.dst.name
structure.
(Bug#47349, Bug#45408)
The line numbers provided in stack traces would be out by one line. (Bug#47348)
The supplied script active-transactions.lua
had not been updated to use the new
resultset_is_needed
flag.
(Bug#47345)
When submitting an address on the command line using
--proxy-backend-addresses, the option would
accept more than one address as an argument to the option. You
should specify one --proxy-backend-addresses
for each backend address.
(Bug#47273)
MySQL Proxy would return the wrong version string internally
from the proxy.PROXY_VERSION
constant.
(Bug#45996)
MySQL Proxy could stop accepting network packets if a large number of packets were sent to the proxy. The listen queue has been extended to allow a larger backlog. (Bug#45878, Bug#43278)
Due to a memory leak, memory usage for each uniqute connection to the proxy would increase, leading to very high consumption. (Bug#45272)
MySQL Proxy would fail to work with certain versions of MySQL, including MySQL 5.1.15, where a change in the MySQL protocol existed. (Bug#45167)
See also Bug#25371.
The supplied script rw-splitting.lua
had
not been updated to use the new
resultset_is_needed
flag or updated
proxy.connections
structure.
(Bug#43424, Bug#42841, Bug#46141)
Logging to syslog
with the
use-log-syslog
option did not work.
(Bug#36431)
It was possible for the MySQL Proxy to incorrectly insert null values into the returned result set, even though non-null values were returned in the original query. (Bug#35729)
MySQL Proxy would raise an error when processing query packets larger than 16MB in size. (Bug#35202)
Bugs fixed:
When using MySQL Proxy on Windows, the required modules may not
be found properly during initialization. The core code has now
been updated to find the components correctly, and the Lua-based
C modules are prefixed with lua-
and Lua
plugins with plugin-
.
(Bug#45833)
Bugs fixed:
Due to a memory leak, memory usage for each uniqute connection to the proxy would increase, leading to very high consumption. (Bug#45272)
The port number reported in
proxy.connection.client.address
would be
reported incorrectly.
(Bug#43313)
Result sets with more than 250 fields could cause MySQL Proxy to crash. (Bug#43078)
MySQL Proxy would be unable to increase it's own maximum number of open files accorindg to the applied limit, if the limit was less than 8192. When set to debug level, MySQL Proxy will now report the open files limits and when the limits have been updated. (Bug#42783)
When connecting to a MySQL 4.0 server, the proxy would crash. You are now provided with an error message. (Bug#38601)
When using the rw-splitting.lua
script you
could get an error when talking to the backend server:
2008-07-28 18:00:30: (critical) (read_query) [string "/usr/local/share/mysql-proxy/rw-splitting.l..."]:218: bad argument #1 to 'ipairs' (table expected, got userdata)
This would lead to the proxy closing the connection to the configured MySQL backend. (Bug#38419)
When using MySQL Proxy with multiple backends, the failure of one backend would cause proxy to disconnect all backends and stop routing requests. (Bug#34793)
Functionality added or changed:
Support for using a configuration file, in addition to the
command-line options, has been added. You can specify the file
to use by using the --defaults-file
command
line option. See Section 14.6.3, “MySQL Proxy Configuration Options”.
(Bug#30206)
A number of the internal structures used during developing Lua scripts for work with MySQL proxy have been updated and harmonised to make their meaning and contents easier to use and consistent across multiple locations.
The address information has been updated so that instead of
a combined ip:port
structure that you had
to parse to extract the individual informaiton, you can now
access that information directly. For example, instead of
structures providing a single item
.address
, you now have items,
name
(the combined
ip:port
) and address
(the IP address) and port
(port number).
In addition, all addresses now supply both the
src
(source) and dst
(destination) socket information for both ends of the
connections.
Some familiar strucgtures have been updated to acommodate this information:
proxy.connection.client.address
is
proxy.connection.client.src.name
proxy.connection.server.address
is
proxy.connection.server.dst.name
proxy.backends
is now in
proxy.global.backends
The
.address
field of each backend is a
address-object as described above. For example,
proxy.backends[1].address
is
proxy.global.backends[1].dst.name
.
The read_auth()
and
read_handshake()
functions no longer
receive an auth
parameter. Instead, all
the data is available in the connection tables.
In read_handshake() you access the informaiton through the
global proxy.connction
table:
0.6 | 0.7 |
---|---|
auth.thread_id
| proxy.connection.server.thread_id
|
auth.mysqld_version
| proxy.connection.server.mysqld_version
|
auth.server_addr
| proxy.connection.server.dst.name
|
auth.client_addr
| proxy.connection.client.src.name
|
auth.scramble
| proxy.connection.server.scramble_buffer
|
In read_auth()
you can use the
following:
0.6 | 0.7 |
---|---|
auth.username
| proxy.connection.client.username
|
auth.password
| proxy.connection.client.scrambled_password
|
auth.default_db
| proxy.connection.client.default_db
|
auth.server_addr
| proxy.connection.server.dst.name
|
auth.client_addr
| proxy.connection.client.src.name
|
In the function proxy.queries:append()
a 3rd parameter is an (optional) table with options specific
to the this packet. Specifically, if you want to have access
to the resultset in the
read_query_result()
hook, you have to
set the resultset_is_needed
flag:
proxy.queries:append( 1, ..., { resultset_is_needed = true } )
For more information, see proxy.queries.
proxy.backends
is now in
proxy.global.backends
.
Bugs fixed:
Security Enhancement: Accessing mysql-proxy using a client or backend with a MySQL protocol less than MySQL 5.0 would result in mysql-proxy aborting with an assertion. This is because mysql-proxy only supports MySQL Protocol 5.0 or higher. The proxy will now report a fault. (Bug#31419)
MySQL Proxy would be configured with the
LUA_PATH
and LUA_CPATH
n
directory locations according to the build, not execution, host.
In addition, during installation, certain Lua source files could
be installed into the incorrect locations.
(Bug#44877, Bug#44497)
Using mysql-proxy with very large return datasets from queries, with or without manipulate of the dataset within the Lua engine could cause a crash. (Bug#39332)
If a submitted packet was smaller than expected by the protocol, MySQL Proxy would terminate. (Bug#36743)
When using mysql-proxy in a master-master replication scenario, a failure in one of the replication masters would fail to be identified by the proxy and connections would not be redirected to the other master. (Bug#35295)
Functionality added or changed:
Fixed assertions on write-errors
Fixed sending fake server-greetings in
connect_server()
.
Fixed error handling for socket functions on Windows.
Added new features to run-tests.lua
.
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.