MySQL Enterprise Backup 4.1.0 has been released

[Karen Langford]

Dear MySQL users,

MySQL Enterprise Backup v4.1.0, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

MySQL Enterprise Backup 4.1.0 supports only the MySQL Server 5.7.9 and
above.  For any earlier versions of the MySQL server, please use MySQL
Enterprise Backup 3.12 instead.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.1.0 is given below.

Changes in MySQL Enterprise Backup 4.1.0 (2017-03-03)

   Functionality Added or Changed

 * MySQL Enterprise Backup now supports the --ssl-mode
   option, which enables you to specify the security state
   of the connection to the server. It replaces the client
   side --ssl and --ssl-verify-server-cert options, which
   are now deprecated. See the description of the --ssl-mode
   option in MySQL 5.7 Reference Manual
   (http://dev.mysql.com/doc/refman/5.7/en/) for details.
   (Bug #23508228)

 * A new option, --skip-final-rescan, makes mysqlbackup skip
   the final rescan for InnoDB tables that are modified by
   DDL operations after the database has been locked near
   the end of a backup operation. This potentially shortens
   the duration for the lock and reduces the backup's impact
   on the server's normal operation. See the description for
   --skip-final-rescan for details. (Bug #21094221)

 * The output by mysqlbackup, which goes to the stderr
   stream and the message log, has now been improved to
   include the timestamps and thread IDs for all steps taken
   by mysqlbackup, in order to provide more information for
   debugging purposes. (Bug #20142619)

 * During the final stage of a backup when MySQL Enterprise
   Backup tried to temporarily put the database into a
   read-only state using the FLUSH TABLES WITH READ LOCK
   statement in order to copy non-InnoDB files, if a long
   query was running on the server at the same time, the
   FLUSH TABLES WITH READ LOCK statement could be taking too
   long to finish, holding up further queries and eventually
   bringing down the server.
   A new mysqlbackup option --lock-wait-timeout can now be
   used to specify the timeout in seconds for the FLUSH
   TABLES WITH READ LOCK statement. If the timeout is
   exceeded, the statement is failed and the lock on the
   tables is released, so that queries held up by the lock
   can then be executed. mysqlbackup then retries the
   statement and continues with the backup. Default value
   for --lock-wait-timeout is 60 [seconds]. (Bug #14339483)

 * A full set of exit codes have now been implemented for
   MySQL Enterprise Backup. Also, a new mysqlbackup command,
   print-message, returns an exit message for any given exit
   code supplied with the new option --error-code. See Exit
   codes of MySQL Enterprise Backup
   (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/en/ 

meb-exitcodes.html 
) 
for details.


 * To increase the performance for hot backups, mysqlbackup
   now shortens the final phase of the backups by resizing
   the MyISAM key cache before it locks the database with a
   FLUSH TABLES WITH READ LOCK statement. The resize
   triggers a flush of the MyISAM key cache, which reduces
   the time it takes to run the FLUSH TABLES WITH READ LOCK
   statement. The MyISAM key cache size is changed back to
   its original value afterward.

 * Apply-log operations can now be performed with multiple
   worker threads in parallel, which can improve performance
   for the operations. The number of threads to be used can
   be specified with the --process-thread option.

 * The copying of redo log files into backups has been made
   faster, shortening the overall backup time in some cases
   and making it less likely that a backup fails because a
   redo log file has been overwritten before it is copied.

 * MySQL Enterprise Backup now supports optimistic
   incremental backup, in which mysqlbackup scans only those
   InnoDB data files that have been modified since the last
   backup for changed pages and then saves them into the
   incremental backup. It potentially makes incremental
   backups faster, and is performed by specifying
   --incremental=optimistic. See Full-scan versus Optimistic
   Incremental Backup
   (http://dev.mysql.com/doc/mysql-enterprise-backup/4.1/ 

MySQL Connector/C++ 2.0.3 m3 Development Release has been released

[karen langford]

Dear MySQL users,

MySQL Connector/C++ 2.0.3 is the next development milestone of the MySQL
Connector/C++ 2.0 series, and the first public release. Apart from
covering more X DevAPI features, it adds a new, plain C API, called
XAPI, that offers functionality similar to X DevAPI to applications
written in plain C. Thus, not only can MySQL Connector/C++ be used to
write C++ applications, as before. Now, using the XAPI, MySQL
Connector/C++ can be used to write plain C applications to access MySQL
Database implementing a document store as well as execute traditional
plain SQL statements. For more information about XAPI, refer to the
documentation at
http://dev.mysql.com/doc/dev/connector-cpp/xapi_ref.html.

To learn more about how to write applications using the X DevAPI, see X
DevAPI User Guide (http://dev.mysql.com/doc/x-devapi-userguide/en/). For
more information about how to use Connector/C++ 2.0 and how the X DevAPI
is implemented in it, see http://dev.mysql.com/doc/dev/connector-cpp/.

Note

The X DevAPI requires at least MySQL Server version 5.7.12 or higher
with the X Plugin enabled. For general documentation about how to get
started using MySQL as a document store, see Using MySQL as a Document
Store (http://dev.mysql.com/doc/refman/5.7/en/document-store.html).

To download MySQL Connector/C++ 2.0.3 m3, see the "Development Releases"
tab at http://dev.mysql.com/downloads/connector/cpp/

X DevAPI Notes

 * New X DevAPI features added in this MySQL Connector/C++
   release:

  + Methods for starting and controlling transactions

  + Using an X DevAPI URI or connection string to
specify new session parameters

  + Capability of binding a session to the default shard
and execute SQL statements there (using
XSession.bindToDefaultShard())

  + Methods for counting elements in a table or
collection

  + Access to multiple result sets if present in a query
result

  + Methods to count items in a result set and fetch a
complete result set at once (using fetchAll()),
instead of accessing items one by one (using
fetchOne())

  + Access to warnings reported when processing a
statement (getWarnings())

  + Access to information about affected rows, generated
auto-increment values, and identifiers of documents
added to a collection


On Behalf of the MySQL/ORACLE RE Team


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Notifier 1.1.7 has been released

[karen langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL Notifier version 1.1.7, the latest addition to the MySQL
Installer for Windows.

MySQL Notifier enables developers and DBAs to easily monitor, start and
stop all their MySQL database instances. It provides a familiar
Microsoft SQL Server look and feel and integrates with MySQL Workbench.

MySQL Notifier is installed using the MySQL Installer for Windows.

The MySQL installer comes in 2 versions

- Full (150 MB) which includes a complete set of mysql products with
  their binaries included in the download

or

- Web (1.5 MB - a network install) which will just pull the MySQL
  Notifier over the web and install it when run.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.


Changes in MySQL Notifier 1.1.7 (2016-08-01)

   Functionality Added or Changed

 * The automatic migration of connections from MySQL
   Notifier to MySQL Workbench can now be delayed for a
   period of time or suspended indefinitely.

 * An option for setting the interval to ping monitored
   MySQL server instances for status changes was added to
   the Actions, Options menu.

   Bugs Fixed

 * The Configure Instance option was renamed to Manage
   Instance. (Bug #24339668)

 * An error was displayed when valid domain user credentials
   were used to add a remote Windows service. (Bug
   #24305736)

 * Testing new connections for remote MySQL instances would
   display a "High Severity Error" message. (Bug #24010582)

 * When MySQL Notifier was installed using MySQL Installer,
   an exception was thrown and MySQL Notifier failed to
   start. (Bug #23762891)

 * The SQL Editor link to MySQL Workbench was disabled for
   each monitored MySQL instance or service when MySQL
   Workbench was installed. (Bug #23748734)

 * Validation checking identified domain\username as an
   invalid format to use when adding a remote Windows
   service to be monitored. Now, domain users with
   sufficient permissions to access the remote computer can
   connect using the domain\username format. (Bug #23746334)

 * The main XML element in %APPDATA%\Oracle\MySQL
   Notifier\settings.config was renamed to MySQLNotifier
   from MySQLForExcel. Indentations were added to improve
   the overall readability of configuration settings. (Bug
   #23740262)

 * Windows services on a remote computer were not retrieved
   and could not be added to the list services to be
   monitored. (Bug #23667056)

 * A corrupted connections.xml file caused MySQL Notifier to
   display a "Root element is missing" error message when
   started. (Bug #22160640, Bug #73540)

 * Attempts to subscribe to a remote Windows service for the
   first time failed and returned a "High Severity Error"
   message when the remote service was an instance of MySQL.
   (Bug #20389122, Bug #75319)

 * Case-sensitive naming prevented status changes to MySQL
   instances running as services for Windows. Now, service
   names for MySQL instances are added with compatible
   casing. (Bug #19881188, Bug #74516)

 * A "High Severity Error" raised by MySQL Notifier appeared
   intermittently during installations performed using MySQL
   Installer. (Bug #17825477)


You can access the MySQL Notifier documentation at
http://dev.mysql.com/doc/refman/5.6/en/windows-notifier.html.

You can find our team's blog at http://blogs.oracle.com/MySQLOnWindows.

You can also post questions on our MySQL Notifier forum found at
http://forums.mysql.com/.

Enjoy and thanks for the support!


MySQL Notifier Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Enterprise Backup 4.0.2 has been released

[karen langford]

Dear MySQL users,

MySQL Enterprise Backup v4.0.2, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

MySQL Enterprise Backup v4.0.2 supports only the MySQL Server 5.7.9 and 
above.

For any earlier versions of the MySQL server, please use
MySQL Enterprise Backup 3.12 instead.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.0.2 is given below.

Changes in MySQL Enterprise Backup 4.0.2 (2016-07-26)

Functionality Added or Changed

 * When there were no tables matching the regular expression
   specified with the --include-table option during a backup
   operation, mysqlbackup still created a backup, which
   contained an empty folder for each database on the
   server. mysqlbackup now throws an error when
   --include-tables selects no tables to be backed up. (Bug
   #18114353)

 * MySQL Enterprise Backup can now backup and restore
   encrypted InnoDB tables. See Working with Encrypted
   InnoDB Tables and Options for Working with Encrypted
   InnoDB Tablespaces for details.

   Bugs Fixed

 * When trying to restore a compressed image backup of a
   server that had separate undo tablespaces residing in the
   data directory with the copy-back-and-apply-log command,
   the operation failed at the apply-log phase, as
   mysqlbackup could not load the undo tablepaces. (Bug
   #23583961)

 * Attempts to restore an image backup from the cloud using
   the --skip-binlog option failed with a "global tail magic
   mismatch" error. This was because mysqlbackup failed to
   perform a non-sequential read from the cloud with gaps
   caused by the skipping of the binary logs. This fix makes
   sure mysqlbackup can perform such reads. (Bug #23534700)

 * When a compressed backup was being restored, if the undo
   logs had been put into separate tablespaces outside of
   the data directory on the backed up server, they got
   restored twice, once mistakenly as general tablespaces
   with the .ibd extension, and once as undo tablespaces
   without a file extension. This fix makes sure they are
   restored normally as undo tablespaces only. (Bug
   #23179194)

 * An extract operation for an image backup failed with a
   checksum mismatch error in cases when, during the backup,
   an InnoDB tablespace file kept growing in size, and
   mysqlbackup failed to put the correct file size in its
   file header. (Bug #22905984)
   References: This issue is a regression of: Bug #22613568.

 * During a mysqlbackup operation on a compressed backup
   (that is, the --uncompress option was used), mysqlbackup,
   in some situations, wrote to the log file multiple
   instances of the message "ERROR: InnoDB: file write at
   offset > 4 GB," even though the operation was actually
   successful. (Bug #22733760)

 * Occasionally, some files were missing from an image
   backup created by the --backup-to-image command. It was
   due to an internal race condition, which this fix
   eliminates. (Bug #19600687)

The complete manual for MEB 4.0.2 is at
http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html

The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).

You can also download the binaries from MOS, https://support.oracle.com
Choose the "Patches & Updates" tab, and then use the "Product or Family
(Advanced Search)" feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/
for the product "MySQL Enterprise Backup"

Thanks,

On behalf MySQL RE team at Oracle

Sreedhar S


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 6.9.9 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.9 is a maintenance release for the 6.9.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.9.9 (2016-07-01)


   Functionality Added or Changed

 * Added TLS support for TLSv1.1 and TLSv1.2 when connecting
   to MySQL Server 5.7.

   Bugs Fixed

 * Improvements were made to how the connector handles
   aborted connections. (Bug #23346197, Bug #80997)

 * With Entity Framework 6, building a table with a primary
   key would not enclose the key name in quotes, which
   caused a syntax error. (Bug #22696180, Bug #22696207, Bug
   #76292)

 * The connector was not disposing the transaction returned
   by DBContext.Database.BeginTransaction() when exiting a
   using code block. (Bug #22514355, Bug #22514363)

 * The connector did not attempt to enumerate stored
   procedures via mysql.proc(). Instead it looked up stored
   procedures in INFORMATION_SCHEMA.ROUTINES. This could
   have led to performance degradation in certain scenarios.
   (Bug #20960373, Bug #23528155, Bug #74116)


The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/6.9.9
https://www.nuget.org/packages/MySql.Data.Entity/6.9.9
https://www.nuget.org/packages/MySql.Fabric/6.9.9
https://www.nuget.org/packages/MySql.Web/6.9.9


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL for Visual Studio 2.0.2 m1 Development Release has been released

[karen langford]

Dear MySQL users,

MySQL for Visual Studio 2.0.2 M1 is the first development release of the
MySQL for Visual Studio 2.0 series.  This series adds support for the
new X DevAPI. The X DevAPI enables application developers to write code
that combines the strengths of the relational and document models using
a modern, NoSQL-like syntax that does not assume previous experience
writing traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information about
how the X DevAPI is implemented in MySQL for Visual Studio, and its usage,
see http://dev.mysql.com/docs/refman-5.7/en/mysql-shell-visual-studio.html.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

Changes in MySQL for Visual Studio 2.0.2 (2016-04-11, Milestone 1)

   Known limitation of this release: SSL connections are not yet
   supported.

   Functionality Added

 * Added support for Visual Studio 2015 with .NET Framework
   4.6.

 * Added support for Python scripts. Python code can now be
   executed and can interact with the X DevAPI introduced in
   MySQL 5.7.12, where relational and document data can be
   queried. Extended views (Field Types, Query Statistics and
   Execution Plan) are not available for Python in this version.

 * Added new result views for document-based (JSON) data
   returned by MySQL X, where data can be viewed in a grid,
   tree, or text representation.

 * Added a new Javascript query type, in addition to SQL
   type that was already present. JavaScript code can be
   executed and interact with the X DevAPI introduced in
   MySQL 5.7.12, where relational and document data can be
   queried. Extended views (Field Types, Query Statistics
   and Execution Plan) are not available for JavaScript in
   this version.

 * Enhanced the user interface for query scripts where
   different views for result sets returned by the MySQL
   Server are now available, similar to the ones in MySQL
   Workbench. For SQL scripts the available views are:

  + Results: shows returned data

  + Field Types: shows information about columns of a
result set, such as names, data types, character
sets, and more.

  + Query Statistics: shows information about the
executed query, such as execution times, processed
rows, index and temporary tables usage, and more.

  + Execution Plan: shows a text-view explanation of the
query execution performed internally by the MySQL
Server.

 * After MySQL scripts are executed, each result set
   returned by the MySQL Server is now displayed in a
   separate Results tab. In previous versions, only the last
   result set returned by MySQL Server was displayed in the
   Output tab.

 * Added an option to create MySQL scripts directly from a
   MySQL Server instance in the Server Explorer. This
   simplifies the process of creating scripts, as there is
   no longer a requirement to open a connection for each
   script like in previous versions of MySQL for Visual
   Studio.

   Bugs Fixed

 * Fixed the coloring of SQL code so it is readable on any
   VS color theme, like the "Dark" one.


On behalf of the MySQL Release Team

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/Node.js 1.0.2 m1 Development Release has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Node.js is a new Node.js driver for use with the X
DevAPI. This release, v1.0.2 M1, is the first development release of the
MySQL Connector/Node.js 1.0 series.

The X DevAPI enables application developers to write code that combines
the strengths of the relational and document models using a modern,
NoSQL-like syntax that does not assume previous experience writing
traditional SQL.

To learn more about how to write applications using the X DevAPI, see
http://dev.mysql.com/doc/x-devapi-userguide/en/. For more information
about how the X DevAPI is implemented in MySQL Connector/Node.js, and
its usage, see http://dev.mysql.com/doc/dev/connector-nodejs/.

Please note that the X DevAPI requires at least MySQL Server version
5.7.12 or higher with the X Plugin enabled. For general documentation
about how to get started using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html.

Changes in MySQL Connector/Node.js 1.0.2 (2016-04-11, Milestone 1)

   Functionality Added

 * Added support for the new X Dev API that was introduced
   in MySQL Server 5.7.12.


Enjoy and thanks for the support!

On behalf of the MySQL Release Team

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Shell 1.0.3 m1 Development Release has been released

[karen langford]

Dear MySQL users,

Today we are excited to announce for the first time the MySQL Shell, a
new component for the MySQL Server.

The MySQL Shell is an interactive JavaScript and Python command-line
interface, supporting development and administration for the MySQL
Server. The MySQL Shell enables developers to use a new Create Read
Update Delete (CRUD) API. MySQL Shell is a component of the MySQL
Server.

This is a Developer Release, so we are looking forward to getting your
feedback on the MySQL Shell as well as the new API and all the other new
features.

The MySQL Shell provides

 * Both Interactive and Batch operations

 * JavaScript, Python, and SQL language modes

 * Document and Relational Models

 * CRUD Document and Relational API via scripting

 * Output results in Traditional Table, JSON, and Tab Separated 
formats


 * Global and Stored Sessions

 * And much more


To download the MySQL Shell
http://dev.mysql.com/downloads/shell

To learn more about MySQL Shell, a component of the MySQL Server, see
http://dev.mysql.com/doc/refman/5.7/en/mysql-shell.html

To learn more about using MySQL as a document store, see
http://dev.mysql.com/doc/refman/5.7/en/document-store.html

For MySQL Shell Tutorials
JavaScript - 
http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-javascript.html 

Python - 
http://dev.mysql.com/doc/refman/5.7/en/mysqlx-shell-tutorial-python.html


User documentation for the new X DevAPI
http://dev.mysql.com/doc/x-devapi-userguide/en/index.html


On behalf of the MySQL Engineering Group

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/ODBC 5.3.6 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/ODBC 5.3.6, a new version of the ODBC driver for
the MySQL database management system, has been released.

The available downloads include both a Unicode driver and an ANSI
driver based on the same modern codebase. Please select the driver type
you need based on the type of your application - Unicode or ANSI.
Server-side prepared statements are enabled by default. It is suitable
for use with any MySQL version from 5.5 onward.

This is the third release of the MySQL ODBC driver conforming to the
ODBC 3.8 specification. It contains implementations of key 3.8 features,
including self-identification as a ODBC 3.8 driver, streaming of output
parameters (supported for binary types only), and support of the
SQL_ATTR_RESET_CONNECTION connection attribute (for the Unicode driver
only).

Also, Connector/ODBC 5.3 introduces a GTK+-based setup library
providing a GUI DSN setup dialog on some Unix-based systems, currently
included in the Oracle Linux 6 and Debian 6 binary packages. Other new
features in the 5.3 driver are FileDSN and Bookmarks support.

The release is now available in source and binary form for a number of
platforms from our download pages at

   http://dev.mysql.com/downloads/connector/odbc/5.3.html

For information on installing, please see the documentation at

http://dev.mysql.com/doc/refman/5.6/en/connector-odbc-installation.html

Enjoy!

The MySQL Connectors team at Oracle


Changes in MySQL Connector/ODBC 5.3.6 (2016-03-17)

   Security Notes

 * Security Fix: The linked OpenSSL library for
   Connector/ODBC Commercial 5.3.6 has been updated from
   version 1.0.1m to version 1.0.1q. Versions of OpenSSL
   prior to 1.0.1q are reported to be vulnerable to
   CVE-2015-3195
   (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2015-3195).
   This change does not affect the Oracle-produced MySQL
   Community build of Connector/ODBC 5.3.6, which uses the
   yaSSL library instead. (CVE-2015-3195)

   Functionality Added or Changed

 * Two new option parameters, DISABLE_SSL_DEFAULT and
   SSL_ENFORCE, have been introduced for specifying whether
   the default requirement to use SSL connections is to be
   followed. See Connector/ODBC Option Parameters
   (http://dev.mysql.com/doc/connector-odbc/en/connector-odb 

	c 
-configuration-connection-parameters.html#codbc-dsn-opti 

	on-flags 
) for details. (Bug #21027928)


   Bugs Fixed

 * The function MySQLGetPrivateProfileStringW() used
   malloc() to allocate memory and then xfree() to free the
   allocated memory for a returned value. That caused some
   issues when certain third-party versions of MySQL client
   library (like MariaDB 10.x) was used. The issues have
   been fixed by replacing malloc() with my_malloc(). (Bug
   #21074676, Bug #76984)

 * Attempt to build Connector/ODBC from source on a Linux
   platform against the client library and header files
   shipped with MySQL server 5.7.6 or newer failed. It was
   due to the changes made to the client library and the
   header files, to which Connector/ODBC has now been
   adapted. (Bug #20685833)

 * An application that used ActiveX Data Objects (ADO) and
   the Connector/ODBC ANSI driver hung after trying to write
   French characters to a database that used the UTF-8
   character set. (Bug #20526062)

 * Calling the SQLGetDiagField function with the
   DiagIdentifier SQL_DIAG_ROW_COUNT always returned "0,"
   even if there were updated, deleted, or modified rows.
   (Bug #16920750)

 * Because Connector/ODBC did not parse comments properly,
   the parameter markers embedded in comments caused the
   complaint that SQLBindParameter was not used for all
   parameters. (Bug #16613308, Bug #53891)


On behalf on the MySQL RE Team.

MySQL for Visual Studio 1.2.5 has been released

[karen langford]

Dear Users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Visual Studio 1.2.5.

This is a maintenance release for the 1.2 release series. It can be
used for production environments.

MySQL for Visual Studio is a product that includes all of the Visual
Studio integration functionality to create and manage MySQL databases
when developing .NET applications.

MySQL for Visual Studio is installed using the MySQL Installer for
Windows which comes in 2 versions:

   . Full (150 MB) which includes a complete set of MySQL products with
   their binaries included in the downloaded bundle.

   . Web (1.5 MB - a network install) which will just pull MySQL for
   Visual Studio over the web and install it when run.


You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.


MySQL for Visual Studio can also be downloaded by using the product
standalone installer found at
http://dev.mysql.com/downloads/windows/visualstudio/.


Changes in MySQL for Visual Studio 1.2.5 (2015-10-29)

This section documents all changes and bug fixes applied to MySQL for
Visual Studio since the release of 1.2.5. Several new features were
added to the 1.2.x branch, for more information see the section below
called: What Is New In MySQL for Visual Studio 1.2.


   Known Limitations:

  . Item templates do not work correctly with MySQL Server 5.7.x,
as it prevents the creation of an Entity Framework model.


   Functionality Added or Changed

  . Added the Entity Framework option to the MySQL Website
Configuration dialog for web projects, so Entity Framework
version 5 or 6 can be used with a MySQL database provider.
These automatically add the configuration/references needed
to the web.config file and the project itself. Also, all available
configuration options are now listed in the dialog.

  . Project Templates were replaced with Project Items.
The Project Templates option was removed from the plugin
toolbar, and from the Project menu, in order to add the Project
Items feature with two options: MySQL New MVC Item and

MySQL New Windows Form, which are available on the Add New
Item dialog when adding a new Project Item. They add new
windows forms or MVC controllers/views connected to MySQL.


   Bugs Fixed

  . The Installer could not uninstall MySQL for Visual Studio if Visual
Studio was uninstalled first. (Bug #21953055, Bug #71226)

  . In v1.2.4, the Launch Workbench and Open MySQL Utilities
Console toolbar buttons were disabled. (Bug #21495692)

  . The Templates installer feature could not be uninstalled via
Add/Remove Programs. Because Project Templates were
replaced by Project Items, this is no longer a concern.
(Bug #21488922, Bug #77802)

  . The dataset designer wizard was not showing the stored
procedure parameters when creating a "TableAdapter" using
existing stored procedures for the "Select" command. Also,
the stored procedure command had an "error" thus causing the
dataset to not be created. (Bug #20233133, Bug #74195)


What Is New In MySQL for Visual Studio 1.2
--

. New MySQL Project Items for creating data views in Windows Forms and
  ASP.NET MVC web applications.

. A new option in web configuration tool for the ASP.NET Personalization
  Provider (this feature requires MySQL Connector/NET 6.9 or newer).

. A new option in web configuration tool for the ASP.NET Site Map
  Provider (this feature requires MySQL Connector/NET 6.9 or newer).

. A new option for the MySQLSimpleMembership provider in the web
  configuration tool. (This feature requires MySQL Connector/NET or
  newer).


MySQL Windows Forms Project Item


This Project Item is available on the Add New Item dialog in Visual
Studio when adding a new item to an existing project.

The dialog presented to create the MySQL Windows Forms Project Item
automates the generation of a Windows Form, representing a view for
MySQL data available through an existing Entity Framework's model entity
containing a MySQL table or view. Different view types are available to
present the data:

   . Single-column: A form that contains one control by each existing
 column in the table with navigation controls and that allows CRUD
 operations.All controls can include validations for numeric and
 DateTime data types.

   . Grid: A form with a data grid view that contains navigation
 controls.

   . Master-detail: A form with a single control layout for the Parent
 table and a data grid view to navigate through child table's data.

Supported with C# or Visual Basic language. This feature requires
Connector/NET 6.7.5, 6.8.3 or 6.9.x.

For more details on the features included check the documentation at:

MySQL for Visual Studio 1.2.5 has been released

[karen langford]

Dear MySQL users,

MySQL for Visual Studio is a product that includes all of the Visual
Studio integration functionality to create and manage MySQL databases
when developing .NET applications. This is a maintenance release for
1.2.x.  It is feature complete and is suitable for production
environments.

This version is appropriate for using with MySQL server versions
5.5-5.6.  The 5.7 server version is also compatible but is not fully
supported, thus it should be used at your own discretion.

As this is a maintenance release of the MySQL for Visual Studio product,
it can be downloaded by using the product standalone installer at this
link http://dev.mysql.com/downloads/windows/visualstudio/ or with the
MySQL Windows Installer.

Changes in MySQL for Visual Studio 1.2.5 (2015-10-29)

   Known Limitation:

   Item templates do not work correctly with MySQL Server 5.7.x, as it
   prevents the creation of an Entity Framework model.

   Functionality Added or Changed

 * Added the Entity Framework option to the MySQL Website
   Configuration dialog for web projects, so Entity
   Framework version 5 or 6 can be used with a MySQL
   database provider. These automatically add the
   configuration/references needed to the web.config file
   and the project itself. Also, all available configuration
   options are now listed in the dialog.

 * Project Templates were replaced with Item Templates.
   The Project Templates option was removed from the plugin
   toolbar, and from the Project menu, in order to add the
   Item Templates feature with two options: MySQL MVC Item
   and MySQL Windows Forms Item, which are available as a
   context menu for existing projects. They add new windows
   forms or MVC controllers/views connected to MySQL.

   Bugs Fixed

 * The Installer could not uninstall MySQL for Visual Studio
   if Visual Studio was uninstalled first. (Bug #21953055,
   Bug #71226)

 * In v1.2.4, the Launch Workbench and Open MySQL Utilities
   Console toolbar buttons were disabled. (Bug #21495692)

 * The "Templates" could not be uninstalled via Add/Remove
   Programs. Because Project Templates were replaced by Item
   Templates, this is no longer a concern. (Bug #21488922,
   Bug #77802)

 * The dataset designer wizard was not showing the stored
   procedure parameters when creating a "TableAdapter" using
   existing stored procedures for the "Select" command.
   Also, the stored procedure command had an "error" thus
   causing the dataset to not be created. (Bug #20233133,
   Bug #74195)


What's new in the 1.2 version
-
- A new MySQL Project Wizard for creating Windows Forms applications.
- A new MySQL Project Wizard for creating ASP.NET MVC web applications.
- A new option in web configuration tool for the ASP.NET Personalization
  Provider (this feature requires Connector/Net 6.9).
- A new option in web configuration tool for the ASP.NET Site Map
  Provider (this feature requires Connector/Net 6.9).
- A new option for the MySQLSimpleMembership provider in the web
  configuration tool. (This feature requires Connector/Net 6.9
  installed).



MySQL Project Wizard for Windows Forms
--
The Windows Forms Project Wizard is available at the Visual Studio New
Project dialog, either at the MySQL category or by filtering by name.
It also can be accessed by using the MySQL Toolbar inside Visual Studio.
This wizard automates the generation of a .NET Windows Forms Application
that is connected to a MySQL data source. A Typed DataSet or an Entity
Framework Model can also be generated to link the Application to the MySQL
Database.  The user can select one or more tables that exists in the
database. Each table can have a different type of view. The types of views
that are available in this version are:

Single Layout: A form that contains one control by each existing column
in the table with navigation controls and that allows CRUD operations.
All controls can include data typed validations for Numeric types and
Datetime types.  Grid layout: A form with a Grid that contains
navigation controls.  Master-Detail: A form with a single controls
layout for the Parent table and a grid to navigate in the child table.
Supported with C# or Visual Basic language.
This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x

For more details on the features included check the documentation at :
http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio-windows-forms.html


MySQL Project Wizard for ASP.NET MVC

The ASP.NET MVC Project Wizard is available at the Visual Studio New
Project dialog, either at the MySQL category or by filtering by name. It
also can be accessed by using the MySQL Toolbar inside Visual Studio.

This wizard automates the generation of an ASP.NET MVC. The MVC versions
supported for this 

MySQL for Excel 1.3.5 has been released

[karen langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.5. This is a maintenance release for 1.3.x.
It can be used for production environments.

MySQL for Excel is an application plug-in enabling data analysts to very
easily access and manipulate MySQL data within Microsoft Excel. It
enables you to directly work with a MySQL database from within Microsoft
Excel so you can easily do tasks such as:

  * Importing MySQL Data into Excel

  * Exporting Excel data directly into MySQL to a new or existing table

  * Editing MySQL data directly within Excel


MySQL for Excel is installed using the MySQL Installer for Windows.

The MySQL Installer comes in 2 versions

- Full (150 MB) which includes a complete set of MySQL products with
  their binaries included in the download.

- Web (1.5 MB - a network install) which will just pull the MySQL for
  Excel over the web and install it when run.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link
http://dev.mysql.com/downloads/windows/excel/


Changes in MySQL for Excel 1.3.5 (2015-10-23)

   Functionality Added or Changed

 * Added support for the JSON data type that was added in
   MySQL Server 5.7.

   The JSON data type is now selectable from the Export Data
   column dialog, if the advanced option to show all data
   types is enabled. All data operations (Import, Export,
   Append and Edit) now function with the JSON data type.

 * Added a new advanced option to Show column data types
   above column names. When checked, the Append Data dialog
   grid will show data type information for columns on
   source and target grids. This is especially helpful when
   manually mapping columns.

 * A new Append Data advanced option was added, titled
   Confirm column mapping overwriting. When enabled, dragging and
   dropping source columns over target columns that were already
   mapped (in other words, they already contained a mapped source
   column) now triggers a confirmation dialog asking if the
   overwrite should be executed. This option is disabled by default
   as data overwrite is a common operation. (Bug #16239058)

   Bugs Fixed

 * Attempting to save data to a column where the data can
   not be written (incompatible data type) now generates an
   error. (Bug #21898699, Bug #78550)

 * Changed the way data type related warnings are linked to
   grid columns in the Append Data dialog. Now the warnings
   are linked to the target (lower) grid view columns,
   because a single source column can be mapped to multiple
   target columns, and the warnings are about source data
   not being suitable for the target column's data type.
   (Bug #21898678, Bug #78549)

 * When scrolling the target MySQL table grid horizontally,
   the upper column headers that contained names of the
   mapped source columns were not rendering text properly.
   The text moved while scrolling, and the column separators
   disappeared when scrolling to the right. (Bug #21898210,
   Bug #78548)

 * Change the data type detection logic for a column's data
   that was failing when only the first row of data
   contained data, when the rest of the rows were empty.
   (Bug #21799680, Bug #78358)

 * Connection information created after the last save was
   cleared from memory when an Excel Workbook was closed,
   thus causing the connection information to not write to
   disk. Now the connection cleanup happens after a
   Workbench is saved, thereby saving the new connection
   information. (Bug #21172751, Bug #21089790, Bug #76475,
   Bug #73467)

 * Stopped using hidden defined names to store formulas that
   transform date values into a date format used by MySQL.
   These defined names were being detected by Excel as
   macros or user functions that could not be saved in
   macro-free workbooks, thus generating bogus warnings
   every time a Workbook was saved when the Excel plugin was
   active. (Bug #19358961, Bug #73467)

 * Updated the data connection library to Connector/NET
   v6.9.8, which fixes the problem of accessing a schema
   that contained Unicode (non-ASCII) characters in its
   name. These databases now successfully open. (Bug
   #17409832)

 * Deleted stored mappings would remain in the stored
   mapping method list. (Bug #16493255)

 * Enhanced the custom grid view control used in the Append
   Data dialog to automatically adjust the width of the grid
   columns. This adjustment considers the grid's cell
   contents, the base column header text, and also the
   contents of the additional 

MySQL Enterprise Backup 4.0.0 has been released

[karen langford]

Dear MySQL users,

MySQL Enterprise Backup v4.0.0, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) 
website
as our latest GA release. This release will be available on eDelivery 
(OSDC)

after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

MySQL Enterprise Backup v4.0.0 supports only the MySQL server 5.7.9 and 
above.

For any earlier versions of the MySQL server, please use
MySQL Enterprise Backup 3.12 instead.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 4.0.0 is given below.

Changes in MySQL Enterprise Backup 4.0.0 (2015-10-21)

   Functionality Added or Changed


 *  MySQL Enterprise Backup 4.0 supports MySQL server 5.7, on
which:

  + Tables in general tablespaces
(http://dev.mysql.com/doc/refman/5.7/en/glossary.htm
l#glos_general_tablespace 
) 
can be backed up and

restored.

  + InnoDB tables with page sizes
(http://dev.mysql.com/doc/refman/5.7/en/glossary.htm
l#glos_page_size 
) 
of 32 and 64K can be backed up and

restored.

  + Partitioned tables can be selectively backed up or
restored using the --use-tts, --include-tables, and
--exclude-tables options.
   See What's New in MySQL Enterprise Backup 4.0?
   (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/
what-is-new.html 
) 
for details.


 * MySQL Enterprise Backup now writes tape information onto
   the MySQL server when a backup is made to a tape using
   the System Backup to Tape (SBT) API. See What's New in
   MySQL Enterprise Backup 4.0?
   (http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/
what-is-new.html 
) 
for details.


   Bugs Fixed

 * When restoring an incremental backup image, if the binary
   log in the backup was larger than 16MB, the restored
   binary log would become corrupted. (Bug #20915642)

 * When the --password option was used without an argument
   with the copy-back-and-apply-log command, mysqlbackup did
   not prompt user for a password, but either took the
   password from the defaults files, or took it to be an
   empty string when no value was specified in the defaults
   files. (Bug #20915642)


The complete manual for MEB 4.0.0 is at
http://dev.mysql.com/doc/mysql-enterprise-backup/4.0/en/index.html

The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).

You can also download the binaries from MOS, https://support.oracle.com
Choose the "Patches & Updates" tab, and then use the "Product or Family
(Advanced Search)" feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/
for the product "MySQL Enterprise Backup"

Thanks,

On behalf MySQL RE team at Oracle

Sreedhar S

MySQL Connector/NET 6.9.8 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.8 is a maintenance release for the 6.9.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.9.8 (2015-10-20)

   Functionality Added or Changed

 * The GB18030 Chinese character set is now supported, a
   character set that was added in MySQL 5.7.4. (Bug
   #21098546, Bug #21803306, Bug #21803300)

 * Generated columns (GENERATION_EXPRESSION) are now
   supported, a feature added in MySQL 5.7.6.

 * The JSON type is now supported, a type that was added in
   MySQL 5.7.8.


The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/6.9.8
https://www.nuget.org/packages/MySql.Data.Entity/6.9.8
https://www.nuget.org/packages/MySql.Fabric/6.9.8
https://www.nuget.org/packages/MySql.Web/6.9.8


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/C++ 1.1.6 has been released

[karen langford]

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C++ has
been made available: MySQL Connector/C++ 1.1.6 GA. The MySQL
Connector/C++ provides a C++ API for connecting client applications to
the MySQL Server 5.5 or newer.

You can download the production release at:

http://dev.mysql.com/downloads/connector/cpp/1.1.html

MySQL Connector C++ (Commercial) will be available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month's upload cycle.

The MySQL driver for C++ offers an easy to use API derived from JDBC
4.0. MySQL Workbench has used it successfully for years.

We have improved the driver since the last GA release. Please see the
documentation and the CHANGES file in the source distribution for a
detailed description of bugs that have been fixed. Bug descriptions are
also listed below.

Enjoy!

The MySQL build team at Oracle

==

Changes in MySQL Connector/C++ 1.1.6 (2015-06-10)

   Security Notes

 * Security Fix: Connector/C++ 1.1.6 Commercial upgrades the
   linked OpenSSL library to version 1.0.1m which has been
   publicly reported as not vulnerable to CVE-2015-0286
   (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-20
   15-0286). (CVE-2015-0286)

   Functionality Added or Changed

 * The std::auto_ptr class template is deprecated in C++11,
   and its usage has been replaced with
   boost::scoped_ptr/shared_ptr.
   The CMAKE_ENABLE_C++11 CMake option has been added to
   permit enabling C++11 support. (Bug #75251)

 * Connector/C++ now provides macros to indicate the
   versions of libraries against which it was built:
   MYCPPCONN_STATIC_MYSQL_VERSION and
   MYCPPCONN_STATIC_MYSQL_VERSION_ID (MySQL client library
   version, string and numeric), and MYCPPCONN_BOOST_VERSION
   (Boost library version, numeric). (Bug #75250)

   Bugs Fixed

 * With defaultStatementResultType=FORWARD_ONLY and a row
   position after the last row, using getter methods such as
   getInt() or getString() resulted in a segmentation fault.
   (Bug #20085944)

 * For prepared statements, calling wasNull() before
   fetching data resulted in an assertion failure. (Bug
   #19938873)

 * Result sets from prepared statements were not freed. (Bug
   #18135088)

 * MySQL Connector/C++ failed to build against
   Boost-devel-1.41.0-25 on OLE6. (Bug #75063, Bug
   #20125824)

 * Configuration failed if the MYSQL_CONFIG_EXECUTABLE
   option was specified and the MySQL installation path
   contained the characters -m. Installation failed if the
   build directory was not in the top source directory. (Bug
   #73502, Bug #19447498)

 * For prepared statements, getString() did not return the
   fractional seconds part from temporal columns that had a
   fractional sections part. (Bug #68523, Bug #17218692)

 * For queries of the form SELECT MAX(bit_col) FROM
   table_with_bit_col, getString() returned an incorrect
   result. (Bug #66235, Bug #14520822)

 * For Connector/C++ builds from source, make install failed
   if only the static library had been built without the
   dynamic library. (Bug #52281, Bug #11759926)

On Behalf of the MySQL/ORACLE RE Team,

Kent Boortz


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/C 6.1.6 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/C 6.1.6, a new version of MySQL client library for
client/server communication for the MySQL database management system,
has been released.

This version of Connector/C provides full support for MySQL 5.6
protocol. Connector/C is compatible with the client libraries
(libmysql). It includes all the features in the MySQL client library
shipped with MySQL servers 5.6 as well as prior versions. You can
recompile existing code linked with Connector/C 6.1.6 without any code
changes.

You can use Connector/C to run and build client applications which
communicate with MySQL server versions from 5.5 to 5.6 without a need
to do a complete server installation.

The release is now available in source and binary form for a number
of platforms from our download pages at

  http://dev.mysql.com/downloads/connector/c/

MySQL Connector/C 6.1.6 will also be available for downloads via the
Oracle Software Delivery Cloud in approximately 1-2 weeks.

For information on installing, please see the documentation at

http://dev.mysql.com/doc/connector-c/en/connector-c-installation.html

Enjoy!


Changes in MySQL Connector/C 6.1.6 (2015-03-20)

   Security Notes

 * Connector/C 6.1.6 upgrades the linked OpenSSL library to
   version 1.0.1k. Issues fixed in the new version are
   described at
   http://www.openssl.org/news/vulnerabilities.html.

   Functionality Added or Changed

 * yaSSL sources included in Connector/C source packages and
   used in GPL binary distributions were upgraded to version
   2.3.7. (Bug #20201864)

   Bugs Fixed

 * For source packages, it was not possible to build
   Connector/C with the client protocol test trace plugin
   enabled. (Bug #20316149)

 * When there is no change in session state, the OK packet
   sent from server to the client contained an unneeded byte
   at the end of the packet. (Bug #19625718)

 * The client protocol trace plugin did not account for the
   removal of the EOF packet from the client/server protocol
   in MySQL 5.7.5. (Bug #19512199)

 * The mysql_session_track_get_first() and
   mysql_session_track_get_next() C API functions could
   cause a client crash if passed invalid arguments. (Bug
   #18769620)

 * mysql_config --libs_r produces output containing link
   flags for libmysqlclient_r, even though that library was
   removed in MySQL 5.5 and replaced with a symlink to the
   underlying libmysqlclient library. The output now refers
   directly to libmysqlclient. (The implication is that it
   is no longer necessary to maintain the symlink for the
   sake of being able to use mysql_config --libs_r.) (Bug
   #73724, Bug #19506315)

 * Invalid memory access could occur when using prepared
   statements if a mysql client connection was lost after
   statement preparation was complete and there was at least
   one statement that was in initialized state but not
   prepared yet. (Bug #70429, Bug #17512527)

 * Client auto-reconnect did not work for clients linked
   against libmysqlclient, even with MYSQL_OPT_RECONNECT
   enabled.
   Also, if a FEDERATED table was accessed after
   wait_timeout expired, a Lost connection to MySQL server
   error occurred without an attempt to re-establish the
   connection. (Bug #70026, Bug #17309863, Bug #14874, Bug
   #11745408)

 * mysql_real_connect() could close a file descriptor twice
   if the server was not running. (Bug #69423, Bug
   #19226740)

On Behalf of the MySQL/ORACLE RE Team


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL for Excel 1.3.4 has been released

[karen langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.4. This is a maintenance release for 1.3.x.
It can be used for production environments.

MySQL for Excel is an application plug-in enabling data analysts to very
easily access and manipulate MySQL data within Microsoft Excel. It
enables you to directly work with a MySQL database from within Microsoft
Excel so you can easily do tasks such as:

  * Importing MySQL Data into Excel

  * Exporting Excel data directly into MySQL to a new or existing table

  * Editing MySQL data directly within Excel


MySQL for Excel is installed using the MySQL Installer for Windows.

The MySQL Installer comes in 2 versions

- Full (150 MB) which includes a complete set of MySQL products with
  their binaries included in the download.

- Web (1.5 MB - a network install) which will just pull the MySQL for
  Excel over the web and install it when run.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link
http://dev.mysql.com/downloads/windows/excel/

Changes in MySQL for Excel 1.3.4 (2015-03-06)

   Functionality Added or Changed

 * Two new options were added to the Manage Import/Edit
   connection information maintenance dialog. The first is
   used to automatically remove stored connection
   information related to Excel Workbooks that are no longer
   found where they were originally saved. The second new
   option is used to select all connection information
   entries that have not been used in the last n days, where
   n is configurable. (Bug #19789907, Bug #74304)

   Bugs Fixed

 * For Excel 2007, a pop-up warning message incorrectly
   stated that some features could not be saved in a
   macro-free workbook would appear when closing a Workbook
   that was not saved. (Bug #20540331, Bug #75900)
   References: See also Bug #19358961.

 * The Refresh All action did not function on pivot tables.
   Each pivot table had to be individually updated. (Bug
   #20524883, Bug #75565)

 * When a named table in Excel was filtered using the
   standard Excel filtering option, this filter was not
   taken into account when the append function of the MySQL
   for Excel plugin was called. All rows of the table were
   inserted, not just the remaining (filtered) ones. (Bug
   #20433602, Bug #75635)

 * While the Export Data operation automatically assembles
   the SET declaration when detecting values suitable for a
   SET data type (such as lists of values separated by
   commas), the SET declaration assembled by MySQL for Excel
   was incorrect and did not correctly merge all of the
   values nor did it remove the duplicates when generating a
   single list of suitable values. (Bug #20426374, Bug
   #75660)

 * An error similar to Exception from HRESULT: 0x800A03EC
   was generated when importing data with dates older than
   January 1, 1900. Dates older than this are now converted
   to text, as to prevent the COM exception. (Bug #20340588,
   Bug #75450)

 * For Excel 2007, only .xls files were available in the
   Save As dialog. Now, all formats supported by Excel 2007
   are available. (Bug #20296618, Bug #75389)

 * Executing Export Data to a New Table with the Preview SQL
   statements before they are sent to the server option
   enabled would report an incorrect (off by -1) number of
   affected rows under the Review SQL Script dialog. (Bug
   #20286897, Bug #75342)

 * During Data Export, if the number of rows to be exported
   was higher than the number of previewed rows, the export
   operation was restricted to the number of previewed rows.
   A workaround was to increase the number of previewed rows
   to the number of rows being exported. (Bug #20077608, Bug
   #74942)

 * Connection information entries could not be deleted. (Bug
   #19789907, Bug #74304)

 * During an Edit Data session, and after data was added to
   a new row (and the row turned blue to indicate
   uncommitted changes), copying a value from a cell that
   lacked a status color (not modified) and pasting it into
   the new blue row did not retain the blue color. (Bug
   #19783737, Bug #74285)

 * The Import Data, Append Data and Edit Data action labels
   were not disabled after a DB Object was deselected from
   the list. (Bug #18323840)

 * Excel cells selected before MySQL for Excel was launched
   were not recognized, which caused the Export Data action
   label to remain disabled unless cells were selected again
   after MySQL for Excel was opened. (Bug #18323840)

 * When performing an Export Data operation, 

MySQL Connector/NET 6.9.6 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.6 is a maintenance release for the 6.9.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.9.6 (2015-03-04)

   Bugs Fixed

 * The MySqlSimpleRoleProvider.RoleExists method would
   return true instead of false. (Bug #20325391, Bug #73880,
   Bug #75397)

 * With the Driver.GetTimeZoneOffset method, the TimeZone
   offset was not calculated correctly, and instead it was
   always set to 0. In other words, this caused the time
   zone to always be set to UTC. (Bug #20200662, Bug #74134)

 * With Entity Framework 6, passing in a string reference to
   the StartWith clause would return incorrect results. (Bug
   #20129927, Bug #20334228, Bug #20334274, Bug #74918)

 * Repeatedly calling the
   MySql.Web.Security.MySqlSimpleMembershipProvider.Validate
   User method could leave open MySQL connections. (Bug
   #20109419, Bug #75662)

 * The GetTimeZoneOffset method would return an incorrect
   value depending on the server Time and TimeZone, as it
   did not take into account the day into the context of the
   time difference. (Bug #20065691, Bug #20362040, Bug
   #20362036, Bug #74905)

 * The uninstaller process would fail and not remove the
   connector. (Bug #19485102, Bug #73677)

 * A connection string that included Chinese characters for
   a database or uid property would emit the following
   exception; MySqlException: Unknown database '???'. (Bug
   #18141356, Bug #20508130, Bug #70041)

 * Loading two nested collections could be reported as an
   invalid SQL query as MySQL Connector/Net only generated a
   partial query. (Bug #18049862, Bug #20409538, Bug
   #20409528, Bug #70941)

The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/6.9.6
https://www.nuget.org/packages/MySql.Data.Entity/6.9.6
https://www.nuget.org/packages/MySql.Fabric/6.9.6

https://www.nuget.org/packages/MySql.Web/6.9.6


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 6.7.7 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/NET 6.7.7, a new version of the all-managed .NET driver
for MySQL has been released.  This is the GA, is feature complete. It is
recommended for production environments.  It is appropriate for use with
MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsand mirror sites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

The 6.7 version of MySQL Connector/NET brings the following new
features:
-  WinRT Connector.
-  Load Balancing support.
-  Entity Framework 5.0 support.
-  Memcached support for Innodb Memcached plugin.
-  This version also splits the product in two: from now on, starting
   version 6.7, Connector/NET will include only the former Connector/NET
   ADO.NET driver, Entity Framework and ASP.NET providers (Core
   libraries of MySql.Data, MySql.Data.Entity  MySql.Web). While all
   the former product Visual Studio integration (Design support,
   Intellisense, Debugger) are available as part of MySQL Windows
   Installer under the name MySQL for Visual Studio.

WinRT Connector
---
Now you can write MySql data access apps in Windows Runtime (aka Store
Apps) using the familiar API of Connector/NET for .NET.

Load Balancing Support
---
Now you can setup a Replication or Cluster configuration in the backend,
and Connector/NET will balance the load of queries among all servers
making up the backend topology.

Entity Framework 5.0
---
Connector/NET is now compatible with EF 5, including special features of
EF 5 like spatial types.

Memcached
---
Just setup Innodb memcached plugin and use Connector/NET new APIs to
establish a client to MySQL 5.6 server's memcached daemon.


Changes in MySQL Connector/Net 6.7.7 (2015-03-04)

   Bugs Fixed

 * With Entity Framework 6, passing in a string reference to
   the StartWith clause would return incorrect results. (Bug
   #20129927, Bug #20334228, Bug #20334274, Bug #74918)

 * The GetTimeZoneOffset method would return an incorrect
   value depending on the server Time and TimeZone, as it
   did not take into account the day into the context of the
   time difference. (Bug #20065691, Bug #20362040, Bug
   #20362036, Bug #74905)

 * A memory leak was fixed. (Bug #19467233, Bug #19474480,
   Bug #19474510, Bug #73122)

 * The CreateUser function did not trim whitespace before
   storing values into the database, while MembershipUser
   did return trimmed values. The trimming is now performed
   before the data is stored. (Bug #19453313, Bug #19459461,
   Bug #19459436, Bug #73411)

 * Queries with collations using the _utf16le character set
   were not read correctly and instead yielded a not
   presented key in dictionary error. (Bug #19446614, Bug
   #19355906, Bug #19446571, Bug #72737)

 * MySQL Connector/Net would sometimes attempt to call
   stored procedures when it should not. (Bug #19446554, Bug
   #19446523, Bug #19325120, Bug #72736)

 * A connection string that included Chinese characters for
   a database or uid property would emit the following
   exception; MySqlException: Unknown database '???'. (Bug
   #18141356, Bug #20508130, Bug #70041)

 * Loading two nested collections could be reported as an
   invalid SQL query as MySQL Connector/Net only generated a
   partial query. (Bug #18049862, Bug #20409538, Bug
   #20409528, Bug #70941)

The documentation is available at:
http://dev.mysql.com/doc/refman/5.7/en/connector-net.html

Nuget packages are available at:

https://www.nuget.org/packages/MySql.Data/6.7.7
https://www.nuget.org/packages/MySql.Data.Entity/6.7.7
https://www.nuget.org/packages/MySql.Web/6.7.7

Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/Python 2.1.1 Alpha has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Python 2.1.1-alpha is the first alpha version of
2.1 release series of the pure Python database driver for MySQL.
It is intended to introduce users to the new features.

This release is not feature complete but it should be stable
enough for users to understand the new features and how we
expect them to work.

As is the case with all non-GA releases, it should not be used
in any production environment.

MySQL Connector/Python version 2.1.1-alpha is compatible with MySQL
Server versions 5.5 and greater. Python 2.6 and greater as well as
Python 3.3 and greater are supported. Python 2.4, 2.5 and 3.1, 3.2
are not supported.

MySQL Connector/Python 2.1.1-alpha is available for download from:
 http://dev.mysql.com/downloads/connector/python/#downloads

The ChangeLog file included in the distribution contains a brief summary
of changes in MySQL Connector/Python 2.1.1. For a more complete list of
changes, see below or online at:
 http://dev.mysql.com/doc/relnotes/connector-python/en/


=

Changes in MySQL Connector/Python 2.1.1 (2015-02-23)

   C Extension Notes

 * MySQL Connector/Python distributions now are available
   that include a C Extension that interfaces with the MySQL
   C client library. For queries that return large result
   sets, using the C Extension can improve performance
   compared to a pure Python implementation of the MySQL
   client/server protocol.
   For binary Connector/Python distributions, some packaging
   types have a single distribution file that includes the
   pure-Python Connector/Python code together with the C
   Extension. (Windows MSI and OS X Disk Image packages fall
   into this category.) Other packaging types have two
   related distribution files: One that includes the
   pure-Python Connector/Python code, and one that includes
   only the C Extension. For packaging types that have
   separate distribution files, install both distributions
   if you want to use the C Extension. The two files have
   related names, the difference being that the one that
   contains the C Extension has cext in the distribution
   file name.
   Source distributions include both the pure-Python code
   and the C Extension, and distribution names do not
   contain cext. Instead, availability of the C Extension
   is determined by whether you compile the distribution
   with the --with-mysql-capi option.
   Packages for Connector/Python with the C Extension are
   available at the Connector/Python download site
   (http://dev.mysql.com/downloads/connector/python/). For
   installation instructions, see Connector/Python
   Installation
(http://dev.mysql.com/doc/connector-python/en/connector-python-installation.html).
   For information about using the
   C Extension, see The Connector/Python C Extension
(http://dev.mysql.com/doc/connector-python/en/connector-python-cext.html).
   For Connector/Python installations that support the C
   Extension, the use_pure connection argument to connect()
   controls whether to use the extension. If use_pure is
   True (the default), the connection uses pure Python. If
   use_pure is False, the connection uses the C Extension.
   It is also possible to use the C Extension directly, by
   importing the _mysql_connector module rather than the
   mysql.connector module. See The _mysql_connector C
   Extension Module
(http://dev.mysql.com/doc/connector-python/en/connector-python-cext-module.html).

   Bugs Fixed

 * With mysql.connector.django as the engine, the python
   manage.py inspectdb command failed with an Unread result
   found error. (Bug #20022533)

 * If the pool_size and pool_name connection arguments were
   specified using the option file (as opposed to being
   passed explicitly to the connect call), the pooled
   connection was successfully created, but an exception was
   raised when closing it. (Bug #19549363)

 * The Django backend raised an exception when converting
   -00-00 00:00:00 to None. (Bug #73940, Bug
   #19667984)

 * The type_code in cursor.description did not compare equal
   to any of the type objects defined in
   mysql.connector.dbapi. (Bug #73798, Bug #19584051)

 * Data corruption occurred when inserting sufficiently
   large data in a table with a TEXT type column using
   prepared statements, due to incorrect encoding of the
   data length while sending the prepared statement packet.
   (Bug #73690, Bug #19522948)

 * When the character set was binary, character set
   conversion could occur. Conversion is no longer done and
   binary data is returned as is. (Bug #71909, Bug
   #19500097)


Documentation

MySQL Cluster Manager 1.3.3 has been released

[karen langford]

Dear MySQL users,

MySQL Cluster Manager 1.3.3, has been released and can be downloaded
from the My Oracle Support (MOS) website. It will also be available
on Oracle Software Delivery Cloud at http://edelivery.oracle.com with
the next monthly update.

MySQL Cluster Manager is an optional component of the MySQL Cluster Carrier
Grade Edition, providing a command-line interface that automates common
management tasks, including the following online operations:
 - Configuring and starting MySQL Cluster
 - Upgrades
 - Addition of new nodes
 - Configuration changes
 - Backup and restore

MySQL Cluster Manager is a commercial extension to the MySQL family of 
products.

More details can be found at http://www.mysql.com/products/cluster/mcm/

A brief summary of changes in MySQL Cluster Manager version 1.3.3 is 
listed below:


Changes in MySQL Cluster Manager 1.3.3 (2014-12-01)

   This section documents all changes and bug fixes that have
   been applied in MySQL Cluster Manager 1.3.3 since the release
   of MySQL Cluster Manager version 1.3.0.

   Functionality Added or Changed

 * Agent: For a node on which an expected backup is not found,
   the output for the list backups command now reads None
   for BackupId and says No backups. (Bug #19208671)

 * A remove process command has been added, providing a means
   to perform an offline scale down for a cluster.
   See Section 4.6.6, The remove process Command, for details.

   Bugs Fixed

 * Agent: When a cluster was in single-user mode, any mcm command
   that causes a configuration change and a subsequent rolling
   restart (for example a set, add process, or a restart cluster)
   would stop the first data node in each nodegroup and would then
   be unable to restart it, due to a limitation with the MySQL
   Cluster. With this fix, mcm rejects those commands under the
   situation with an error message, instead of letting the data
   nodes be stopped. (Bug #20026523)

 * Agent: When MySQL Cluster Manager was trying to create a
   temporary directory (tmpdir) for a MySQL node under its
   directory for manager data (manager-dir), it did not
   always follow the specification for manager-dir for the
   node, which resulted in putting the temporary directory
   at the wrong location sometimes. (Bug #20026523)

 * Agent: When the --log-use-syslog option was set during
   the startup of mcmd, an error was thrown, complaining
   that the option log-file was also used (which is not
   allowed) even if --log-file was not really set. (Bug
   #19972864)

 * Agent: If a data node went from the running into the
   added state for some reasons, it became irrecoverable by
   MySQL Cluster Manager because, as a safeguard, MySQL
   Cluster Manager did not start a newly added data node
   automatically when the cluster was running. The safeguard
   is now removed, in order to allow the recovery of a data
   node in the described situation. (Bug #19787156)

 * Agent: During the recovery of an mcmd agent from a crash,
   if the cluster's management node could not be contacted
   for information, the agent just reported the statuses of
   the managed processes as they were last known, which
   might not reflect the processes' real statuses (for
   example, a process might have just crashed, and the agent
   would still said it is running), With this fix, the mcmd
   agent will report the statuses of the processes as
   unknown in the described situation. (Bug #19321446)

 * Agent: When bootstrapping a default cluster with the
   --bootstrap option, the ndbd process was used for data
   nodes. With this fix, the multi-threaded ndbmtd process
   is used instead, which is preferable from a performance
   perspective. (Bug #18068338)

 * Agent: An mcmd agent crashed when trying to stop a
   cluster that was hanging during an operation to restore
   itself. (Bug #17957393)

 * Agent: Configuration attribute values that start and end
   with double quotes could not be set using the set
   command. (Bug #13040122)

 * Client: When setting the LogDestination configuration
   attribute using the set command, mcm threw a syntax error
   when the attribute's value was single-quoted. (Bug
   #19435351)

 * Client: The error reporting for a data node crash by the
   MySQL Cluster Manager client did not include what had
   been reported by the ALERT statements before. With this
   fix, ALERT is included as a matching pattern for
   picking up errors from logs of the data nodes, which
   might result in more information on the crash being
   provided. (Bug #19426279)

 * Client: At an attempt to add to a site a host that
   already belonged to another site, the MySQL Cluster
   Manager client hung; and even after the client was
   

MySQL Connector/C++ 1.1.5 has been released

[karen langford]

Dear MySQL Users,

A new GA (general availability) version of MySQL Connector/C++ has
been made available: MySQL Connector/C++ 1.1.5 GA. The MySQL
Connector/C++ provides a C++ API for connecting client applications to
the MySQL Server 5.5 or newer.

You can download the production release at:

http://dev.mysql.com/downloads/connector/cpp/1.1.html

MySQL Connector C++ (Commercial) will be available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month's upload cycle.

The MySQL driver for C++ offers an easy to use API derived from JDBC
4.0. MySQL Workbench has used it successfully for years.

We have improved the driver since the last GA release. Please see the
documentation and the CHANGES file in the source distribution for a
detailed description of bugs that have been fixed. Bug descriptions are
also listed below.

Enjoy!

The MySQL build team at Oracle

==

Changes in MySQL Connector/C++ 1.1.5  (2014-11-26)

   Functionality Added or Changed

 * It was not possible to delete multiple connection
   attributes using the OPT_CONNECT_ATTR_DELETE option. This
   can now be done using the std::list sql::SQLString 
   type. (Bug #19939417)

 * MySQL_Prepared_Statement::getMoreResults() functionality
   has been implemented, so multiple result sets now can be
   fetched using a prepared statement. (Bug #19147677)

 * The following connection options have been implemented:
   MYSQL_DEFAULT_AUTH, MYSQL_OPT_CONNECT_ATTR_DELETE,
   MYSQL_OPT_CONNECT_ATTR_RESET, MYSQL_OPT_LOCAL_INFILE,
   MYSQL_PLUGIN_DIR, MYSQL_READ_DEFAULT_FILE,
   MYSQL_READ_DEFAULT_GROUP, MYSQL_SET_CHARSET_DIR, and
   max_statement_timeout for session-based query timeout.
   (Bug #73665, Bug #19479950)

 * These functions were added: Connection::isValid() checks
   whether the connection is alive, and
   Connection::reconnect() reconnects if the connection has
   gone down. (Bug #65640, Bug #14207722)

 * The Boost dependency was removed from the Connector/C++
   API headers. These headers were using the boost::variant
   type, making it impossible to use Connector/C++ binaries
   without having Boost installed.

   Bugs Fixed

 * For installation from MSI packages, variant.h and
   version_info.h were missing from the include/cppconn
   folder. (Bug #19973637)

 * For several valid client options, getClientOption() did
   not return a value. (Bug #19940314)

 * A memory leak occurred when adding the
   OPT_CONNECT_ATTR_ADD parameter to the options list.
   (Bug #19938970)

 * getClientOption() raised an assertion if the specified
   option was not set at connect time. (Bug #19938922)

 * Several metadata flaws were corrected:

  + getTables() did not return a correct result when
TableType=VIEW and metadataUseInfoSchema=false.

  + getColumns() did not return column inforomation when
metadataUseInfoSchema=TRUE.

  + getColumnName() returned the display name instead of
the actual column name.

  + getProcedures() returned a syntax error when
metadataUseInfoSchema=false.
   (Bug #19505348, Bug #19147897, Bug #19244736, Bug
   #19505421)

 * The LOCALHOST global variable was referenced at two
   places in C/C++ code, which could result in a double-free
   corruption error. (Bug #74616, Bug #19910311)

 * driver/version_info.h (containing version macros) was not
   included in the installed header files.
   (Bug #73795, Bug #19553971)

 * Several CMake issues were corrected:

  + CMake could misconfigure the link flags.

  + CMake did not pick up the libmysqlclient path from
the MYSQL_LIB_DIR option.

  + For test suite compilation, CMake did not pick up
libmysqlclient from the user-specified path, even if
MYSQL_LIB_DIR and DYNLOAD_MYSQL_LIB were given.
   (Bug #73427, Bug #19315635, Bug #19370844, Bug #19940663)

 * Connector/C++ issued a ping command every time isClosed()
   was called in a Connection, rather than just checking
   whether close() had been called earlier or when a fatal
   error occurred in an earlier operation.
   (Bug #69785, Bug #17186530)

 * With the result set type set to TYPE_FORWARD_ONLY,
   Statement::executeQuery() returns almost immediately, but
   MySQL_ResultSet::next() and
   MySQL_Prepared_ResultSet::next() returned false if the
   connection was lost rather than throwing an exception,
   making it impossible to distinguish loss of connection
   from normal end of the result set.
   MySQL_ResultSet::next() and
   MySQL_Prepared_ResultSet::next() now throw an exception
   when the connection is lost. (Bug #69031, Bug 

MySQL Connector/NET 6.9.5 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.5 is a maintenance release for the 6.9.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.9.5 (2014-11-12)

   Bugs Fixed

 * Generated code that matched against the start of a
   VARCHAR/CHAR column now correctly uses LIKE instead of
   location functions for the LINQ to Entity operators
   StartsWith, Contains, and EndsWith. Locate
   functions do not make use of indexes placed on the
   VARCHAR/CHAR columns, which caused significant
   performance degradation. (Bug #19783747, Bug #19680236,
   Bug #19944400, Bug #72058)

 * The web providers registration required the removal of
   the .v20 suffix from the type in the web providers
   section in machine.config. (Bug #19715398, Bug #74080)

 * Generated SQL was missing several clauses, such as
   OrderBy, GroupBy, and Skip), in cases that involved the
   let keyword, or in other scenarios that were translated
   into a DbApplyExpression. (Bug #19698010, Bug #19783760,
   Bug #19944549, Bug #73549)

 * LINQ to Entities queries failed for the cases that
   contained a predicate using IList.Contains with an
   argument of DbCastExpression, DbConstantExpression,
   DbParameterReferenceExpression. (Bug #19690370, Bug
   #19783755, Bug #19944528, Bug #73643)

 * A SELECT query that had a nullable DATETIME field in a
   child .Any() clause with an .OrderBy() would fail and
   emit a NotImplementedException exception. (Bug #19681723,
   Bug #19795751, Bug #70722)

 * The query optimization routine would return statements
   with invalid table aliases when nested queries were being
   optimized. This would throw an Unknown column
   exception. (Bug #19681348, Bug #19934324, Bug #72004)

 * A memory leak was fixed. (Bug #19467233, Bug #19474480,
   Bug #19474510, Bug #73122)

 * The CreateUser function did not trim whitespace before
   storing values into the database, while MembershipUser
   did return trimmed values. The trimming is now performed
   before the data is stored. (Bug #19459461, Bug #73411)

 * LINQ to Entities queries that used Views with the Take
   operator were not correctly generated. This problem
   affected EF Database First scenarios. (Bug #19356006,
   Bug #19789288, Bug #72148)


The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/6.9.5
https://www.nuget.org/packages/MySql.Data.Entity/6.9.5
https://www.nuget.org/packages/MySql.Fabric/6.9.5
https://www.nuget.org/packages/MySql.Web/6.9.5


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 6.6.7 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.6.7 is a maintenance release for the 6.6.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.6.7 (2014-11-11)

   This is the final release of the 6.6.x branch.

   Bugs Fixed

 * The fluent API DbModelBuilder.HasColumnType had no effect
   in Entity Framework 6. (Bug #19476922, Bug #19456229, Bug
   #19462808)

 * Creating a Model First or Database First model using
   MySQL 5.7 would set ProviderManifestToken to 5.6. (Bug
   #19475012)

 * Setting a Primary Key GUID identity in Code First in
   Entity Framework 6 did not function with MySQL server
   5.7. Inserting a row with a valid value for the GUID
   generated an error, even when it had a trigger set to the
   correct value.
   As a workaround, it was necessary to redeclare the column
   definition to accept a dummy default, such as default
   ''. (Bug #19456452, Bug #19462811, Bug #19476995)

 * Non Primary Keys declared as Identity GUID did not have
   their GUID's automatically generated. (Bug #19456415, Bug
   #19461919, Bug #19477029)

 * When using Entity Framework 4.3 Code first Identifiers
   for Migrations and Entity Framework 6, generated foreign key
(http://dev.mysql.com/doc/refman/5.6/en/glossary.html#glos_foreign_key)
   identifiers could be longer than 64
   characters, causing MySQLException errors. The fix
   renames any too-long identifiers using the name format
   FK_guid, where guid is a global unique identifier
   generated at runtime. (Bug #19211564, Bug #19483128)
   References: This bug is a regression of Bug #67285.

 * When trying to alter a stored procedure or trigger that
   included references to session variables, an error
   occurred and the changes were not saved, unless Allow
   User Variables=true was set in the connection settings.
   An error is no longer generated, and similar issues with
   renaming stored procedures or triggers using Alter
   Routine were also fixed. (Bug #19211432)

 * In Visual Studio, Connector/Net did not read the
   millisecond portion of a time value for a field of type
   TIME(3). (Bug #19211409, Bug #18111085)

 * The MySQL parser did not recognize the full string
   literal syntax of [_charset_name]'string' [COLLATE
   collation_name] as supported by the MySQL Server. This
   fix makes Connector/Net and MySQL for Visual Studio
   recognize the string literal syntax as specified in the
   Character String Literal Character Set and Collation
   (http://dev.mysql.com/doc/refman/5.6/en/charset-literal.html)
   section of the MySQL Server manual. (Bug #19211249,
   Bug #18169145)

 * When the connection limit was exceeded,
   MySqlConnection.Open() would leave the TCP connections in
   a CLOSE_WAIT state, but now closes them. (Bug #18665388,
   Bug #72025)

 * When a client refreshed a web page associated with an
   expired session and if the ASP.NET project was using
   SessionState ... regenerateExpiredSessionId=true ...,
   a duplicate entry exception was generated from the
   MySqlSessionProvider. (Bug #18657550, Bug #19783515, Bug
   #70409)

 * Entity Framework threw a NullReferenceException on
   insertion of a record into tables that had an
   auto-increment, unsigned, bigint primary key. (Bug
   #18189217, Bug #19211404, Bug #71242)

 * In Visual Studio, the stored procedure debugger did not
   evaluate the last_insert_id() function in a watch
   expression correctly. This fix also corrects similar
   issues for two other information functions that query the
   debug data table: row_count() and found_row(). (Bug
   #18111085)

 * When Connector/Net's SQL generator emitted code for the
   LINQ Union() or Concat() operator, parentheses were not
   applied around the individual SELECT statements. That
   could cause a change of meaning for the query when a
   Take() operator (thus a LIMIT clause in the SQL code) was
   applied to the last SELECT statement. With this fix,
   parentheses were put around individual SELECT statements,
   so that the LIMIT clause will not be applied to the
   entire result of the UNION operation. (Bug #18049691, Bug
   #19211182, Bug #19483110, Bug #70828)

 * The MySQL parser could not parse an if statement when
   there were any spaces before the parenthesis for the
   arguments (for example, if (1,1, 

MySQL Connector/NET 6.7.6 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/NET 6.7.6, a new version of the all-managed .NET driver
for MySQL has been released.  This is the GA, is feature complete. It is
recommended for production environments.  It is appropriate for use with
MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsand mirror sites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

The 6.7 version of MySQL Connector/NET brings the following new
features:
-  WinRT Connector.
-  Load Balancing support.
-  Entity Framework 5.0 support.
-  Memcached support for Innodb Memcached plugin.
-  This version also splits the product in two: from now on, starting
   version 6.7, Connector/NET will include only the former Connector/NET
   ADO.NET driver, Entity Framework and ASP.NET providers (Core
   libraries of MySql.Data, MySql.Data.Entity  MySql.Web). While all
   the former product Visual Studio integration (Design support,
   Intellisense, Debugger) are available as part of MySQL Windows
   Installer under the name MySQL for Visual Studio.

WinRT Connector
---
Now you can write MySql data access apps in Windows Runtime (aka Store
Apps) using the familiar API of Connector/NET for .NET.

Load Balancing Support
---
Now you can setup a Replication or Cluster configuration in the backend,
and Connector/NET will balance the load of queries among all servers
making up the backend topology.

Entity Framework 5.0
---
Connector/NET is now compatible with EF 5, including special features of
EF 5 like spatial types.

Memcached
---
Just setup Innodb memcached plugin and use Connector/NET new APIs to
establish a client to MySQL 5.6 server's memcached daemon.


Changes in MySQL Connector/Net 6.7.6 (2014-11-11)

   Bugs Fixed

 * Generated code that matched against the start of a
   VARCHAR/CHAR column now correctly uses LIKE instead of
   location functions for the LINQ to Entity operators
   StartsWith, Contains, and EndsWith. Locate
   functions do not make use of indexes placed on the
   VARCHAR/CHAR columns, which caused significant
   performance degradation. (Bug #19783747, Bug #19680236,
   Bug #72058)

 * Creating a Geometry Column with an SRID value would not
   save the value to the table. (Bug #19783444, Bug
   #19137999, Bug #19476721, Bug #71869)

 * Generated SQL was missing several clauses, such as
   OrderBy, GroupBy, and Skip), in cases that involved the
   let keyword, or in other scenarios that were translated
   into a DbApplyExpression. (Bug #19698010, Bug #19783760,
   Bug #73549)

 * LINQ to Entities queries failed for the cases that
   contained a predicate using IList.Contains with an
   argument of DbCastExpression, DbConstantExpression,
   DbParameterReferenceExpression. (Bug #19690370, Bug
   #19783755, Bug #73643)

 * A SELECT query that had a nullable DATETIME field in a
   child .Any() clause with an .OrderBy() would fail and
   emit a NotImplementedException exception. (Bug #19681723,
   Bug #19795751, Bug #70722)

 * The query optimization routine would return statements
   with invalid table aliases when nested queries were being
   optimized. This would throw an Unknown column
   exception. (Bug #19681348, Bug #72004)

 * The Feature will be installed when required option was
   removed from the features list in the Connector/Net
   installer due to it not supporting on-demand
   installations because of dependencies with the
   assemblies. (Bug #19670596, Bug #19681113)

 * The fluent API DbModelBuilder.HasColumnType had no effect
   in Entity Framework 6. (Bug #19476922, Bug #19456229, Bug
   #19462808)

 * Creating a Model First or Database First model using
   MySQL 5.7 would set ProviderManifestToken to 5.6. (Bug
   #19475012)

 * Setting a Primary Key GUID identity in Code First in
   Entity Framework 6 did not function with MySQL server
   5.7. Inserting a row with a valid value for the GUID
   generated an error, even when it had a trigger set to the
   correct value.
   As a workaround, it was necessary to redeclare the column
   definition to accept a dummy default, such as default
   ''. (Bug #19456452, Bug #19462811, Bug #19476995)

 * Non Primary Keys declared as Identity GUID did not have
   their GUID's automatically generated. (Bug #19456415, Bug
   #19461919, Bug #19477029)

 * LINQ to Entities queries that used Views with the Take
   operator were not correctly generated. This problem
   affected EF Database First scenarios. (Bug 

MySQL Enterprise Backup 3.11.1 has been released

[karen langford]

Dear MySQL users,

MySQL Enterprise Backup v3.11.1, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension to the MySQL family of products.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 3.11.1 is given below.

Changes in MySQL Enterprise Backup 3.11.1  (2014-11-05)

   Bugs Fixed

 * The copying of the relay log files from a MySQL slave
   server into a backup (which has been the default behavior
   of MySQL Enterprise Backup since 3.11.0) crashed MySQL
   Enterprise Backup when the server is of version 5.5. (Bug
   #19904912)

 * The copying of the binary log files from the server into
   a backup (which has been the default behavior of MySQL
   Enterprise Backup since 3.11.0) caused some databases to
   be silently skipped over during the backup process when
   (1) the binary log files are located in the server's data
   directory, and the name of any database matches the data
   directory's base name or (2) the binary log files are
   located in a subdirectory of the data directory. (Bug
   #19883801)


You can also find more information on the contents of this release in 
the change log:

http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/meb-news.html

The complete manual for MEB 3.11.1 is at,
http://dev.mysql.com/doc/mysql-enterprise-backup/3.11/en/index.html

The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).

You can also download the binaries from MOS, https://support.oracle.com
Choose the Patches  Updates tab, and then use the Product or Family
(Advanced Search) feature. If you haven't looked at MEB recently,
please do so now and let us know how MEB works for you.

Your feedback is greatly appreciated!

Please report any problems you have at https://bug.oraclecorp.com/
for the product MySQL Enterprise Backup

Thanks,
The MySQL build team at Oracle


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL for Excel 1.3.3 has been released

[karen langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.3. This is a maintenance release for 1.3.x.
It can be used for production environments.

MySQL for Excel is an application plug-in enabling data analysts to very
easily access and manipulate MySQL data within Microsoft Excel. It
enables you to directly work with a MySQL database from within Microsoft
Excel so you can easily do tasks such as:

  * Importing MySQL Data into Excel

  * Exporting Excel data directly into MySQL to a new or existing table

  * Editing MySQL data directly within Excel


MySQL for Excel is installed using the MySQL Installer for Windows.

The MySQL Installer comes in 2 versions

- Full (150 MB) which includes a complete set of MySQL products with
  their binaries included in the download.

- Web (1.5 MB - a network install) which will just pull the MySQL for
  Excel over the web and install it when run.

You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/

The MySQL for Excel product can also be downloaded by using the product
standalone installer found at this link
http://dev.mysql.com/downloads/windows/excel/

Changes in MySQL for Excel 1.3.3 (2014-10-27)

This section documents all changes and bug fixes applied to MySQL
for Excel since the release of 1.3.2. Several new features were
added the 1.3.x branch, for more information see What Is New In
MySQL for Excel 1.3
(http://dev.mysql.com/doc/mysql-for-excel/en/mysql-for-excel-what-is-new-1-3.html).

Known limitation:

Upgrading from versions MySQL for Excel 1.3.2 and lower is not
possible due to a bug fixed in MySQL for Excel 1.3.3. In that
scenario, the old version (MySQL for Excel 1.3.2 or lower) must be
uninstalled first. Upgrading from version 1.3.3 works correctly.

Bugs Fixed

  * The MySQL for Excel MSI was not replacing the registry keys on
an upgrade, in that registry keys from previous versions
remained and were not upgraded. (Bug #19783949, Bug #74286)

  * Using semicolons (';') in values like schema names, column
names or text values caused SQL queries sent to the MySQL
server to fail. Internally, MySQL for Excel treated the
semicolon as a separator for SQL statements. (Bug #19680607,
Bug #74057)

  * Committing 20+ cell changes and new rows at the same time
would fail to commit. (Bug #19639669, Bug #73911)

  * The Preview SQL statements before they are sent to the
server option is now overridden when the Auto-Commit
checkbox in the Edit Data dialog is checked. Before, each edit
(that was auto committed) would first show the preview dialog.
(Bug #19607260, Bug #73900)

  * The Export Data dialog's preview grid would display time data
as a standard decimal numbers.
Also, exported data with time values were not properly wrapped
in single quotes. (Bug #19607195, Bug #73899)

  * Importing a table with a row count that exceeded the number of
rows below the cursor would generate a fatal High severity
error and fail to import the data. Now, the import succeeds
but the Import will be truncated since it exceeds the
available worksheet space. (Bug #19588933, Bug #73866)

  * When selecting a non-primary column that only contains integer
values, the Create Index option is automatically checked,
and the Allow Empty option is unchecked. This is the
expected behavior with the advanced Automatically check the
Allow Empty checkbox for columns without an index option
enabled. (Bug #19503820, Bug #73719)

  * For consistency, all references to Varchar were changed to
VarChar. (Bug #19501346, Bug #73712)

  * The Allow Empty checkbox only had an effect the first time the
SQL query was previewed. (Bug #19467535, Bug #73646)

  * Changed the way NULL and zero dates are handled. Previously,
MySQL zero dates (-00-00 00:00:00) were imported into
Excel as the minimum valid date allowed by .NET
(DateTime.MinValue), which was then converted into a text
representation where the cell's value was no longer recognized
as a date. Now, zero dates are always treated as NULL. (Bug
#19423952, Bug #73541)

  * Exporting data that used a comma as the decimal separator
would fail to export. The commas are now converted to periods,
as already done when appending data. (Bug #19403063, Bug
#73293)

  * When the number of mapped columns was less than the number of
columns in the target table, and when the last MySQL column
contained NULL values, append operations would insert NULL
values for all fields in the aforementioned last column
instead of inserting the values defined in Excel. (Bug

MySQL Connector/NET 6.9.4 has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.4 is a maintenance release for the 6.9.x
series of the .NET driver for MySQL. It can be used for production
environments.

It is appropriate for use with MySQL server versions 5.5-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.9.4 (2014-09-26)

   Functionality Added or Changed

 * MySQL Fabric is now supported.

The documentation is available at:
http://dev.mysql.com/doc/connector-net/en/

Nuget packages are available at:
https://www.nuget.org/packages/MySql.Data/6.9.4
https://www.nuget.org/packages/MySql.Data.Entity/6.9.4
https://www.nuget.org/packages/MySql.Web/6.9.4
https://www.nuget.org/packages/MySql.Fabric/6.9.4


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Notifier 1.1.6 has been released

[karen langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL Notifier version 1.1.6, the latest addition to the MySQL
Installer for Windows.

MySQL Notifier enables developers and DBAs to easily monitor, start and
stop all their MySQL database instances. It provides a familiar
Microsoft SQL Server look and feel and integrates with MySQL Workbench.

MySQL Notifier is installed using the MySQL Installer for Windows.

The MySQL installer comes in 2 versions

- Full (150 MB) which includes a complete set of mysql products with
  their binaries included in the download

or

- Web (1.5 MB - a network install) which will just pull the MySQL
  Notifier over the web and install it when run.


You can download MySQL Installer from our official Downloads page at
http://dev.mysql.com/downloads/installer/.

Changes in MySQL Notifier 1.1.6 (2014-09-22)

   Bugs Fixed

 * A High Severity Error was thrown when restarting Notifier if
   MySQL services/products had been removed while Notifier was
   not running. (Bug #19439604, Bug #73576)

 * A High Severity Error was thrown when a my.ini file for a
   monitored MySQL instance was deleted. (Bug #19422802, Bug
   #73539)

 * Available updates detected by MySQL Installer were not being
   communicated back to MySQL Notifier. Now, the Notifier
   correctly displays notifications for available updates. (Bug
   #19219905)

 * MySQL Notifier would fail to start when a monitored service
   name contained the string MySQL since it was being treated
   as a MySQL server service. Now, the detection of MySQL
   services has been fixed to select real MySQL server services.
   (Bug #19078684, Bug #73135)

 * Removing MySQL Workbench's connections from within Workbench,
   or by deleting the MySQL Workbench connections.xml file, now
   removes those MySQL connections from the SQL editor sub menus
   of corresponding monitored services in MySQL Notifier. (Bug
   #18163378)

 * Selecting Actions, Check for updates, and then No, would throw
   a High Severity Error. (Bug #17858917)

 * MySQL Notifier now handles Fabric, Fabric managed, and unknown
   connections, in the instances dialog. Fabric connections are
   not shown, Fabric Managed connections are shown in the
   Manage Instances dialog with Type = Fabric Managed. MySQL
   Connections that do not use a native, SSH, socket, or Fabric
   driver are treated as unknown and not shown.

You can access the MySQL Notifier documentation at
http://dev.mysql.com/doc/refman/5.6/en/windows-notifier.html.

You can find our team's blog at http://blogs.oracle.com/MySQLOnWindows.

You can also post questions on our MySQL Notifier forum found at
http://forums.mysql.com/.

Enjoy and thanks for the support!


MySQL Notifier Team.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Workbench 6.2.2 RC has been released

[karen langford]

Dear MySQL Users,

The MySQL developer tools team announces 6.2.2 RC - the final release
candidate for MySQL Workbench 6.2.

MySQL Workbench 6.2 is the upcoming major update for the official MySQL
graphical development tool .

MySQL Workbench 6.2 focuses on support for innovations released in MySQL
5.6 and MySQL 5.7 DMR (Development Release) as well as MySQL Fabric 1.5,
with features such as:

* A new spatial data viewer, allowing graphical views of result sets
containing GEOMETRY data and taking advantage of the new GIS
capabilities in MySQL 5.7.
* Support for new MySQL 5.7.4 SQL syntax and configuration options.
* Metadata Locks View shows the locks connections are blocked or waiting
on.
* MySQL Fabric cluster connectivity - Browsing, view status, and connect
to any MySQL instance in a Fabric Cluster.
* MS Access migration Wizard - easily move to MySQL Databases.


Other significant usability improvements were made, aiming to raise
productivity for advanced and new users:

* Direct shortcut buttons to commonly used features in the schema tree.
* Improved results handling. Columns have better auto-sizing and their
widths are saved. Fonts can also be customized. Results pinned to
persist viewing data.
* A convenient Run SQL Script command to directly execute SQL scripts,
without loading them first.
* Database Modeling has been updated to allow changes to the formatting
of note objects and attached SQL scripts can now be included in forward
engineering and synchronization scripts.
* Integrated Visual Explain within the result set panel.  Visual Explain
* drill down for large to very large explain plans.  Shared SQL snippets
* in the SQL Editor, allowing multiple users to
share SQL code by storing it within a MySQL instance.
* And much more.

The list of provided binaries was updated and MySQL Workbench binaries
now available for:
* Windows 7 32 and 64bits
* Mac OS X Lion or newer
* Ubuntu 12.04 LTS and Ubuntu 14.04 64bits
* Fedora 20 64bits
* Oracle Linux 6.5 64bits
* Oracle Linux 7 64bits
* Sources for building in other Linux distributions. Pre-compiled binaries
   are no longer provided for 32bit Linux distributions, although users may
   still download and build from sources.

For the full list of changes in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-2.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?151

Download MySQL Workbench 6.2.2 now, for Windows, Mac OS X 10.7+, Oracle
Linux 6 and 7, Fedora 20, Ubuntu 12.04 and Ubuntu 14.04 or sources,
from:

http://dev.mysql.com/downloads/tools/workbench/

Enjoy!

Changes in MySQL Workbench 6.2.2 (2014-09-05, RC)

   Functionality Added or Changed

 * The following SSL related changes were introduced:

  + The Use SSL option for SSL connection options was changed
to a dropdown, where you can select one of: No, If
Available, or Required.

  + If Required is selected, the connection will fail if a
SSL connection cannot be enabled.

  + New MySQL connections default to If available.

  + The Test Connection button now shows whether SSL was
enabled when the connection was opened.

  + The Session Information panel in the SQL Editor sidebar
shows is SSL is enabled, and also the Cipher in use.
   (Bug #18547269)

 * Indentation is now respected in the SQL and code editors, when
   before the current indention level would be forgotten. New lines
   now start at the previous indention level. (Bug #17354356, Bug
   #14666286, Bug #70138, Bug #66941)

 * The tab key now inserts a tab character into the query editor,
   when before it inserted three spaces. (Bug #14499535, Bug #66382)

   Bugs Fixed

 * The document tab controls now block mouse movements when the
   button is down, as to prevent accidental window dragging. (Bug
   #19484086, Bug #72256)

 * Selecting a color from color picker on a table would generate
   an invalid color value. (Bug #19487822, Bug #73682)

 * On Windows, the catalog treeview now has tooltips to show
   object names of any length. On Linux, this information is
   available from a new column. (Bug #19487798, Bug #73681)

 * The Commit results edits and Discard results Edits options
   would sometimes be hidden from view. (Bug #19484760, Bug #71539)

 * The server management functionality would sometimes fail with
   connections using SSH tunneling. (Bug #19447288, Bug #73580)

 * If a transaction was already open with auto-commit disabled,
   there was a dialog that prompted to commit the open transaction
   before applying the changes. That dialog was simplified to only
   offer Apply and Cancel options. This dialog still has no effect
   on the transaction for applying the result set itself.  Also, the
   result set changes will no longer be committed if a 

MySQL for Visual Studio 1.2.3 GA has been released

[karen langford]

Dear MySQL users,

MySQL for Visual Studio is a product that includes all of the Visual
Studio integration functionality to create and manage MySQL databases
when developing .NET applications. The 1.2.3 version is a General
Availability release of this product which is feature complete and is
suitable for production environments.

This version is appropriate for using with MySQL server versions 5.5-5.6.
The 5.7 server version is also compatible but is not fully supported,
thus it should be used at your own discretion.

As this is a GA version of the MySQL for Visual Studio product, it can
be downloaded by using the product standalone installer at this link
http://dev.mysql.com/downloads/windows/visualstudio/ or with the MySQL
Windows Installer.

What's new in the 1.2.3 GA version
--
- A new option for the MySQLSimpleMembership provider in the web
  configuration tool. (This feature requires Connector/Net 6.9
  installed).

What's new in the 1.2 version
-
- A new MySQL Project Wizard for creating Windows Forms applications.
- A new MySQL Project Wizard for creating ASP.NET MVC web applications.
- A new option in web configuration tool for the ASP.NET Personalization
  Provider (this feature requires Connector/Net 6.9).
- A new option in web configuration tool for the ASP.NET Site Map
  Provider (this feature requires Connector/Net 6.9).
- A new option for the MySQLSimpleMembership provider in the web
  configuration tool. (This feature requires Connector/Net 6.9
  installed).



MySQL Project Wizard for Windows Forms
--
The Windows Forms Project Wizard is available at the Visual Studio New
Project dialog, either at the MySQL category or by filtering by name.
It also can be accessed by using the MySQL Toolbar inside Visual Studio.
This wizard automates the generation of a .NET Windows Forms Application
that is connected to a MySQL data source. A Typed DataSet or an Entity
Framework Model can also be generated to link the Application to the MySQL
Database.  The user can select one or more tables that exists in the
database. Each table can have a different type of view. The types of views
that are available in this version are:

Single Layout: A form that contains one control by each existing column
in the table with navigation controls and that allows CRUD operations.
All controls can include data typed validations for Numeric types and
Datetime types.  Grid layout: A form with a Grid that contains
navigation controls.  Master-Detail: A form with a single controls
layout for the Parent table and a grid to navigate in the child table.
Supported with C# or Visual Basic language.
This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x

For more details on the features included check the documentation at :
http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio-windows-forms.html 




MySQL Project Wizard for ASP.NET MVC

The ASP.NET MVC Project Wizard is available at the Visual Studio New
Project dialog, either at the MySQL category or by filtering by name. It
also can be accessed by using the MySQL Toolbar inside Visual Studio.

This wizard automates the generation of an ASP.NET MVC. The MVC versions
supported for this wizard are 3 when using Visual Studio 2010 or 2012,
and 4 when using Visual Studio 2013. The Web Application includes the
MySQL Membership configuration to manage ASP.NET authentication. The
login and create user views are generated by the wizard and it also
includes the generation of multiple browsable views for each one of the
tables selected for the application generation.

The generation of the MVC items is done by creating an Entity Framework
data model either with Entity Framework version 5 or 6 depending on the
user's selection.  Supported with C# or Visual Basic language.
This feature requires Connector/Net 6.7.5, 6.8.3 or 6.9.x

For more details on the features included check the documentation at :
http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio-mvc-project-wizard.html 




New option in web configuration tool for the ASP.NET Personalization 
Provider
- 


Personalization provider allows to store personalization state-state
data regarding the content and layout of Web Parts pages-generated by
the Web Parts personalization service using MySQL as a data source. This
feature requires Connector/Net 6.9.x
http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html


New option in web configuration tool for the ASP.NET Site Map Provider
--
Site Map provider allows to show a hierarchical list of links that
describe the structure of a site. This feature requires Connector/Net
6.9.x
http://dev.mysql.com/doc/connector-net/en/connector-net-website-config.html


New option 

MySQL Community Server 5.6.20 has been released

[karen langford]

Dear MySQL users,

MySQL Server 5.6.20, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.6.20 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.6, please see

http://dev.mysql.com/doc/refman/5.6/en/mysql-nutshell.html

Starting with 5.6.11, Microsoft Windows packages for MySQL 5.6
are available both as a full installer and as a web installer.
The full installer is significantly larger and comes bundled with
the latest software releases available. This bundle makes it easy
to download and configure a full server and development suite.

The web installer doesn't come bundled with any actual products
and instead relies on download-on-demand to fetch only the
products you choose to install. This makes the initial download
much smaller but increases install time as the individual products
will need to be downloaded.

For information on installing MySQL 5.6.20 on new servers or upgrading
to MySQL 5.6.20 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.6/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

https://wikis.oracle.com/display/mysql/Contributing

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.6. It may also be viewed
online at

http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-20.html

Enjoy!

Changes in MySQL 5.6.20 (2014-07-31)

   Security Notes

 * Security Fix: The linked OpenSSL library for the MySQL 5.6
   Commercial Server has been updated from version 1.0.1g to
   version 1.0.1h. Versions of OpenSSL prior to and including
   1.0.1g are reported to be vulnerable to CVE-2014-0224
   (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224).
   This change does not affect the Oracle-produced MySQL
   Community build of MySQL Server 5.6, which uses the yaSSL
   library instead. (CVE-2014-0224)

   InnoDB Notes

 * Important Change: Redo log writes for large, externally stored
   BLOB fields could overwrite the most recent checkpoint. The
   5.6.20 patch limits the size of redo log BLOB writes to 10% of
   the redo log file size. The 5.7.5 patch addresses the bug
   without imposing a limitation. For MySQL 5.5, the bug remains
   a known limitation.
   As a result of the redo log BLOB write limit introduced for
   MySQL 5.6, innodb_log_file_size should be set to a value
   greater than 10 times the largest BLOB data size found in the
   rows of your tables plus the length of other variable length
   fields (VARCHAR, VARBINARY, and TEXT type fields). Failing to
   do so could result in Row size too large errors. No action
   is required if your innodb_log_file_size setting is already
   sufficiently large or your tables contain no BLOB data. (Bug
   #16963396, Bug #19030353, Bug #69477)

   Functionality Added or Changed

 * Replication: The new system variable binlog_impossible_mode
   controls what happens if the server cannot write to the binary
   log, for example, due to a file error. For backward
   compatibility, the default for binlog_impossible_mode is
   IGNORE_ERROR, meaning the server logs the error, halts
   logging, and continues updates to the database. Setting this
   variable to ABORT_SERVER makes the server halt logging and
   shut down the server if it can not write to the binary log.
   (Bug #51014, Bug #11758766)

 * CMake support was updated to handle CMake version 3. (Bug
   #19001781)

 * New Debian7, Ubuntu12.04, and Ubuntu14.04 distribution support
   that was introduced with 5.6.17 now comes with the
   platform-specific packaging source placed under the packaging
   directory, in the deb-precise, deb-wheezy, and deb-trusty
   directories. (Bug #19020385)

 * Support for LinuxThreads has been removed from the source
   code. LinuxThreads was superseded by NPTL in Linux 2.6. (Bug
   #17007529, Bug #72888, Bug #18913935)

 * By default, mysql_install_db creates a my.cnf file in the
   installation base directory using a template. This may be
   undesireable for some deployments. To enable this behavior to
   be suppressed, mysql_install_db now supports a --keep-my-cnf
   option to preserve any existing my.cnf file and not create a
   new my.cnf file. (Bug #71600, Bug #18205019)

 * The mysqlhotcopy utility is now deprecated and will be removed
   in a future version of MySQL. Among the reasons for 

MySQL Enterprise Backup 3.10.2 has been released

[karen langford]

Dear MySQL users,

MySQL Enterprise Backup 3.10.2, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) 
website
as our latest GA release. This release will be available on eDelivery 
(OSDC)

after the next upload cycle. MySQL Enterprise Backup is a commercial
extension.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 3.10.2 is given below.

Changes in MySQL Enterprise Backup 3.10.2 (2014-07-01)

 Security Note

 * Security Fix: The linked OpenSSL library for MySQL Enterprise
   Backup 3.10 has been updated from version 1.0.1g to version
   1.0.1h. Versions of OpenSSL prior to and including 1.0.1g are
   reported to be vulnerable to CVE-2014-0224
   (http://www.cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2014-0224).
   (CVE-2014-0224)

   Functionality Added or Changed

 * MySQL Enterprise Backup now supports creation and restoration
   of single-file backups using a cloud storage. See Section
   5.1.15, Cloud Storage Options for details.

   Bugs Fixed

 * After a table backed up using the transportable tablespace
   option (--use-tts) was restored to a server, queries on the
   table did not make use of its indexes. That was because the
   cardinalities of the indexes were not properly updated after
   the table's restoration. This fix adds an ANALYZE TABLE
   (http://dev.mysql.com/doc/refman/5.6/en/analyze-table.html)
   step towards the end of the restoration process for tables
   backed up with the --use-tts option, in order to update the
   indexes' cardinalities. (Bug #18682317)

 * When cloning a slave for a GTID-enabled server using MySQL
   Enterprise Backup, the backup_gtid_executed.sql script created
   and stored in the backup directory was not copied onto the
   slave by the copy-back-and-apply-log operation. This fix has
   the script copied into the data directory of the slave. (Bug
   #18674861)

 * The maximum number of memory buffers that could be created for
   a mysqlbackup operation was hard-coded to be 100, making it
   impossible to set the number of buffers to a larger value
   using the number-of-buffers option. This fix removes the
   hard-coded maximum number for buffers. (Bug #18560870)

 * mysqlbackup threw an error if a table was dropped when the
   backup process was running. With this fix, the dropped table
   is ignored (as it does not need to be restored) and
   mysqlbackup finishes without throwing an error. (Bug
   #18358912, Bug #71865)

 * A segmentation fault occurred when a backup image created from
   a backup directory was restored using the
   copy-back-and-apply-log subcommand. It was because
   copy-back-and-apply-log was not able to extract backup-my.cnf
   from the image and get the value for innodb_data_file_path.
   (Bug #18242586)

 * After an apply-log operation was performed on a compressed
   backup (with the --uncompress and --apply-log options), when a
   copy-back-and-apply-log was applied on the backup, the
   restored data was inconsistent. That was because the first
   operation did not delete the compressed, .ibz backup file and
   did not mark the data as uncompressed at the end of the
   operation. The subsequent copy-back-and-apply-log operation
   than acted on the still existing, raw, compressed file, but
   thought that an apply-log operation had already been performed
   on it. This fix makes mysqlbackup delete the compressed, raw
   backup file once decompression and apply-log are finished and
   properly mark the backup as uncompressed and up-to-date. (Bug
   #18005786, Bug #18005732)

 * After an incremental backup was applied to a full backup, a
   second incremental would fail if the same incremental backup
   directory was used and if the
   --incremental-base=dir:directory_path option was pointing to
   the full backup's directory. This was because MySQL Enterprise
   Backup checked the end LSN in the full backup directory
   against the end LSN in the MySQL history table (which might
   not have been updated yet) and failed the process when there
   was a mismatch. This fix removes that check, so user in the
   described situation can proceed with creating more incremental
   backups. (Bug #16249018)

You can also find more information on the contents of this release in 
the change log:

http://dev.mysql.com/doc/mysql-enterprise-backup/3.10/en/meb-news.html

The complete manual for MEB 3.10.2 is at,
http://dev.mysql.com/doc/mysql-enterprise-backup/3.10/en/index.html

The tool is available for download from Oracle Software Delivery
Cloud (http://edelivery.oracle.com/).

You can also download the binaries from MOS, https://support.oracle.com
Choose the Patches  Updates tab, and then use the 

MySQL for Excel 1.3.0 Beta has been released

[karen langford]

Dear MySQL users,

The MySQL Windows Experience Team is proud to announce the release of
MySQL for Excel version 1.3.0.  This is a beta release for 1.3.x.

MySQL for Excel is an application plug-in enabling data analysts to very
easily access and manipulate MySQL data within Microsoft Excel. It
enables you to directly work with a MySQL database from within Microsoft
Excel so you can easily do tasks such as:

 * Importing MySQL Data into Excel

 * Exporting Excel data directly into MySQL to a new or existing table

 * Editing MySQL data directly within Excel


As this is a beta version the MySQL for Excel product can be
downloaded only by using the product standalone installer at this link
http://dev.mysql.com/downloads/windows/excel/


Changes in MySQL for Excel 1.3.0 (2014-06-06, Beta)

   This section documents all changes and bug fixes applied to MySQL
   for Excel since the release of 1.2.1. Several new features were
   added, for more information see What Is New In MySQL for Excel
(http://dev.mysql.com/doc/refman/5.6/en/mysql-for-excel-what-is-new.html).

   Known limitations:

   Upgrading from versions MySQL for Excel 1.2.0 and lower is not
   possible due to a bug fixed in MySQL for Excel 1.2.1. In that
   scenario, the old version (MySQL for Excel 1.2.0 or lower) must be
   uninstalled first. Upgrading from version 1.2.1 works correctly.

   Control + A cannot be used to select all database objects. Either
   shift + Arrow or Control + click must be used instead.

   Excel tables created from external data sources may not refresh if
   the MySQL for Excel add-in is loaded.

   PivotTables are normally placed to the right (skipping one column)
   of the imported data, they will not be created if there is another
   existing Excel object at that position.

   Functionality Added or Changed

 * Imported data can now be refreshed by using the native Refresh
   feature. Fields in the imported data sheet are then updated
   against the live MySQL database using the saved connection ID.

 * Functionality was added to import data directly into
   PivotTables, which can be created from any Import operation.

 * Multiple objects (tables and views) can now be imported into
   Excel, when before only one object could be selected.
   Relational information is also utilized when importing
   multiple objects.

 * All options now have descriptive tooltips. Hovering over an
   option/preference displays helpful information about its use.

 * A new Export Data, Advanced Options option was added that
   shows all available data types in the Data Type combo box,
   instead of only showing a subset of the most popular data
   types.

 * The option dialogs now include a Refresh To Defaults button
   that resets the dialog's options to their defaults values.
   Each option dialog is set individually.

 * A new Add Summary Fields for Numeric Columns option was added
   to the Import Data dialog that automatically adds summary
   fields for numeric data after the last row of the imported
   data. The specific summary function is selectable from many
   options, such as Total and Average.

 * A new collation option was added for the schema and table
   creation wizards. The default schema collation is Server
   Default, and the default table collation is Schema Default.
   Collation options may be selected from a drop-down list of all
   available collations.

Quick links:
You can access the MySQL for Excel documentation at 
http://dev.mysql.com/doc/en/mysql-for-excel.html.

You can find our team's blog at http://blogs.oracle.com/MySQLOnWindows.
You can also post questions on our MySQL for Excel forum found at 
http://forums.mysql.com/list.php?172.
You can follow our videos on our YouTube channel found at 
http://www.youtube.com/user/MySQLChannel.



Enjoy and thanks for the support!

The MySQL on Windows team at Oracle.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 6.9.1 Beta has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.1 a new version of the all-managed .NET driver
for MySQL has been released. This is a beta release for 6.9.x and is
not recommended for production environments.

It is appropriate for use with MySQL server versions 5.5-5.7.


It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsandmirrorsites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

Changes in MySQL Connector/Net 6.9.1 (2014-05-29, Beta)

   Functionality Added or Changed

 * Asynchronous methods are now supported.

   Bugs Fixed

 * When a client refreshed a web page associated with an expired
   session and if the ASP.NET project was using SessionState ...
   regenerateExpiredSessionId=true ..., a duplicate entry
   exception was generated from the MySqlSessionProvider. (Bug
   #18657550, Bug #70409)


The documentation is available at:
http://dev.mysql.com/doc/refman/5.7/en/connector-net.html


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 6.9.0 alpha has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Net 6.9.0 a new version of the all-managed .NET driver
for MySQL has been released. This is an alpha release for 6.9.x and is
not recommended for production environments.

It is appropriate for use with MySQL server versions 5.0-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloads  and mirror sites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)


The 6.9 version of MySQL Connector/NET brings the following new
features:

 * Added a MySQL Personalization Provider.

 * Added a SiteMap Web Provider.

 * Added a Simple Membership Web Provider.


The documentation is available at:
http://dev.mysql.com/doc/refman/5.7/en/connector-net.html


Enjoy and thanks for the support!

On behalf of the MySQL Connector/NET and the MySQL/ORACLE RE Team.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL for Visual Studio 1.2.0 alpha has been released

[karen langford]

Dear MySQL users,

MySQL for Visual Studio is a product including all of the Visual Studio
integration previously available as part of Connector/Net. The 1.2.0
version is an alpha release of this product that intends to introduce
users to the new features in this version.

This release is not feature complete and there are significant
limitations but it should be stable enough for users to understand the
new features and how we expect them to work.  As is the case with all
non-GA releases, it should not be used in any production environment.
It is appropriate for use with MySQL server versions 5.0-5.6.

As this is an alpha version the MySQL for Visual Studio product can be
downloaded only by using the product standalone installer at this link
http://dev.mysql.com/downloads/windows/visualstudio/

The 1.2.0 version introduces the following new features:

- A new MySQL Project Wizard for Windows Forms.
- A new MySQL Project Wizard for ASP.NET MVC 3.
- A new option in web configuration tool for the ASP.NET Personalization
  Provider (this feature requires Connector/Net 6.9).
- A new option in web configuration tool for the ASP.NET Site Map
  Provider (this feature requires Connector/Net 6.9).


MySQL Project Wizard for Windows Forms
--
The Windows Forms Project Wizard is available at the Visual Studio New
Project dialog, either at the MySql category or by filtering by name.
This wizard automates the generation of a simple .NET Windows Forms
Application with a form that is connected to a MySql data source.

MySQL Project Wizard for ASP.NET MVC 3
--
The ASP.NET MVC Project Wizard is available at the Visual Studio New
Project dialog, either at the MySql category or by filtering by name.
This wizard automates the generation of an ASP.NET application that
includes the MySQL Membership configuration and set up to a new or
existing MySQL database. Optionally the application can also use the
MySQL Role and MySQL Profile providers.


New option in web configuration tool for the ASP.NET Personalization 
Provider
- 


Personalization provider allows to store personalization state-state
data regarding the content and layout of Web Parts pages-generated by
the Web Parts personalization service using MySQL as a data source. This
feature requires Connector/Net 6.9.

New option in web configuration tool for the ASP.NET Site Map Provider
--
Site Map provider allows to show a hierarchical list of links that
describe the structure of a site. This feature requires Connector/Net 6.9.


For discussion, join the MySQL for Visual Studio forums:
http://forums.mysql.com/list.php?174

Download MySQL for Visual Studio 1.2.0 alpha from:
http://dev.mysql.com/downloads/windows/visualstudio/


Quick links

- MySQL for Visual Studio documentation
http://dev.mysql.com/doc/connector-net/en/connector-net-visual-studio.html
- Bugs: http://bugs.mysql.com
- Forums: http://forums.mysql.com/index.php?174
- Blog: http://blogs.oracle.com/MySqlOnWindows/



Enjoy and thanks for the support!

MySQL for Visual Studio Team.

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Connector/NET 6.7.5 has been released

[karen langford]

MySQL Connector/NET 6.7.5, a new version of the all-managed .NET driver
for MySQL has been released.  This is the GA, is feature complete. It is
recommended for production environments.  It is appropriate for use with
MySQL server versions 5.0-5.7.

It is now available in source and binary form from
http://dev.mysql.com/downloads/connector/net/#downloadsand mirror sites
(note that not all mirror sites may be up to date at this point-if you
can't find this version on some mirror, please try again later or choose
another download site.)

The 6.7 version of MySQL Connector/NET brings the following new
features:
-  WinRT Connector.
-  Load Balancing support.
-  Entity Framework 5.0 support.
-  Memcached support for Innodb Memcached plugin.
-  This version also splits the product in two: from now on, starting
   version 6.7, Connector/NET will include only the former Connector/NET
   ADO.NET driver, Entity Framework and ASP.NET providers (Core
   libraries of MySql.Data, MySql.Data.Entity  MySql.Web). While all
   the former product Visual Studio integration (Design support,
   Intellisense, Debugger) are available as part of MySQL Windows
   Installer under the name MySQL for Visual Studio.

WinRT Connector
---
Now you can write MySql data access apps in Windows Runtime (aka Store
Apps) using the familiar API of Connector/NET for .NET.

Load Balancing Support
---
Now you can setup a Replication or Cluster configuration in the backend,
and Connector/NET will balance the load of queries among all servers
making up the backend topology.

Entity Framework 5.0
---
Connector/NET is now compatible with EF 5, including special features of
EF 5 like spatial types.

Memcached
---
Just setup Innodb memcached plugin and use Connector/NET new APIs to
establish a client to MySQL 5.6 server's memcached daemon.

Changes in MySQL Connector/Net 6.7.5 (2014-04-04)

   Bugs Fixed

 * Entity Framework threw a NullReferenceException on insertion
   of a record into tables that had an auto-increment, unsigned,
   bigint primary key. (Bug #18189217, Bug #71242)

 * MaximumPoolSize and MinimumPoolSize were not recognized as
   valid connection string options. (Bug #18182246)

 * The MySQL parser did not recognize the full string literal
   syntax of [_charset_name]'string' [COLLATE collation_name] as
   supported by the MySQL Server. This fix makes Connector/Net
   and MySQL for Visual Studio recognize the string literal
   syntax as specified in the Character String Literal Character
   Set and Collation
(http://dev.mysql.com/doc/refman/5.6/en/charset-literal.html)
   section of the MySQL Server manual. (Bug #18169145)

 * In Visual Studio, Connector/Net did not read the millisecond
   portion of a time value for a field of type TIME(3). (Bug
   #18111085)

 * When Connector/Net's SQL generator emitted code for the LINQ
   Union() or Concat() operator, parentheses were not applied
   around the individual SELECT statements. That could cause a
   change of meaning for the query when a Take() operator (thus a
   LIMIT clause in the SQL code) was applied to the last SELECT
   statement. With this fix, parentheses were put around
   individual SELECT statements, so that the LIMIT clause will
   not be applied to the entire result of the UNION operation.
   (Bug #18049691, Bug #70828)

 * During migrations with ASP.NET Identity 1.0 in Visual Studio,
   the code generator did not generate the indexes and foreign
   keys in the Up() class. (Bug #18049272, Bug #71287)

 * Connector/Net did not add the AUTO_INCREMENT property to a
   primary key column of type BIGINT when creating a model in
   Entity Framework. (Bug #17924407, Bug #17937401, Bug #70602)

 * Millisecond values written to a TIME(6)-typed field of a
   database were wrongly serialized by Connector/Net. (Bug
   #17924388, Bug #70686)

 * The RenameColumn operation in an Entity Framework migration
   threw an Unknown column 'no' in the 'field list' error when
   Update-Database was applied. (Bug #17959787, Bug #71102)

 * A MySQL-session-state-enabled web application threw exceptions
   for referencing the wrong table name my_aspnet_Sessions
   (instead of the correct name my_aspnet_sessions). This was due
   to the incorrect case handling of the SQL queries for
   MySqlSessionStateStore. (Bug #17960855, Bug #69652)

 * The value for the Keepalive option in the connection string
   was interpreted by Connector/Net to be in milliseconds. This
   fix makes it to be interpreted as number of seconds, as
   specified in the documentation. (Bug #17981275, Bug #69484)

 * When using the Code First approach in Entity Framework 5,
   automatic 

MySQL Workbench 6.1.4 GA has been released

[karen langford]

Dear MySQL users,

The MySQL developer tools team announces 6.1.4 as our GA release for
MySQL Workbench 6.1.

MySQL Workbench 6.1 is an upcoming major update for the official MySQL
graphical development tool.

Introducing over 30 new features, this version has many significant
enhancements focusing on real-time performance assessment and analysis
from the SQL statement level to server internals and file IO. You can
see this from additions to the SQL Editor as well as new dashboard
visualization and reporting that take advantage of MySQL Server 5.6
and 5.7 Performance Schema, and enhancements to the MySQL Explain Plans.

Additionally Workbench 6.1 is leveraging work from various teammates in
MySQL Engineering by introducing a schema called SYS that provides
simplified views on Performance Schema, Information Schema, and other 
areas.

Special thanks to the server optimizer team, server runtime team, and Mark
Leith.  For Oracle DBAs MySQL SYS is similar to the V$ catalog views, and
MSSQL folks its like DMVs (Dynamic Management Views).

MySQL Workbench 6.1 includes:

* Improved drag and drop support in the Home screen and SQL Editor
* Visual Explain 2. The Visual Explain feature was revamped and is now
easier to read and interpret. You can also get the traditional tabular
explain output from within the same interface.
* Performance Dashboard. A graphical representation of some key statistics
from the server status, gives you a bird's eye view of the status of key
server subsystems.
* For advanced users, Performance Schema Instrumentation. A GUI for
configuring the Performance Schema in detail, for advanced users.
* Performance Schema based reporting. Gives insight into the operation
of the server through many high-level reports.
* New query result view. Get more information about queries you execute,
such as information about the fields in your result set and key performance
statistics from your query (timing, index usage, number of rows scanned,
joins etc).
* Form Editor for resultsets. In addition to the result grid, you can now
edit records row by row in a form style editor.
* Table Inspector. Similar to the Schema Inspector, view detailed
information from tables. A streamlined interface for creating indexes is
also included.
* Support for the Windows accessibility API and Windows high contrast
color schemes. A new high contrast theme has been introduced.
* And more.

More than 60 enhancement requests and bugs reported by users have also been
addressed, providing performance, usability and stability improvements
across the board.

For the full list of bugs fixed in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-1.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?151

Download MySQL Workbench 6.1.4 GA now, for Windows, Mac OS X 10.6+, Oracle
Linux 6, Fedora 19, Fedora 20, Ubuntu 12.04 and Ubuntu 13.10 or sources,
from:

http://dev.mysql.com/downloads/tools/workbench/

In Windows, you can also use the integrated MySQL Installer to update
MySQL Workbench and other MySQL products.

Quick links:
- http://mysqlworkbench.org/
- Download: http://dev.mysql.com/downloads/tools/workbench/
- Bugs: http://bugs.mysql.com
- Forums: http://forums.mysql.com/index.php?151

Enjoy!

Changes in MySQL Workbench 6.1.4 (2014-03-31)

   Functionality Added or Changed

 * The Beautify query feature was changed. It now only affects
   the current statement, unless there is an explicit selection.
   Before, it would reformat all statements in the window by
   default. (Bug #18237189, Bug #71544)

 * The default schema is now expanded automatically when a
   connection is opened, or when the default schema changes. (Bug
   #18237247, Bug #70522)

 * A specific connection string can now be passed to the --query
   command-line option at startup, in the form of --query
   user@host:port. If this connection string does not already
   exist, then it will be created. (Bug #17353691, Bug #70134)

 * MySQL Workbench now checks if the lower_case_table_name
   variable is correctly set on Microsoft Windows and Mac OS X
   systems. If not, then MySQL Workbench will display a dialog
   after connect, and emit a warning message when performing
   synchronization or reverse engineering actions. (Bug
   #14802853)

 * New Report a Bug functionality now opens a browser with the
   MySQL bug page pre-populated with MySQL Workbench data. This
   also allows MySQL Workbench to be fully manipulated while
   submitting the bug report. (Bug #14079590, Bug #65258)

   Bugs Fixed

 * The local private key file for an SSH connection when
   executing Remote Connection in MySQL Workbench through SSH
   could not be saved to a folder with accented characters. (Bug
   #18328846, Bug #71800)

 * FOUND_ROWS() (after a SQL_CALC_FOUND_ROWS statement) returned
   1 (true) instead of the 

MySQL Connector/Python 1.2.1 RC has been released

[karen langford]

Dear MySQL users,

MySQL Connector/Python v1.2.1 is the new version of
the 1.2 release series of the pure Python database driver
for MySQL. It is intended to introduce users to the new features.

MySQL Connector/Python version 1.2.1 is compatible with MySQL Server
versions 5.5 and greater, but should work with earlier versions
(greater than 4.1). Python 2.6 and 2.7, as well as Python 3.1
and greater are supported.

MySQL Connector/Python 1.2.1 is available for download from

http://dev.mysql.com/downloads/connector/python/#downloads

The ChangeLog file included in the distribution contains a brief summary
of changes in MySQL Connector/Python 1.2.1. For a more complete list of
changes, see below or online at:

http://dev.mysql.com/doc/relnotes/connector-python/en/

Changes in MySQL Connector/Python 1.2.1 (2014-03-31)

-- 



Functionality Added or Changed

 * It was not possible to initiate an SSL session without
   explicitly giving a key and certificate. Now it is possible to
   connect to a MySQL server using only the ssl_ca connection
   argument pointing to a file of CA certificates. This means the
   ssl_key and ssl_cert connection arguments are optional.
   However, when either is given, both must be given or an
   AttributeError is raised. (Bug #69418, Bug #17054848)

 * Connector/Python now supports authentication plugins found in
   MySQL 5.6. This includes mysql_clear_password and
   sha256_password, both of which require an SSL connection. The
   sha256_password plugin does not work over a non-SSL connection
   because Connector/Python does not support RSA encryption.
   The connect() method now supports an auth_plugin parameter
   that can be used to force use of a particular plugin. For
   example, if the server is configured to use sha256_password by
   default and you want to connect to an account that
   authenticates using mysql_native_password, either connect
   using SSL or specify auth_plugin='mysql_native_password'. (Bug
   #68054, Bug #16217765)

 * Connector/Python now permits the type for stored procedure
   parameters to be specified. To do this, specify a parameter as
   a two-item tuple consisting of the parameter value and type.
   For more information, see Method
   MySQLCursor.callproc(procname, args=())
(http://dev.mysql.com/doc/connector-python/en/connector-python-api-mysqlcursor-callproc.html). 


   (Bug #71124, Bug #17965619)

* A new MySQLConnection class reset_connection() method enables
   applications to send a COM_RESET_CONNECTION to the server.
   This method is analogous to the mysql_reset_connection() C API
   function added in MySQL 5.7.3.
   A new MySQLConnection class reset_session() method is similar
   to reset_connection() but falls back to use reauthentication
   for older servers that do not support COM_RESET_CONNECTION.

 * Connector/Python now can report errors to Fabric that occur
   while accessing a MySQL instance. The information can be used
   to update the backing store and trigger a failover operation,
   provided that the instance is a primary server and Fabric has
   received a sufficient number of problem reports from different
   connectors.

  + The fabric dictionary argument to the connect() method
now accepts a report_errors value. Its default value is
False; pass a value of True to enable error reporting to
Fabric.

  + To define which errors to report, use the
extra_failure_report() function:
from mysql.connector.fabric import extra_failure_report
extra_failure_report([error_code_0, error_code_1, ...])

 * Connector/Python now enables applications to specify
   additional information to be used when connecting to Fabric:
   User name and credentials, and information to use for
   establishing an SSL connection. The fabric dictionary argument
   to the connect() method accepts these additional values:
   username, password, ssl_ca, ssl_cert, ssl_key. Only the ssl_ca
   value is required to establish an SSL connection. If ssl_cert
   or ssl_key are given, both must be specified.

 * The connect() method now accepts a failover argument hat
   provides information to use for server failover in the event
   of connection failures. The argument value is a tuple or list
   of dictionaries (tuple is preferred because it is nonmutable).
   Each dictionary contains connection arguments for a given
   server in the failover sequence. Permitted dictionary values
   are: user, password, host, port, unix_socket, database,
   pool_name, pool_size.

   Bugs Fixed

 * The MySQLConnection.autocommit attribute failed to set the
   value of the self._autocommit 

MySQL Connector/J 5.1.30 has been released

[karen langford]

Hello all,

MySQL Connector/J 5.1.30, a maintenance release of the production 5.1
branch has been released. Connector/J is the Type-IV pure-Java JDBC
driver for MySQL.

Version 5.1.30 is suitable for use with many MySQL server versions,
including 4.1, 5.0, 5.1, 5.4, 5.5 and 5.6.

MySQL Connector Java (Commercial) is already available for download on the
My Oracle Support (MOS) website. This release will be available on eDelivery
(OSDC) in next month's upload cycle.

As always, we recommend that you check the CHANGES file in the
download archive to be aware of changes in behavior that might affect
your application.

MySQL Connector/J 5.1.30 includes the following general bug fixes and
improvements, also available in more detail on
http://dev.mysql.com/doc/relnotes/connector-j/en/news-5-1-30.html :

Changes in MySQL Connector/J 5.1.30 (2014-03-31)

   Functionality Added or Changed

 * Connector/J now supports MySQL Fabric. See Using Connector/J
   with MySQL Fabric
(http://dev.mysql.com/doc/connector-j/en/connector-j-usagenotes-fabric.html) 


for details.

   Bugs Fixed

 * Replaced a for loop with the System.arraycopy() method for
   copying array values in the
   MysqlIO.unpackNativeEncodedColumn() and
   LoadBalancingConnectionProxy.addHost() methods, in order to
   improve the two methods' performance. (Bug #18327245, Bug
   #71861)

 * Avoided the use of an iterator over the list of statement
   interceptors in the methods
   MysqlIO.invokeStatementInterceptorsPost() and
   MysqlIO.invokeStatementInterceptorsPre(), so that Connector/J
   does not increase the stack size unnecessarily. (Bug
   #18236388, Bug #71679)

 * Improved on the code for integer-to-hex conversion when
   building XA commands by avoiding the creation of temporary
   character arrays, thus enhancing performance. (Bug #18228302,
   Bug #71621)

 * The Field.getStringFromBytes() method created a useless byte
   array when using JVM's converter and the encoding defined by
   the connection. This fix makes the method call
   StringUtils.toString() using the original buffer instead of
   creating a temporary byte array for the call. (Bug #18228668,
   Bug #71623)

 * There were sporadic cases of the key store file being open
   hundreds of times and causing some Too many files open
   errors. This fix makes sure that in
   com.mysql.jdbc.ExportControlled and in
   MysqlIO.sendFileToServer(), the input stream for the key store
   file is explicitly closed after use. (Bug #18107621, Bug
   #71432)

 * It was intended that if a previous query on a connection had
   used the setMaxRows() method, in the next query, Connector/J
   would not cancel that by setting SQL_SELECT_LIMIT=DEFAULT if
   the query contained a LIMIT clause. However, in the actual
   implementation, the maximum row setting was reused in the
   subsequent query in various situations beyond expectation (for
   example, when a table name contains the string limit in it).
   This fix removes the LIMIT-clause parsing and replaces it by a
   better way of controlling the maximum rows per session. (Bug
   #18110320, Bug #71396)

 * When working with MySQL 5.6, calling
   PreparedStatement.setTimestamp() resulted in a
   java.lang.StringIndexOutOfBoundsException being thrown if the
   Timestamp contained a fractional second. This fix corrects the
   digit truncation performed in the formatNanos() method, which
   was the cause of the problem. (Bug #18091639)

 * Calling ResultSet.close() on an already closed ResultSet
   caused an SQLException. While the exception was silently
   discarded, it did result in performance issues. This fix makes
   Connector/J comply with the Java specification that when a
   ResultSet object is already closed, application of the close
   method on it should be a no-op. (Bug #16722637, Bug #67318)

 * Fixed the problem of the wrong source being provided when the
   build property com.mysql.jdbc.noCryptoBuild was set.

Thanks,

On behalf of Oracle/MySQL Build Team,
Murthy Narkedimilli

--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Utilities 1.4.2 (including MySQL Fabric) RC has been released

[karen langford]

Dear MySQL users,

MySQL Utilities version 1.4.2 is compatible with MySQL Server
versions 5.1 and greater, but should work with earlier versions
(greater than v4.1). Python v2.6 and v2.7 are supported.

In addition to server utilities, MySQL Utilities also contains
MySQL Fabric: a framework for managing a collection of MySQL servers.
MySQL Fabric is deployed as a separate service daemon that contains
support for high-availability and sharding.

The management framework maintains a database of the routing and
state information for the servers making up the system and provides
an easy-to-use command line interface for adding, removing and
organizing servers.

High-availability is provided by continuously monitoring the servers
and executing slave promotion when the master crashes and just as
importantly automatically updates the state and routing information
that gets messages to the right server.

MySQL Fabric comes with built-in support for sharding either using
ranges or consistent hashing and supports the sharding of multiple
tables to ensure that rows with matching sharding keys are stored
in the same shard. MySQL Fabric also contains support for global
tables that are duplicated on all shards as well as the ability to
synchronize schema updates across all of the servers.

To provide high performance and avoid latency, transactions are
directly routed by Fabric-aware connectors rather than routing via
an external proxy. The connectors dispatch transactions to the
correct shard, perform load-balancing, and handle read-write
splitting. Currently there exists Fabric-aware versions of
Connector/Python, Connector/Java, and Connector/PHP (through a
Fabric-aware mysqlnd_ms plugin).

MySQL Utilities v1.4.2 is available for download from

http://dev.mysql.com/downloads/tools/utilities/

A brief summary of changes is listed below. Please check the
CHANGES.txt file inside the distribution for a more complete list
of changes.

Functionality Added or Changed (2014-03-31)
---

  * The mysqlrplsync utility was added, which checks data
consistency between servers in a replicated setup.

  * The mysqlrplms utility was added, which provides round-robin
multi-source replication (a slave server continually cycles
through multiple masters in order to store a consolidated data
set).

Bugs Fixed
--

  * With fabric, the scheduler did not check and determine which
procedures needed to be notified after releasing the procedure
that was blocking them. (Bug #18454582, Bug #72117)

  * With fabric, failover was not handled properly when both the
global and shard groups had a failed master. (Bug #18403885,
Bug #72016)

  * The mysqlrplsync utility would crash when the --exclude option
was used, and at least one database was available to be
checked. This issue was due to an incomplete check when
determining which tables to exclude from the slaves. (Bug
#18388846)

  * The MySQL Utilities testing suite (mut) now tests if ports are
available before assigning them to a test. (Bug #18339351)

  * MySQL Server UUIDs are now handled in a case-insensitive way,
more precisely when checking if GTIDs belong to the master.
This helps accommodate MySQL Server 5.6.9, which could change
the case for the server_uuid variable. (Bug #18275566)

  * With Fabric, attempting to destroy a group when the group was
used in the shard sub-system would output an unfriendly and
unclear error. Fabric now checks if the group is used in the
shard sub-system before trying to destroy (remove) it, and a
clearer error is emitted if it is in use. (Bug #18280004, Bug
#71766)

  * The mut rpl_admin_gtid test result varied from host to host,
due to using the RESET MASTER statement without first stopping
all the slaves. This resulted in undefined behavior, which led
to inconsistent rest results. (Bug #18203946)

  * A typo was fixed in the mysqldbcopy utility's help text. (Bug
#18206923, Bug #71627)

  * With Fabric, group definitions now use a single (global)
username and password, instead of requiring a
username/password for each MySQL server when they were added
to the group. (Bug #18153823, Bug #71512)

  * When checking for proper permissions, Fabric would execute
several SELECT statements against the 'mysql' database, which
caused the login mechanism to fail if the user lacked access.
This mechanism now uses 'SHOW GRANTS' statements instead, and
now prints out a detailed error message when access is
unavailable. (Bug #18138545, Bug #71448)

  * The server.set_status() function's status parameter now
accepts an integer, to better coincide with the integer value
provided by dump_servers(). The strings PRIMARY,
SECONDARY, SPARE and FAULTY also remain as acceptable
values. (Bug #18124108, Bug #71428)

  * The mysqlrpladmin utility did not correctly account for

MySQL Workbench 6.1.3 RC has been released

[karen langford]

Dear MySQL users,

The MySQL developer tools team announces 6.1.3 RC - the final release
candidate for MySQL Workbench 6.1.

MySQL Workbench 6.1 is the upcoming major update for the official MySQL
graphical development tool.

Introducing over 30 new features, this version has many significant
enhancement focusing on real-time performance assessment and analysis
from the SQL statement level to server internals and file IO. You'll
see this in additions to the SQL Editor as well as new dashboard
visualization and reporting that takes advantage of MySQL Server 5.6
and 5.7 Performance Schema, and enhancements to the MySQL Explain Plans.

Additionally Workbench 6.1 is leveraging work from various teammates in
MySQL Engineering by introducing a schema called SYS that provides
simplified views on Performance Schema, Information Schema, and other 
areas.

Special thanks to the server optimizer team, server runtime team, and Mark
Leith.  For Oracle DBAs MySQL SYS is similar to the V$ catalog views and
MSSQL folks its like DMVs (Dynamic Management Views).

MySQL Workbench 6.1 includes:

* Improved drag and drop support in the Home screen and SQL Editor
* Visual Explain 2. The Visual Explain feature was revamped and is now
easier to read and interpret. You can also get the traditional tabular
explain output from within the same interface.
* Performance Dashboard. A graphical representation of some key statistics
from the server status, gives you a bird's eye view of the status of key
server subsystems.
* For advanced users, Performance Schema Instrumentation. A GUI for
configuring the Performance Schema in detail, for advanced users.
* Performance Schema based reporting. Gives insight into the operation
of the server through many high-level reports.
* New query result view. Get more information about queries you execute,
such as information about the fields in your result set and key performance
statistics from your query (timing, index usage, number of rows scanned,
joins etc).
* Form Editor for resultsets. In addition to the result grid, you can now
edit records row by row in a form style editor.
* Table Inspector. Similar to the Schema Inspector, view detailed
information from tables. A streamlined interface for creating indexes is
also included.
* Support for the Windows accessibility API and Windows high contrast
color schemes. A new high contrast theme has been introduced.
* And more.

More than 60 enhancement requests and bugs reported by users have also been
addressed, providing performance, usability and stability improvements
across the board.

For the full list of bugs fixed in this revision, visit
http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-1.html

For discussion, join the MySQL Workbench Forums:
http://forums.mysql.com/index.php?151

Download MySQL Workbench 6.1.3 RC now, for Windows, Mac OS X 10.6+, Oracle
Linux 6, Fedora 19, Fedora 20, Ubuntu 12.04 and Ubuntu 13.10 or sources,
from:

http://dev.mysql.com/downloads/tools/workbench/

In Windows, you can also use the integrated MySQL Installer to update
MySQL Workbench and other MySQL products.

Quick links:
- http://mysqlworkbench.org/
- Download: http://dev.mysql.com/downloads/tools/workbench/
- Bugs: http://bugs.mysql.com
- Forums: http://forums.mysql.com/index.php?151

Enjoy!

Changes in MySQL Workbench 6.1.3 (2014-03-24, RC)

   Functionality Added or Changed

 * The Beautify query feature was changed. It now only affects
   the current statement, unless there is an explicit selection.
   Before, it would reformat all statements in the window by
   default. (Bug #18237189, Bug #71544)

 * The default schema is now expanded automatically when a
   connection is opened, or when the default schema changes. (Bug
   #18237247, Bug #70522)

 * A specific connection string can now be passed to the --query
   command-line option at startup, in the form of --query
   user@host:port. If this connection string does not already
   exist, then it will be created. (Bug #17353691, Bug #70134)

 * MySQL Workbench now checks if the lower_case_table_name
   variable is correctly set on Microsoft Windows and Mac OS X
   systems. If not, then MySQL Workbench will display a dialog
   after connect, and emit a warning message when performing
   synchronization or reverse engineering actions. (Bug
   #14802853)

 * New Report a Bug functionality now opens a browser with the
   MySQL bug page pre-populated with MySQL Workbench data. This
   also allows MySQL Workbench to be fully manipulated while
   submitting the bug report. (Bug #14079590, Bug #65258)

   Bugs Fixed

 * The local private key file for an SSH connection when
   executing Remote Connection in MySQL Workbench through SSH
   could not be saved to a folder with accented characters. (Bug
   #18328846, Bug #71800)

 * FOUND_ROWS() (after a SQL_CALC_FOUND_ROWS statement) returned
   1 (true) 

MySQL Enterprise Backup 3.10.0 has been released

[karen langford]

Dear MySQL users,

MySQL Enterprise Backup v3.10.0, a new version of the online MySQL backup
tool, is now available for download from the My Oracle Support (MOS) website
as our latest GA release. This release will be available on eDelivery (OSDC)
after the next upload cycle. MySQL Enterprise Backup is a commercial
extension.

A brief summary of the changes in MySQL Enterprise Backup (MEB)
version 3.10.0 is given below.

Changes in MySQL Enterprise Backup 3.10.0 (2014-03-10)

Functionality Added or Changed

 * When using the --skip-unused-pages option for backup
   operations, MySQL Enterprise Backup now displays, besides the
   number of pages of data skipped, the total amount of memory
   saved by using the option. (Bug #15915315)

 * In order to enhance security for backed up data, MySQL
   Enterprise Backup now provides encryption function for
   single-file backups. See Section 7.3, Encryption for Backups
   and Section 5.1.14, Encryption Options for details.

 * The compression feature of MySQL Enterprise Backup has been
   enhanced by the addition of two compression algorithms: the
   LZ4 method (the default for MySQL Enterprise Backup 3.10 and
   after) and the LZMA method. Because the LZ4 algorithm, though
   faster, produces larger files than the ZLIB algorithm used in
   MySQL Enterprise Backup 3.9 and earlier, users of MySQL
   Enterprise Backup 3.10 will find an increase in the size of
   the compressed files if they use the default values for the
   compression options.

 * Backups created with the --use-tts option can now be restored
   in a single step using the copy-back-and-apply-log subcommand.

 * When the apply-log or apply-incremental-backup operation was
   performed repeatedly on a backup without using the --force
   option, an error message was thrown. From MySQL Enterprise
   Backup release 3.10.0 onward, the same action just causes a
   message to be returned, saying the operation has already been
   performed.

 * MySQL Enterprise Backup can now validate data integrity of a
   backup directory as well as a backup image file. The
   validation function in 3.10 has also become more robust, as it
   tries to verify the checksum value of every data page.

 * MySQL Enterprise Backup 3.10 introduces two new options for
   partial backup: --include-tables and --exclude-tables. The new
   options are intended for replacing the older options of
   --include, --databases, --databases-list-file, and
   --only-innodb-with-frm, which will be deprecated in the near
   future.

   Bugs Fixed

 * mysqlbackup could not read the value of innodb_data_file_path
   from the server when it was more than 1024-character long. It
   was because mysqlbackup could not read the value from the
   configuration files and relied on the SHOW VARIABLES command
   (which reads no more than 1024 characters) to access the
   parameter. With this fix, innodb_data_file_path can now be
   read from the configuration files. (Bug #18038409)

 * A backup taken with both the --use-tts=with-full-locking and
   --skip-unused-pages options could not be restored. This was
   because with --use-tts=with-full-locking used, the apply-log
   operation was always skipped (the command did nothing to the
   backup), while the expansion of the unused pages was part of
   the apply-log operation. This fix separates the expansion from
   the apply-log operation, so that the backup can be restored.
   (Bug #17764917)

 * When a database was initialized with --innodb-file-per-table=0
   and had a fixed-size system tablespace, all non-InnoDB files
   backed up had zero size. (Bug #17793020)

 * After a server restoration from an incremental backup with the
   copy-back-and-apply-log subcommand, mysqlbackup returned a
   success code even after a file renaming failed during the
   restoration process. The restored server thus failed to start
   with an assertion error. This fix makes sure a proper error is
   thrown when a file renaming fails during a restoration. (Bug
   #17539568)

 * In a replication setup, when a backup was performed on a
   master, the modifications of the tables mysql.backup_history
   and mysql.backup_progress were propagated to the slaves,
   causing a wrong backup status for the slaves to be registered.
   This fix makes MySQL Backup Enterprise disable binary logging
   by setting set sql_log_bin=0 during a backup on the master, so
   that the backup information will not get replicated to the
   slaves. (Bug #17449449)

 * When the --messages-logdir option was used and the --trace
   option was set to 2 or 3 for an apply-log operation, MySQL
   Enterprise Backup created an extra log file. (Bug #17271318)

 * When 

MySQL Community Server 5.5.25a has been released

[karen langford]

Dear MySQL users,

MySQL 5.5.25a is a new version of the 5.5 production release of the
world's most popular open source database. MySQL 5.5.25a is recommended
for use on production systems.

MySQL 5.5.25a is a replacement of MySQL 5.5.25, in that version a
regression bug was detected in the optimizer (Bug #65745).
Because of this, MySQL 5.5.25 has been removed from the download sites.
We recommend that users who have installed MySQL 5.5.25 upgrade to
MySQL 5.5.25a at the earliest opportunity.
That bug is specific to MySQL 5.5.25, other versions are not affected.

MySQL 5.5 includes several high-impact enhancements to improve the
performance and scalability of the MySQL Database, taking advantage of
the latest multi-CPU and multi-core hardware and operating systems. In
addition, with release 5.5, InnoDB is now the default storage engine for
the MySQL Database, delivering ACID transactions, referential integrity
and crash recovery by default.

MySQL 5.5 also provides a number of additional enhancements including:

- Significantly improved performance on Windows, with various
  Windows specific features and improvements
- Higher availability, with new semi-synchronous replication and
  Replication Heart Beat
- Improved usability, with Improved index and table partitioning,
  SIGNAL/RESIGNAL support and enhanced diagnostics, including a new
  Performance Schema monitoring capability.

For a more complete look at what's new in MySQL 5.5, please see the
following resources:

MySQL 5.5 is GA, Interview with Tomas Ulin:
http://dev.mysql.com/tech-resources/interviews/thomas-ulin-mysql-55.html

Documentation:
http://dev.mysql.com/doc/refman/5.5/en/mysql-nutshell.html

Whitepaper: What's New in MySQL 5.5:
http://dev.mysql.com/why-mysql/white-papers/mysql-wp-whatsnew-mysql-55.php

If you are running a MySQL production level system, we would like to
direct your attention to MySQL Enterprise Edition, which includes the
most comprehensive set of MySQL production, backup, monitoring,
modeling, development, and administration tools so businesses can
achieve the highest levels of MySQL performance, security and uptime.
http://mysql.com/products/enterprise/

For information on installing MySQL 5.5.25a on new servers, please see
the MySQL installation documentation at
http://dev.mysql.com/doc/refman/5.5/en/installing.html

For upgrading from previous MySQL releases, please see the important
upgrade considerations at:
http://dev.mysql.com/doc/refman/5.5/en/upgrading.html

MySQL Database 5.5.25a is available in source and binary form for a
number of platforms from our download pages at:
http://dev.mysql.com/downloads/mysql/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc.:
http://forge.mysql.com/wiki/Contributing

The following sections list the changes in the MySQL source code since
the previous released versions, MySQL 5.5.25 (withdrawn) and MySQL
5.5.24. They may also be viewed online at:
http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25a.html
http://dev.mysql.com/doc/refman/5.5/en/news-5-5-25.html

Enjoy!



D.1.2. Changes in MySQL 5.5.25a (2012-July-05)

   Note

   Due to MSI restrictions, the MSI packages of MySQL 5.5.25a will
   treat the version as 5.5.26 internally; for example, as displayed
   by the Installation Wizard. MySQL itself reports the version as
   5.5.25a; for example, if you check the value of the VERSION() SQL
   function or the version system variable.

   Bugs Fixed

 * A regression bug in the optimizer could cause excessive disk
   usage for UPDATE statements. (Bug #65745, Bug #14248833)



D.1.3. Changes in MySQL 5.5.25 (2012-May-30)

   Note

   MySQL 5.5.25 is superseded by MySQL 5.5.25a due to a regression bug
   that can cause excessive disk usage (for details, see Bug #65745).
   Current users of 5.5.25: Monitor disk usage and upgrade to 5.5.25a
   as soon as that is made available.
   Users contemplating upgrades to 5.5.25: Defer and upgrade to 5.5.25a
   instead when that is made available.

Functionality Added or Changed

  * Important Change: Replication: The SHOW BINARY LOGS statement
(and its equivalent SHOW MASTER LOGS) may now be executed by a
user with the REPLICATION CLIENT privilege. (Formerly, the
SUPER privilege was necessary to use either form of this
statement.)

  * The --safe-mode server option now is deprecated and will be
removed in MySQL 5.6.

Bugs Fixed

  * Performance: InnoDB: Improved the algorithm related to
adaptive flushing. This fix increases the rate of flushing in
cases where compression is used and the data set is larger
than the buffer pool, leading to eviction. (Bug #13990648, Bug
#65061)

  * InnoDB: In a transaction using the REPEATABLE READ isolation
level, an UPDATE or DELETE 

MySQL Community Server 5.0.96 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.0.96, a new version of the popular Open Source Database
Management System, has been released.  Please note that the active
maintenance of 5.0 has ended, and these builds are only provided
because of the fixes to security bugs as described below.

The release is now available in source and binary form for a number of
platforms from our archive download page at

http://dev.mysql.com/downloads/

Mirror service for MySQL Server 5.0 has ended.  Also, support for some
platforms with very low demand has ended.  Please bear in mind that
MySQL 5.0 now receives extended support only, and that all active
development is happening on MySQL 5.1, 5.5, and beyond. You will find
the MySQL Lifecycle policy here:

http://www.mysql.com/support

For your own best interest, we strongly recommend all current users of
MySQL 5.0 to upgrade to MySQL 5.1.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc:

http://forge.mysql.com/wiki/Contributing

This section documents all changes and bugfixes that have been applied
since the last MySQL Server release (5.0.95).

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-96.html

If you would like to receive more fine-grained and personalized update
alerts about fixes that are relevant to the version and features you
use, please consider subscribing to MySQL Enterprise (a commercial
MySQL offering). For more details please see

http://www.mysql.com/products/enterprise/advisors.html

Changes in MySQL 5.0.96  (21 March, 2012)

  End of Product LifecycleActive development for MySQL Database
  Server version 5.0 has ended. Oracle offers various support
  offerings which may be of interest. For details and more
  information, see the MySQL section of the Lifetime Support Policy
  for Oracle Technology Products
  (http://www.oracle.com/us/support/lifetime-support/index.html).
  Please consider upgrading to a recent version.

   Functionality Added or Changed

 * yaSSL was upgraded from version 1.7.2 to 2.2.0.

Thanks,
Sunanda Menon
Release Engineer, MySQL, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Community Server 5.1.62 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.62, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.62 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.62 on new servers or upgrading
to MySQL 5.1.62 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-62.html

Enjoy!

===
D.1.1. Changes in MySQL 5.1.62 (21 March, 2012)

   Functionality Added or Changed

 * yaSSL was upgraded from version 1.7.2 to 2.2.0.

   Bugs Fixed

 * Security Fix: Bug #13510739 and Bug #63775 were fixed.

 * Incompatible Change: An earlier change (in MySQL 5.1.59 and
   5.5.16) was found to modify date-handling behavior in General
   Availability-status series (MySQL 5.1 and 5.5). This change
   has been reverted.
   The change was that several functions became more strict when
   passed a DATE() function value as their argument, thus they
   rejected incomplete dates with a day part of zero. These
   functions were affected: CONVERT_TZ(), DATE_ADD(), DATE_SUB(),
   DAYOFYEAR(), LAST_DAY(), TIMESTAMPDIFF(), TO_DAYS(),
   TO_SECONDS()
   (http://dev.mysql.com/doc/refman/5.5/en/date-and-time-function
   s.html#function_to-seconds), WEEK(), WEEKDAY(), WEEKOFYEAR(),
   YEARWEEK(). The previous behavior has been restored. (Bug
   #13458237)

 * Important Change: InnoDB Storage Engine: When a row grew in
   size due to an UPDATE operation, other (non-updated) columns
   could be moved to off-page storage so that information about
   the row still fit within the constraints of the InnoDB page
   size. The pointer to the new allocated off-page data was not
   set up until the pages were allocated and written, potentially
   leading to lost data if the system crashed while the column
   was being moved out of the page. The problem was more common
   with tables using ROW_FORMAT=DYNAMIC or ROW_FORMAT=COMPRESSED
   along with the Barracuda file format, particularly with the
   innodb_file_per_table setting enabled, because page allocation
   operations are more common as the .ibd tablespace files are
   extended. Still, the problem could occur with any combination
   of InnoDB version, file format, and row format.
   A related issue was that during such an UPDATE operation, or
   an INSERT operation that reused a delete-marked record, other
   transactions could see invalid data for the affected column,
   regardless of isolation level.
   The fix corrects the order of operations for moving the column
   data off the original page and replacing it with a pointer.
   Now if a crash occurs at the precise moment when the column
   data is being transferred, the transfer will not be re-run
   during crash recovery.
   In MySQL 5.1, this fix applies to the InnoDB Plugin, but not
   the built-in InnoDB storage engine. (Bug #13721257, Bug
   #12612184, Bug #12704861)

 * InnoDB Storage Engine: An erroneous assertion could occur, in
   debug builds only, when creating an index on a column
   containing zero-length values (that is, ''). (Bug #13654923)

 * InnoDB Storage Engine: A DDL operation such as ALTER TABLE ...
   ADD COLUMN could stall, eventually timing out with an Error
   1005: Can't create table message referring to
   fil_rename_tablespace. (Bug #13636122, Bug #62100, Bug #63553)

 * InnoDB Storage Engine: References to C preprocessor symbols
   and macros HAVE_purify, UNIV_INIT_MEM_TO_ZERO, and
   UNIV_SET_MEM_TO_ZERO were removed from the InnoDB source code.
   They were only used in debug builds instrumented for Valgrind.
   They are replaced by calls to the UNIV_MEM_INVALID() macro.
   (Bug #13418934)

 * InnoDB Storage Engine: A DDL operation for an InnoDB table
   could cause a busy MySQL server to halt with an assertion
   error:
InnoDB: Failing assertion: 

MySQL Community Server 5.1.61 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.61, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.61 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.61 on new servers or upgrading
to MySQL 5.1.61 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-61.html

Enjoy!

===
D.1.1. Changes in MySQL 5.1.61 (10 January, 2012)


   Bugs Fixed

 * InnoDB Storage Engine: Issuing INSERT...ON DUPLICATE KEY
   statements for InnoDB tables from concurrent threads could
   cause a deadlock
   (http://dev.mysql.com/doc/refman/5.5/en/glossary.html#glos_dea
   dlock), particularly with the INSERT...ON DUPLICATE KEY UPDATE
   form. The fix avoids deadlocks caused by the same row being
   accessed by more than one transaction. Deadlocks could still
   occur when multiple rows are inserted and updated
   simultaneously by different transactions in inconsistent
   order; those types of deadlocks require the standard error
   handling on the application side, of re-trying the
   transaction. (Bug #11759688, Bug #52020)

 * An incorrect InnoDB assertion could cause the server to halt.
   This issue only affected debug builds. The assertion
   referenced the source file btr0pcur.ic and the variable
   cursor-pos_state. (Bug #13358468)

 * The handle_segfault() signal-handler code in mysqld could
   itself crash due to calling unsafe functions. (Bug #54082, Bug
   #11761576)

 * ARCHIVE tables with NULL columns could cause server crashes or
   become corrupt under concurrent load. (Bug #51252, Bug
   #11758979)

 * Enabling myisam_use_mmap could cause the server to crash. (Bug
   #48726, Bug #11756764)

 * Concurrent access to ARCHIVE tables could cause corruption.
   (Bug #42784, Bug #11751793)


Thanks,
MySQL RE Team
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql

MySQL Community Server 5.1.60 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.60, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.60 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.60 on new servers or upgrading
to MySQL 5.1.60 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-60.html

Enjoy!

===
D.1.1. Changes in MySQL 5.1.60 (16 November, 2011)

   Functionality Added or Changed

 * Upgrading from an Advanced GPL RPM package to an Advanced RPM
   package did not work. Now on Linux it is possible to use rpm
   -U to replace any installed MySQL product by any other of the
   same release family. It is not necessary to remove the old
   produce with rpm -e first. (Bug #11886309)

 * MEMORY table creation time is now available in the CREATE_TIME
   column of the INFORMATION_SCHEMA.TABLES table and the
   Create_time column of SHOW TABLE STATUS output. (Bug #51655,
   Bug #11759349)

   Bugs Fixed

 * InnoDB Storage Engine: This fix improves the performance of
   instrumentation code for InnoDB buffer pool operations. (Bug
   #12950803, Bug #62294)

 * InnoDB Storage Engine: Data from BLOB columns could be lost if
   the server crashed at a precise moment when other columns were
   being updated in an InnoDB table. (Bug #12704861)

 * InnoDB Storage Engine: Lookups using secondary indexes could
   give incorrect matches under a specific set of conditions. The
   conditions involve an index defined on a column prefix, for a
   BLOB or other long column stored outside the index page, with
   a table using the Barracuda file format. (Bug #12601439)

 * InnoDB Storage Engine: This fix corrects cases where the MySQL
   server could hang or abort with a long semaphore wait message.
   (This is a different issue than when these symptoms occurred
   during a CHECK TABLE statement.) (Bug #11766591, Bug #59733)

 * Replication: Issuing the following statements, in the order
   shown, could cause a deadlock between the user thread and I/O
   thread:
START SLAVE;
STOP SLAVE SQL_THREAD;
START SLAVE;
   (Bug #11878104)
   See also Bug #44312, Bug #11752963, Bug #38715, Bug #38716.

 * Internal conversion of zero to binary and back could yield a
   result with incorrect precision. (Bug #12911710)

 * Valgrind warnings generated by filesort operations were fixed.
   (Bug #12856915)

 * Several improvements were made to the libedit library bundled
   with MySQL distributions, and that is available for all
   platforms that MySQL supports except Windows.

  + Navigation keys did not work for UTF-8 input.

  + Word navigation and delete operations did not work for
UTF-8 input with Cyrillic characters.

  + Nonlatin characters were corrupted in overwrite mode for
UTF-8 input.

  + Long queries caused the statement history file to become
corrupted.

  + The Alt key caused history operations to fail.
   (Bug #12605400, Bug #12613725, Bug #12618092, Bug #12624155,
   Bug #12617651, Bug #12605388)

 * The help message for mysql_install_db did not indicate that it
   supports the --defaults-file, --defaults-extra-file and
   --no-defaults options. (Bug #58898, Bug #11765888)

 * An assertion designed to detect zero-length sort keys also was
   raised when the entire key set fit in memory. (Bug #58200, Bug
   #11765254)

 * myisampack could create corrupt FULLTEXT indexes when
   compressing tables. (Bug #53646, Bug #11761180)

 * OPTIMIZE TABLE could corrupt MyISAM tables if myisam_use_mmap
   was enabled. (Bug #49030, Bug #11757032)

 * If MySQL was configured with --without-plugin-innobase and
   --with-plugin-innodb_plugin, to suppress building the built-in
   InnoDB storage engine and build the InnoDB Plugin 

MySQL Database Server 5.1.59 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.59, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.59 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.59 on new servers or upgrading
to MySQL 5.1.59 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-59.html

Enjoy!

===

D.1.2. Changes in MySQL 5.1.59 (15 September, 2011)

   Functionality Added or Changed

 * If the --with-ndbcluster option is given to the configure
   script, it now produces a warning that the version of MySQL
   Cluster included in 5.1 is no longer maintained. (The separate
   MySQL Cluster distribution should be used instead.) (Bug
   #49093, Bug #11757091)

   Bugs Fixed

 * InnoDB Storage Engine: The random read-ahead
   (http://dev.mysql.com/doc/innodb-plugin/1.0/en/glossary.html#g
   los_read_ahead) feature that was removed from the InnoDB
   Plugin is now available again. Because it is only helpful for
   certain workloads, it is turned off by default. To turn it on,
   enable the innodb_random_read_ahead configuration option.
   Because this feature can improve performance in some cases and
   reduce performance in others, before relying on this setting,
   benchmark both with and without the setting enabled. (Bug
   #12356373)

 * Partitioning: Auto-increment columns of partitioned tables
   were checked even when they were not being written to. In
   debug builds, this could lead to a server crash. (Bug
   #11765667, Bug #58655)

 * The option-parsing code for empty strings leaked memory. (Bug
   #12589928)

 * Replication: Processing of corrupted table map events could
   cause the server to crash. This was especially likely if the
   events mapped different tables to the same identifier, such as
   could happen due to Bug#56226.
   Now, before applying a table map event, the server checks
   whether the table has already been mapped with different
   settings, and if so, an error is raised and the slave SQL
   thread stops. If it has been mapped with the same settings, or
   if the table is set to be ignored by filtering rules, there is
   no change in behavior: the event is skipped and IDs are not
   checked. (Bug #44360, Bug #11753004)
   See also Bug #11763509.

 * ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except
   rename columns if the old and new versions of the table had
   exactly the same structure with respect to column data types.
   As a result, the mapping of column name to column data was
   incorrect. The same thing happened for ALTER TABLE DROP COLUMN
   ... ADD COLUMN statements intended to produce a new version of
   the table with exactly the same structure as the old version.
   (Bug #61493, Bug #12652385)

 * For a lower_case_table_names value of 1 or 2 and a database
   having a mixed-case name, calling a stored function using a
   fully qualified name including the database name failed. (Bug
   #60347, Bug #11840395)

 * Previously, Performance Schema table columns that held byte
   counts were BIGINT UNSIGNED. These were changed to BIGINT
   (signed). This makes it easier to perform calculations that
   compute differences between columns. (Bug #59631, Bug
   #11766504)

 * For MyISAM tables, attempts to insert incorrect data into an
   indexed GEOMETRY column could result in table corruption. (Bug
   #57323, Bug #11764487)

 * A race condition between loading a stored routine using the
   name qualified by the database name and dropping that database
   resulted in a spurious error message: The table mysql.proc is
   missing, corrupt, or contains bad data (Bug #47870, Bug
   #11756013)

 * Upgrades using an RPM package recreated the test database,
   which is undesirable when the DBA had removed it. (Bug #45415,
 

MySQL Database Server 5.1.59 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.59, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.59 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.59 on new servers or upgrading
to MySQL 5.1.59 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-59.html

Enjoy!

===

D.1.2. Changes in MySQL 5.1.59 (15 September, 2011)

   Functionality Added or Changed

 * If the --with-ndbcluster option is given to the configure
   script, it now produces a warning that the version of MySQL
   Cluster included in 5.1 is no longer maintained. (The separate
   MySQL Cluster distribution should be used instead.) (Bug
   #49093, Bug #11757091)

   Bugs Fixed

 * InnoDB Storage Engine: The random read-ahead
   (http://dev.mysql.com/doc/innodb-plugin/1.0/en/glossary.html#g
   los_read_ahead) feature that was removed from the InnoDB
   Plugin is now available again. Because it is only helpful for
   certain workloads, it is turned off by default. To turn it on,
   enable the innodb_random_read_ahead configuration option.
   Because this feature can improve performance in some cases and
   reduce performance in others, before relying on this setting,
   benchmark both with and without the setting enabled. (Bug
   #12356373)

 * Partitioning: Auto-increment columns of partitioned tables
   were checked even when they were not being written to. In
   debug builds, this could lead to a server crash. (Bug
   #11765667, Bug #58655)

 * The option-parsing code for empty strings leaked memory. (Bug
   #12589928)

 * Replication: Processing of corrupted table map events could
   cause the server to crash. This was especially likely if the
   events mapped different tables to the same identifier, such as
   could happen due to Bug#56226.
   Now, before applying a table map event, the server checks
   whether the table has already been mapped with different
   settings, and if so, an error is raised and the slave SQL
   thread stops. If it has been mapped with the same settings, or
   if the table is set to be ignored by filtering rules, there is
   no change in behavior: the event is skipped and IDs are not
   checked. (Bug #44360, Bug #11753004)
   See also Bug #11763509.

 * ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except
   rename columns if the old and new versions of the table had
   exactly the same structure with respect to column data types.
   As a result, the mapping of column name to column data was
   incorrect. The same thing happened for ALTER TABLE DROP COLUMN
   ... ADD COLUMN statements intended to produce a new version of
   the table with exactly the same structure as the old version.
   (Bug #61493, Bug #12652385)

 * For a lower_case_table_names value of 1 or 2 and a database
   having a mixed-case name, calling a stored function using a
   fully qualified name including the database name failed. (Bug
   #60347, Bug #11840395)

 * Previously, Performance Schema table columns that held byte
   counts were BIGINT UNSIGNED. These were changed to BIGINT
   (signed). This makes it easier to perform calculations that
   compute differences between columns. (Bug #59631, Bug
   #11766504)

 * For MyISAM tables, attempts to insert incorrect data into an
   indexed GEOMETRY column could result in table corruption. (Bug
   #57323, Bug #11764487)

 * A race condition between loading a stored routine using the
   name qualified by the database name and dropping that database
   resulted in a spurious error message: The table mysql.proc is
   missing, corrupt, or contains bad data (Bug #47870, Bug
   #11756013)

 * Upgrades using an RPM package recreated the test database,
   which is undesirable when the DBA had removed it. (Bug #45415,
 

MySQL Database Server 5.1.59 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.59, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.59 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

   http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.59 on new servers or upgrading
to MySQL 5.1.59 from previous MySQL releases, please see

   http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at
  
   http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

   http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

   http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

   http://dev.mysql.com/doc/refman/5.1/en/news-5-1-59.html

Enjoy!

===

D.1.2. Changes in MySQL 5.1.59 (15 September, 2011)

   Functionality Added or Changed

 * If the --with-ndbcluster option is given to the configure
   script, it now produces a warning that the version of MySQL
   Cluster included in 5.1 is no longer maintained. (The separate
   MySQL Cluster distribution should be used instead.) (Bug
   #49093, Bug #11757091)

   Bugs Fixed

 * InnoDB Storage Engine: The random read-ahead
   (http://dev.mysql.com/doc/innodb-plugin/1.0/en/glossary.html#g
   los_read_ahead) feature that was removed from the InnoDB
   Plugin is now available again. Because it is only helpful for
   certain workloads, it is turned off by default. To turn it on,
   enable the innodb_random_read_ahead configuration option.
   Because this feature can improve performance in some cases and
   reduce performance in others, before relying on this setting,
   benchmark both with and without the setting enabled. (Bug
   #12356373)

 * Partitioning: Auto-increment columns of partitioned tables
   were checked even when they were not being written to. In
   debug builds, this could lead to a server crash. (Bug
   #11765667, Bug #58655)

 * The option-parsing code for empty strings leaked memory. (Bug
   #12589928)

 * Replication: Processing of corrupted table map events could
   cause the server to crash. This was especially likely if the
   events mapped different tables to the same identifier, such as
   could happen due to Bug#56226.
   Now, before applying a table map event, the server checks
   whether the table has already been mapped with different
   settings, and if so, an error is raised and the slave SQL
   thread stops. If it has been mapped with the same settings, or
   if the table is set to be ignored by filtering rules, there is
   no change in behavior: the event is skipped and IDs are not
   checked. (Bug #44360, Bug #11753004)
   See also Bug #11763509.

 * ALTER TABLE {MODIFY|CHANGE} ... FIRST did nothing except
   rename columns if the old and new versions of the table had
   exactly the same structure with respect to column data types.
   As a result, the mapping of column name to column data was
   incorrect. The same thing happened for ALTER TABLE DROP COLUMN
   ... ADD COLUMN statements intended to produce a new version of
   the table with exactly the same structure as the old version.
   (Bug #61493, Bug #12652385)

 * For a lower_case_table_names value of 1 or 2 and a database
   having a mixed-case name, calling a stored function using a
   fully qualified name including the database name failed. (Bug
   #60347, Bug #11840395)

 * Previously, Performance Schema table columns that held byte
   counts were BIGINT UNSIGNED. These were changed to BIGINT
   (signed). This makes it easier to perform calculations that
   compute differences between columns. (Bug #59631, Bug
   #11766504)

 * For MyISAM tables, attempts to insert incorrect data into an
   indexed GEOMETRY column could result in table corruption. (Bug
   #57323, Bug #11764487)

 * A race condition between loading a stored routine using the
   name qualified by the database name and dropping that database
   resulted in a spurious error message: The table mysql.proc is
   missing, corrupt, or contains bad data (Bug #47870, Bug
   #11756013)

 * Upgrades using an RPM package recreated the test database,
   which is undesirable when the DBA had 

MySQL Database Server 5.1.58 has been released

[Karen Langford]

Dear MySQL users,

MySQL Server 5.1.58, a new version of the popular Open Source
Database Management System, has been released. MySQL 5.1.58 is
recommended for use on production systems.

For an overview of what's new in MySQL 5.1, please see

http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html

For information on installing MySQL 5.1.58 on new servers or upgrading
to MySQL 5.1.58 from previous MySQL releases, please see

http://dev.mysql.com/doc/refman/5.1/en/installing.html

MySQL Server is available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

Not all mirror sites may be up to date at this point in time, so if you
can't find this version on some mirror, please try again later or choose
another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches, etc:

http://forge.mysql.com/wiki/Contributing

For information on open issues in MySQL 5.1, please see the errata
list at

http://dev.mysql.com/doc/refman/5.1/en/open-bugs.html

The following section lists the changes in the MySQL source code since
the previous released version of MySQL 5.1. It may also be viewed
online at

http://dev.mysql.com/doc/refman/5.1/en/news-5-1-58.html

Enjoy!

===
Changes in MySQL 5.1.58 (July 5th, 2011)

   Bugs fixed:

 * InnoDB Storage Engine: If the server crashed while an XA
   transaction was prepared but not yet committed, the
   transaction could remain in the system after restart, and
   cause a subsequent shutdown to hang. (Bug #11766513, Bug
   #59641)

 * Partitioning: When executing a row-ordered retrieval index
   merge, the partitioning handler used memory from that
   allocated for the table, rather than allocated to the
   query, causing table object memory not to be freed until the
   table was closed. (Bug #11766249, Bug #59316)

 * Replication: When mysqlbinlog was invoked using
   --base64-output=decode-row and --start-position=pos, (where
   pos is a point in the binary log past the format description
   log event), a spurious error of the type shown here was
   generated:

malformed binlog: it does not contain any Format_description_log_event...

   However, since there is nothing unsafe about not printing the
   format description log event, the error has been removed for
   this case. (Bug #12354268)

 * Replication: Typographical errors appeared in the text of
   several replication error messages. (The word position was
   misspelled as postion.) (Bug #11762616, Bug #55229)

 * After the fix for Bug#11889186, MAKEDATE() arguments with a
   year part greater than  raised an assertion. (Bug
   #12403504)

 * An assertion could be raised due to a missing NULL value check
   in Item_func_round::fix_length_and_dec(). (Bug #12392636)

 * In debug builds on Solaris, an assertion was raised if a
   reverse IP lookup with gethostbyaddr_r() failed. (Bug
   #12377872)

 * MySQL did not build if configured with both --with-debug and
   --with-libedit. (Bug #12329909)

 * A problem introduced in 5.1.57 caused very old (MySQL 4.0)
   clients to be unable to connect to the server. (Bug #61222,
   Bug #12563279)

 * Using CREATE EVENT IF NOT EXISTS for an event that already
   existed and was enabled caused multiple instances of the event
   to run. (Bug #61005, Bug #12546938)

 * The incorrect max_length value for YEAR values could be used
   in temporary result tables for UNION, leading to incorrect
   results. (Bug #59343, Bug #11766270)

 * In Item_func_in::fix_length_and_dec(), a Valgrind warning for
   uninitialized values was corrected. (Bug #59270, Bug
   #11766212)

 * In ROUND() calculations, a Valgrind warning for uninitialized
   memory was corrected. (Bug #58937, Bug #11765923)

 * Valgrind warnings caused by comparing index values to an
   uninitialized field were corrected. (Bug #58705, Bug
   #11765713)

 * LOAD DATA INFILE errors could leak I/O cache memory. (Bug
   #58072, Bug #11765141)

 * For LOAD DATA INFILE, multibyte character sequences could be
   pushed onto a stack too small to accommodate them. (Bug
   #58069, Bug #11765139)

 * An embedded client would abort rather than issue an error
   message if it issued a TEE command (\T file_name) and the
   directory containing the file did not exist. This occurred
   because the wrong error handler was called. (Bug #57491, Bug
   #11764633)

 * In debug builds, Field_new_decimal::store_value() was subject
   to buffer overflows. (Bug #55436, Bug #11762799)

 * On Linux, the mysql client built using the bundled libedit did
   not read ~/.editrc. (Bug #49967, Bug #11757855)

 * The optimizer sometimes incorrectly processed 

MySQL Community Server 5.1.57 has been released

[Karen Langford]

   result. (Bug #59839, Bug #11766675)

 * An incorrect character set pointer passed to
   my_strtoll10_mb2() caused an assertion to be raised. (Bug
   #59648, Bug #11766519)

 * A missing variable initialization for Item_func_set_user_var
   objects could cause an assertion to be raised. (Bug #59527,
   Bug #11766424)

 * mysqldump did not quote database names in ALTER DATABASE
   statements in its output, which could cause an error at reload
   time for database names containing a dash. (Bug #59398, Bug
   #11766310)

 * In Item_func_month::val_str(), a Valgrind warning for a
   too-late NULL value check was corrected. (Bug #59166, Bug
   #11766126)

 * In Item::get_date, a Valgrind warning for a missing NULL value
   check was corrected. (Bug #59164, Bug #11766124)

 * In extract_date_time(), a Valgrind warning for a missing
   end-of-string check was corrected. (Bug #59151, Bug #11766112)

 * In string context, the MIN() and MAX() functions did not take
   into account the unsignedness of a BIGINT UNSIGNED argument.
   (Bug #59132, Bug #11766094)

 * In Item_func::val_decimal, a Valgrind warning for a missing
   NULL value check was corrected. (Bug #59125, Bug #11766087)

 * In Item_func_str_to_date::val_str, a Valgrind warning for an
   uninitialized variable was corrected. (Bug #58154, Bug
   #11765216)

 * The code for PROCEDURE ANALYSE() had a missing DBUG_RETURN
   statement, which could cause a server crash in debug builds.
   (Bug #58140, Bug #11765202)

 * An assertion could be raised in
   Item_func_int_val::fix_num_length_and_dec() due to overflow
   for geometry functions. (Bug #57900, Bug #11764994)

 * An assertion could be raised if a statement that required a
   name lock on a table (for example, DROP TRIGGER) executed
   concurrently with an INFORMATION_SCHEMA query that also used
   the table. (Bug #56541, Bug #11763784)

 * For a client connected using SSL, the Ssl_cipher_list status
   variable was empty and did not show the possible cipher types.
   (Bug #52596, Bug #11760210)

 * With lower_case_table_names=2, resolution of objects qualified
   by database names could fail. (Bug #50924, Bug #11758687)

 * A potential invalid memory access discovered by Valgrind was
   fixed. (Bug #48053, Bug #11756169)

 * Bitmap functions used in one thread could change bitmaps used
   by other threads, causing an assertion to be raised. (Bug
   #43152, Bug #11752069)

 * SHOW EVENTS did not always show events from the correct
   database. (Bug #41907, Bug #11751148)


Thanks,
MySQL RE Team

Karen Langford  MySQL Release Engineer
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Server 5.0.92 has been released.

[Karen Langford]

Dear MySQL users,

MySQL Server 5.0.92, a new version of the popular Open Source Database
Management System, has been released.  Please note that the active
maintenance of 5.0 has ended, and these builds are only provided
because of the fixes to security bugs as described below.

The release is now available in source and binary form for a number of
platforms from our archive download page at

http://dev.mysql.com/downloads/

Mirror service for MySQL Server 5.0 has ended.  Also, support for some
platforms with very low demand has ended.  Please bear in mind that
MySQL 5.0 now receives extended support only, and that all active
development is happening on MySQL 5.1, 5.5, and beyond. You will find
the MySQL Lifecycle policy here:

http://www.mysql.de/about/legal/lifecycle/

For your own best interest, we strongly recommend all current users of
MySQL 5.0 to upgrade to MySQL 5.1.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc:

http://forge.mysql.com/wiki/Contributing

This section documents all changes and bugfixes that have been applied
since the last MySQL Server release (5.0.91).

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-92.html

If you would like to receive more fine-grained and personalized update
alerts about fixes that are relevant to the version and features you
use, please consider subscribing to MySQL Enterprise (a commercial
MySQL offering). For more details please see

http://www.mysql.com/products/enterprise/advisors.html


Changes in MySQL 5.0.92  (7 February, 2011)

Functionality added or changed:

   * The time zone tables available at
http://dev.mysql.com/downloads/timezones.html have been
 updated. These tables can be used on systems such as
 Windows or HP-UX that do not include zoneinfo files.
 (Bug#40230:http://bugs.mysql.com/bug.php?id=40230)

Bugs fixed:

   * Security Fix: During evaluation of arguments to
 extreme-value functions (such as LEAST() and GREATEST()),
 type errors did not propagate properly, causing the
 server to crash.
 (Bug#55826:http://bugs.mysql.com/bug.php?id=55826,
 CVE-2010-3833
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3833)

   * Security Fix: The server could crash after materializing
 a derived table that required a temporary table for
 grouping.
 (Bug#55568:http://bugs.mysql.com/bug.php?id=55568,
 CVE-2010-3834
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3834)

   * Security Fix: A user-variable assignment expression that
 is evaluated in a logical expression context can be
 precalculated in a temporary table for GROUP BY. However,
 when the expression value is used after creation of the
 temporary table, it was re-evaluated, not read from the
 table and a server crash resulted.
 (Bug#55564:http://bugs.mysql.com/bug.php?id=55564,
 CVE-2010-3835
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3835)

   * Security Fix: Joins involving a table with a unique SET
 column could cause a server crash.
 (Bug#54575:http://bugs.mysql.com/bug.php?id=54575,
 CVE-2010-3677
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3677)

   * Security Fix: Pre-evaluation of LIKE predicates during
 view preparation could cause a server crash.
 (Bug#54568:http://bugs.mysql.com/bug.php?id=54568,
 CVE-2010-3836
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3836)

   * Security Fix: GROUP_CONCAT() and WITH ROLLUP together
 could cause a server crash.
 (Bug#54476:http://bugs.mysql.com/bug.php?id=54476,
  CVE-2010-3837
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3837)

   * Security Fix: Queries could cause a server crash if the
 GREATEST() or LEAST() function had a mixed list of
 numeric and LONGBLOB arguments, and the result of such a
 function was processed using an intermediate temporary
 table.
 (Bug#54461:http://bugs.mysql.com/bug.php?id=54461,
 CVE-2010-3838
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3838)

   * Security Fix: Using EXPLAIN with queries of the form
 SELECT ... UNION ... ORDER BY (SELECT ... WHERE ...)
 could cause a server crash.
 (Bug#52711:http://bugs.mysql.com/bug.php?id=52711,
  CVE-2010-3682
 (http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2010-3682)

   * InnoDB Storage Engine: Creating or dropping a table with
 1023 transactions active caused an assertion failure.
 (Bug#49238:http://bugs.mysql.com/bug.php?id=49238)

   * The make_binary_distribution target to make could fail on
 some platforms because the lines generated were too long
 for the shell.
 (Bug#54590:http://bugs.mysql.com/bug.php?id=54590)

   * A client could supply data in chunks to a prepared
 statement parameter other than of type TEXT or BLOB using
 the mysql_stmt_send_long_data() C API function (or
 COM_STMT_SEND_LONG_DATA command). This led to a crash
 

MySQL Server 5.1.55 has been released

[Karen Langford]

 the Euro
   sign (0x88). For example, converting a string containing this
   character to utf8 resulted in '?' rather than the utf8 Euro
   sign. (Bug#56639: http://bugs.mysql.com/bug.php?id=56639)

 * Some unsigned system variables could be displayed with
   negative values.
   (Bug#55794: http://bugs.mysql.com/bug.php?id=55794)

 * CREATE DATABASE and DROP DATABASE caused mysql --one-database
   to lose track of the statement-filtering context.
   (Bug#54899: http://bugs.mysql.com/bug.php?id=54899)

 * An assertion could be raised during concurrent execution of
   DROP DATABASE and REPAIR TABLE if the drop deleted a table's
   .TMD file at the same time the repair tried to read details
   from the old file that was just removed.
   A problem could also occur when DROP TABLE tried to remove all
   files belonging to a table at the same time REPAIR TABLE had
   just deleted the table's .TMD file.
   (Bug#54486: http://bugs.mysql.com/bug.php?id=54486)

 * When mysqld printed crash dump information, it incorrectly
   indicated that some valid pointers were invalid.
   (Bug#51817: http://bugs.mysql.com/bug.php?id=51817)

 * On FreeBSD, if mysqld was killed with a SIGHUP signal, it
   could corrupt InnoDB .ibd files.
   (Bug#51023: http://bugs.mysql.com/bug.php?id=51023)

 * An assertion could be raised if -1 was inserted into an
   AUTO_INCREMENT column by a statement writing more than one
   row. (Bug#50619: http://bugs.mysql.com/bug.php?id=50619)

 * If a client supplied a user name longer than the maximum 16
   characters allowed for names stored in the MySQL grant tables,
   all characters were being considered significant.
   Historically, only the first 16 characters were used to check
   for a match; this behavior was restored.
   (Bug#49752: http://bugs.mysql.com/bug.php?id=49752)

 * The my_seek() and my_tell() functions ignored the MY_WME flag
   when they returned an error, which could cause client programs
   to hang. (Bug#48451: http://bugs.mysql.com/bug.php?id=48451)

 * During assignment of values to system variables, legality
   checks on the value range occurred too late, preventing proper
   error checking.
   (Bug#43233: http://bugs.mysql.com/bug.php?id=43233)

 * On Solaris, time-related functions such as NOW() or SYSDATE()
   could return a constant value.
   (Bug#42054: http://bugs.mysql.com/bug.php?id=42054)

 * If the remote server for a FEDERATED table could not be
   accessed, queries for the INFORMATION_SCHEMA.TABLES table
   failed. (Bug#35333: http://bugs.mysql.com/bug.php?id=35333)


Thanks,
Karen Langford
Release Engineer, MySQL, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.5.8 has been released

[Karen Langford]

 overlapping memory when
   double-assigning the same variable were corrected.
   (Bug#56138: http://bugs.mysql.com/bug.php?id=56138)

 * If a STOP SLAVE statement was issued while the slave SQL
   thread was executing a statement that invoked the SLEEP()
   function, both statements hung.
   (Bug#56096: http://bugs.mysql.com/bug.php?id=56096)

 * OPTIMIZE TABLE for InnoDB tables could raise an assertion.
   (Bug#55930: http://bugs.mysql.com/bug.php?id=55930)

 * Warnings raised by a trigger were not cleared upon successful
   completion. Now warnings are cleared if the trigger completes
   successfully, per the SQL standard.
   (Bug#55850: http://bugs.mysql.com/bug.php?id=55850)

 * For CMake builds, some parts of the source were unnecessarily
   compiled twice if the embedded server was built.
   (Bug#55647: http://bugs.mysql.com/bug.php?id=55647)

 * Boolean command options caused an error if given with an
   option value and the loose- option prefix.
   (Bug#54569: http://bugs.mysql.com/bug.php?id=54569)

 * An error in a stored procedure could leave the session in a
   different default database.
   (Bug#54375: http://bugs.mysql.com/bug.php?id=54375)

 * The CMake wrapper for configure (configure.pl) did not
   handle the --with-comment option properly.
   (Bug#52275: http://bugs.mysql.com/bug.php?id=52275)

 * Grouping by a TIME_TO_SEC() function result could cause a
   server crash or incorrect results. Grouping by a function
   returning a BLOB could cause an unexpected Duplicate entry
   error and incorrect result.
   (Bug#52160: http://bugs.mysql.com/bug.php?id=52160)

 * The find_files() function used by SHOW statements performed
   redundant and unnecessary memory allocation.
   (Bug#51208: http://bugs.mysql.com/bug.php?id=51208)

 * The Windows sample option files contained values more
   appropriate for Linux.
   (Bug#50021: http://bugs.mysql.com/bug.php?id=50021)

 * A failed RENAME TABLE operation could prevent a FLUSH TABLES
   WITH READ LOCK from completing.
   (Bug#47924: http://bugs.mysql.com/bug.php?id=47924)

 * Error messages for several internal conditions that should not
   occur were changed to instruct the user to file a bug if they
   do occur. (Bug#47027: http://bugs.mysql.com/bug.php?id=47027)

 * On file systems with case insensitive file names, and
   lower_case_table_names=2, the server could crash due to a
   table definition cache inconsistency.
   (Bug#46941: http://bugs.mysql.com/bug.php?id=46941)

 * Handling of host name lettercase in GRANT statements was
   inconsistent.
   (Bug#36742: http://bugs.mysql.com/bug.php?id=36742)

 * SET NAMES utf8 COLLATE utf8_sinhala_ci did not work.
   (Bug#26474: http://bugs.mysql.com/bug.php?id=26474)

 * The utf16_bin collation uses code-point order, not
   byte-by-byte order, as described at Section 9.1.14.1, Unicode
   Character Sets. (The order was byte-by-byte in MySQL 5.5.7.)

Enjoy!

Karen Langford


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.53 has been released

[Karen Langford]

 from a binary log containing a log
   event of an invalid type caused the slave to crash.
   (Bug#38718: http://bugs.mysql.com/bug.php?id=38718)

 * Replication: When replicating the mysql.tables_priv table, the
   Grantor column was not replicated, and was thus left empty on
   the slave. (Bug#27606: http://bugs.mysql.com/bug.php?id=27606)

 * SET GLOBAL debug could cause a crash on Solaris if the server
   failed to open the trace file.
   (Bug#57274: http://bugs.mysql.com/bug.php?id=57274)

 * On file systems with case insensitive file names, and
   lower_case_table_names=2, the server could crash due to a
   table definition cache inconsistency.
   (Bug#46941: http://bugs.mysql.com/bug.php?id=46941)

 * Handling of host name lettercase in GRANT statements was
   inconsistent.
   (Bug#36742: http://bugs.mysql.com/bug.php?id=36742)

Thanks,
MySQL RE Team

Karen Langford  MySQL Release Engineer
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.52 has been released

[Karen Langford]

   than as an identifier. The resulting syntax error caused loss
   of replication.
   (Bug#55961: http://bugs.mysql.com/bug.php?id=55961)
   See also Bug#55962: http://bugs.mysql.com/bug.php?id=55962.

 * If a query specified a DATE or DATETIME value in a format
   different from '-MM-DD HH:MM:SS', a greater-than-or-equal
   (=) condition matched only greater-than values in an indexed
   TIMESTAMP column.
   (Bug#55779: http://bugs.mysql.com/bug.php?id=55779)

 * If there was an active SELECT statement, an error arising
   during trigger execution could cause a server crash.
   (Bug#55421: http://bugs.mysql.com/bug.php?id=55421)

 * With an UPDATE IGNORE statement including a subquery that was
   evaluated using a temporary table, an error transferring the
   data from the temporary was ignored, causing an assertion to
   be raised. (Bug#54543: http://bugs.mysql.com/bug.php?id=54543)

 * Row subqueries producing no rows were not handled as UNKNOWN
   values in row comparison expressions.
   (Bug#54190: http://bugs.mysql.com/bug.php?id=54190)

 * In some cases, when the left part of a NOT IN subquery
   predicate was a row and contained NULL values, the query
   result was incorrect.
   (Bug#51070: http://bugs.mysql.com/bug.php?id=51070)

 * For some queries, the optimizer produced incorrect results
   using the Index Merge access method with InnoDB tables.
   (Bug#50402: http://bugs.mysql.com/bug.php?id=50402)

 * EXPLAIN produced an incorrect rows value for queries evaluated
   using an index scan and that included LIMIT, GROUP BY, and
   ORDER BY on a computed column.
   (Bug#50394: http://bugs.mysql.com/bug.php?id=50394)

 * mysql_store_result() and mysql_use_result() are not for use
   with prepared statements and are not intended to be called
   following mysql_stmt_execute(), but failed to return an error
   when invoked that way.
   (Bug#47485: http://bugs.mysql.com/bug.php?id=47485)

 * A malformed packet sent by the server when the query cache was
   in use resulted in lost-connection errors.
   (Bug#42503: http://bugs.mysql.com/bug.php?id=42503)

 * CREATE TABLE failed if a column referred to in an index
   definition and foreign key definition was in different
   lettercases in the two definitions.
   (Bug#39932: http://bugs.mysql.com/bug.php?id=39932)


Thanks,
MySQL RE Team

Karen Langford  MySQL Release Engineer
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.51 has been released

[Karen Langford]

 results between different
   platforms. (Bug#42144: http://bugs.mysql.com/bug.php?id=42144)

 * A PKG install on Solaris put some files in incorrect
   locations. (Bug#31058: http://bugs.mysql.com/bug.php?id=31058)

Thanks,
MySQL RE Team

Karen Langford  MySQL Release Engineer
Database Group, Oracle.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.50 has been released

[Karen Langford]

/bug.php?id=54004)

 * Transactions could be incorrectly committed during recovery,
   rather than rolled back, if the server crashed and was
   restarted after performing ALTER TABLE...ADD PRIMARY KEY on an
   InnoDB table, or some other operation that involves copying
   the entire table.
   (Bug#53756: http://bugs.mysql.com/bug.php?id=53756)

 * Portability problems in SHOW STATUS could lead to incorrect
   results on some platforms.
   (Bug#53493: http://bugs.mysql.com/bug.php?id=53493)

 * Builds of MySQL generated a large number of warnings.
   (Bug#53445: http://bugs.mysql.com/bug.php?id=53445)

 * With lower_case_table_names set to a nonzero value, searches
   for table or database names in INFORMATION_SCHEMA tables could
   produce incorrect results.
   (Bug#53095: http://bugs.mysql.com/bug.php?id=53095)

 * The ABI check for MySQL failed to compile with gcc 4.5.
   (Bug#52514: http://bugs.mysql.com/bug.php?id=52514)

 * mysql_secure_installation sometimes failed to locate the mysql
   client. (Bug#52274: http://bugs.mysql.com/bug.php?id=52274)

 * Reading a ucs2 data file with LOAD DATA INFILE was subject to
   three problems. 1) Incorrect parsing of the file as ucs2 data,
   resulting in incorrect length of the parsed string. This is
   fixed by truncating the invalid trailing bytes (incomplete
   multibyte characters) when reading from the file. 2) Reads
   from a proper ucs2 file did not recognize newline characters.
   This is fixed by first checking whether a byte is a newline
   (or any other special character) before reading it as a part
   of a multibyte character. 3) When using user variables to hold
   column data, the character set of the user variable was set
   incorrectly to the database charset. This is fixed by setting
   it to the character set specified in the LOAD DATA INFILE
   statement, if any.
   (Bug#51876: http://bugs.mysql.com/bug.php?id=51876)

 * Searches in INFORMATION_SCHEMA tables for rows matching a
   nonexistent database produced an error instead of an empty
   query result.
   (Bug#49542: http://bugs.mysql.com/bug.php?id=49542)

 * On FreeBSD, memory mapping for MERGE tables could fail if
   underlying tables were empty.
   (Bug#47139: http://bugs.mysql.com/bug.php?id=47139)

 * The my_like_range_xxx() functions returned badly formed
   maximum strings for Asian character sets, which caused
   problems for storage engines.
   (Bug#45012: http://bugs.mysql.com/bug.php?id=45012)

 * A debugging assertion could be raised after a write failure to
   a closed socket.
   (Bug#42496: http://bugs.mysql.com/bug.php?id=42496)

 * An assertion failure occurred within yaSSL for very long keys.
   (Bug#29784: http://bugs.mysql.com/bug.php?id=29784)
   See also Bug#53463: http://bugs.mysql.com/bug.php?id=53463.


Thanks,
MySQL RE Team

Karen Langford  MySQL Release Engineer
Database Group, Oracle.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.49 has been released

[Karen Langford]

 is not already running when the RPM upgrade occurs, the
   server is not started at the end of the upgrade. The boot
   scripts for MySQL are installed in the appropriate directories
   in /etc, so the MySQL server will be restarted automatically
   at the next machine reboot.
   (Bug#27072: http://bugs.mysql.com/bug.php?id=27072)


Thanks,
MySQL RE Team

Karen Langford  MySQL Release Engineer
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.48 has been released

[Karen Langford]

 completed.
   (Bug#49522: http://bugs.mysql.com/bug.php?id=49522)
   See also Bug#29288: http://bugs.mysql.com/bug.php?id=29288.

 * Replication: Reading from a table that used a self-logging
   storage engine and updating a table that used a transactional
   engine (such as InnoDB) generated changes that were written to
   the binary log using statement format which could make slaves
   diverge. However, when using mixed logging format, such
   changes should be written to the binary log using row format.
   (This issue did not occur when reading from tables using a
   self-logging engine and updating MyISAM tables, as this was
   already handled by checking for combinations of
   non-transactional and transactional engines.) Now such
   statements are classified as unsafe, and in mixed mode, cause
   a switch to row-based logging.
   (Bug#49019: http://bugs.mysql.com/bug.php?id=49019)

 * Valgrind warnings resulting from passing incomplete DATETIME
   values to the TIMESTAMP() function were corrected.
   (Bug#53942: http://bugs.mysql.com/bug.php?id=53942)

 * Builds of the embedded mysqld would fail due to a missing
   element of the struct NET.
   (Bug#53908: http://bugs.mysql.com/bug.php?id=53908,
   Bug#53912: http://bugs.mysql.com/bug.php?id=53912)

 * UPDATE on an InnoDB table modifying the same index that was
   used to satisfy the WHERE condition could trigger a debug
   assertion under some circumstances.
   (Bug#53830: http://bugs.mysql.com/bug.php?id=53830)

 * For single-table DELETE statements that used quick select and
   index scan simultaneously caused a server crash or assertion
   failure. (Bug#53450: http://bugs.mysql.com/bug.php?id=53450)

 * Incorrect results could be returned for LEFT JOIN of InnoDB
   tables with an impossible WHERE condition.
   (Bug#53334: http://bugs.mysql.com/bug.php?id=53334)

 * Fixed a checksum error reported for compressed tables when the
   --innodb_checksums option is enabled.
   (Bug#53248: http://bugs.mysql.com/bug.php?id=53248)

 * Corrected the handling of the setting
   innodb_change_buffering=default. (The appropriate default
   value is different between MySQL 5.1 and 5.5.)
   (Bug#53165: http://bugs.mysql.com/bug.php?id=53165)

 * mysqldump and SELECT ... INTO OUTFILE truncated long BLOB and
   TEXT values to 766 bytes.
   (Bug#53088: http://bugs.mysql.com/bug.php?id=53088)

 * In the debug version of the server, the FreeState() function
   could in some circumstances be called twice, leading to an
   assertion failure.
   (Bug#52884: http://bugs.mysql.com/bug.php?id=52884)

 * Aggregate functions could incorrectly return NULL in outer
   join queries.
   (Bug#52051: http://bugs.mysql.com/bug.php?id=52051)

 * The Loose Index Scan optimization method assumed that it could
   depend on the partitioning engine to maintain interval
   endpoint information, as if it were a storage engine.
   (Bug#50939: http://bugs.mysql.com/bug.php?id=50939)

 * Calculation of intervals for Event Scheduler events was not
   portable. (Bug#50087: http://bugs.mysql.com/bug.php?id=50087)

 * Selecting from INFORMATION_SCHEMA.ROUTINES or
   INFORMATION_SCHEMA.PARAMETERS
   (http://dev.mysql.com/doc/refman/5.5/en/parameters-table.html)
   resulted in a memory leak.
   (Bug#48729: http://bugs.mysql.com/bug.php?id=48729)

 * When the transaction isolation level was REPEATABLE READ and
   binary logging used statement or mixed format, SELECT
   statements with subqueries referencing InnoDB tables
   unnecessarily acquired shared locks on rows in these tables.
   (Bug#46947: http://bugs.mysql.com/bug.php?id=46947)

 * Using an initial command with mysql_options(...,
   MYSQL_INIT_COMMAND, ...) that generated multiple result sets
   (such as a stored procedure or a multi-statement command) left
   the connection unusable.
   (Bug#42373: http://bugs.mysql.com/bug.php?id=42373)

 * If a crash occurs while creating an index using the InnoDB
   Fast Index Creation mechanism, the partially created index
   is dropped during the crash recovery processing when the
   database is restarted.

Thanks,
MySQL RE Team

Karen Langford, Hery Ramilison  MySQL Release Engineers
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.46 has been released

[Karen Langford]

' statement where the string was
   longer than the maximum length of a column name, due to the
   fact that this text was also used as an alias (in the AS
   clause).
   Because not all names retrieved from arbitrary SELECT
   statements can be used as view column names due to length and
   format restrictions, the server now checks the conformity of
   automatically generated column names and rewrites according to
   a predefined format any names that are not acceptable as view
   column names before storing the final view definition on disk.
   In such cases, the name is now rewritten as Name_exp_pos,
   where pos is the position of the column. To avoid this
   conversion scheme, define explicit, valid names for view
   columns using the column_list clause of the CREATE VIEW
   statement.
   As part of this fix, aliases are now generated only for
   top-level statements.
   (Bug#40277: http://bugs.mysql.com/bug.php?id=40277)

 * While looking for the shortest index for a covering index
   scan, the optimizer ignored that a clustered primary key read
   the entire table.
   (Bug#39653: http://bugs.mysql.com/bug.php?id=39653)

 * mysqlbinlog had a memory leak in its option-processing code.
   (Bug#38468: http://bugs.mysql.com/bug.php?id=38468)

 * The test for readline during configuration failed when trying
   to build MySQL in a directory other than the source tree root.
   (Bug#35250: http://bugs.mysql.com/bug.php?id=35250)

Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Oracle.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.46 has been released

[Karen Langford]

' statement where the string was
   longer than the maximum length of a column name, due to the
   fact that this text was also used as an alias (in the AS
   clause).
   Because not all names retrieved from arbitrary SELECT
   statements can be used as view column names due to length and
   format restrictions, the server now checks the conformity of
   automatically generated column names and rewrites according to
   a predefined format any names that are not acceptable as view
   column names before storing the final view definition on disk.
   In such cases, the name is now rewritten as Name_exp_pos,
   where pos is the position of the column. To avoid this
   conversion scheme, define explicit, valid names for view
   columns using the column_list clause of the CREATE VIEW
   statement.
   As part of this fix, aliases are now generated only for
   top-level statements.
   (Bug#40277: http://bugs.mysql.com/bug.php?id=40277)

 * While looking for the shortest index for a covering index
   scan, the optimizer ignored that a clustered primary key read
   the entire table.
   (Bug#39653: http://bugs.mysql.com/bug.php?id=39653)

 * mysqlbinlog had a memory leak in its option-processing code.
   (Bug#38468: http://bugs.mysql.com/bug.php?id=38468)

 * The test for readline during configuration failed when trying
   to build MySQL in a directory other than the source tree root.
   (Bug#35250: http://bugs.mysql.com/bug.php?id=35250)

Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Oracle.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.45 has been released

[Karen Langford]

 execute an SQL statement on a
   connection after doing a send command, unless you do a reap
   first. This was previously accepted but could produce
   unpredictable results.
   (Bug#49269: http://bugs.mysql.com/bug.php?id=49269)

 * For debug builds on Windows, warnings about incorrect use of
   debugging directives were written to the error log. The
   directives were rewritten to eliminate these messages.
   (Bug#49025: http://bugs.mysql.com/bug.php?id=49025)

 * Building MySQL on Fedora Core 12 64-bit failed, due to errors
   in comp_err.
   (Bug#48864: http://bugs.mysql.com/bug.php?id=48864)

 * An ARZ file missing from the database directory caused the
   server to crash.
   (Bug#48757: http://bugs.mysql.com/bug.php?id=48757)

 * Slow CALL statements were not always logged to the slow query
   log because execution time for multiple-statement stored
   procedures was assessed incorrectly.
   (Bug#47905: http://bugs.mysql.com/bug.php?id=47905)

 * Failure to open a view with a nonexistent DEFINER was
   improperly handled and the server would crash later attempting
   to lock the view.
   (Bug#47734: http://bugs.mysql.com/bug.php?id=47734)

 * If EXPLAIN encountered an error in the query, a memory leak
   occurred. (Bug#45989: http://bugs.mysql.com/bug.php?id=45989)

 * Grouping by a subquery in a query with a DISTINCT aggregate
   function led to incorrect and unordered grouping values.
   (Bug#45640: http://bugs.mysql.com/bug.php?id=45640)

 * Propagation of a large unsigned numeric constant in WHERE
   expressions could lead to incorrect results. This also
   affected EXPLAIN EXTENDED, which printed incorrect numeric
   constants in such transformed WHERE expressions.
   (Bug#45360: http://bugs.mysql.com/bug.php?id=45360)

 * Valgrind warnings about uninitialized variables in optimizer
   code were silenced.
   (Bug#45195: http://bugs.mysql.com/bug.php?id=45195)

 * flush_cache_records() did not correctly check for errors that
   should cause statement execution to stop, leading to a server
   crash. (Bug#39022: http://bugs.mysql.com/bug.php?id=39022)

 * When building MySQL when using a different target directory
   (for example using the VPATH environment variable), the build
   of the embedded readline component would fail.
   (Bug#35250: http://bugs.mysql.com/bug.php?id=35250)

 * INSERT INTO ... VALUES(DEFAULT) failed to insert the correct
   value for ENUM columns. For MyISAM tables, an empty value was
   inserted. For CSV tables, the table became corrupt.
   (Bug#33717: http://bugs.mysql.com/bug.php?id=33717)

Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.44 has been released

[Karen Langford]

 correctly.
   (Bug#47418: http://bugs.mysql.com/bug.php?id=47418)
   See also Bug#47442: http://bugs.mysql.com/bug.php?id=47442.

 * Replication: Due to a change in the size of event
   representations in the binary log, when replicating from a
   MySQL 4.1 master to a slave running MySQL 5.0.60 or later, the
   START SLAVE UNTIL statement did not function correctly,
   stopping at the wrong position in the log. Now the slave
   detects that the master is using the older version of the
   binary log format, and corrects for the difference in event
   size, so that the slave stops in the correct position.
   (Bug#47142: http://bugs.mysql.com/bug.php?id=47142)

 * The SSL certificates in the test suite were about to expire.
   They have been updated with expiration dates in the year 2015.
   (Bug#50642: http://bugs.mysql.com/bug.php?id=50642)

 * The printstack function does not exist on Solaris 8 or
   earlier, which would lead to a compilation failure.
   (Bug#50409: http://bugs.mysql.com/bug.php?id=50409)

 * A user could see tables in INFORMATION_SCHEMA.TABLES without
   appropriate privileges for them.
   (Bug#50276: http://bugs.mysql.com/bug.php?id=50276)

 * Debug output for join structures was garbled.
   (Bug#50271: http://bugs.mysql.com/bug.php?id=50271)

 * The filesort sorting method applied to a CHAR(0) column could
   lead to a server crash.
   (Bug#49897: http://bugs.mysql.com/bug.php?id=49897)

 * sql_buffer_result had an effect on non-SELECT statements,
   contrary to the documentation.
   (Bug#49552: http://bugs.mysql.com/bug.php?id=49552)

 * In some cases a subquery need not be evaluated because it
   returns only aggregate values that can be calculated from
   table metadata. This sometimes was not handled by the
   enclosing subquery, resulting in a server crash.
   (Bug#49512: http://bugs.mysql.com/bug.php?id=49512)

 * The method for comparing INFORMATION_SCHEMA names and database
   names was nonoptimal and an improvement was made: When the
   database name length is already known, a length check is made
   first and content comparison skipped if the lengths are
   unequal. (Bug#49501: http://bugs.mysql.com/bug.php?id=49501)

 * The MD5() and SHA1() functions had excessive overhead for
   short strings.
   (Bug#49491: http://bugs.mysql.com/bug.php?id=49491)

 * Mixing full-text searches and row expressions caused a crash.
   (Bug#49445: http://bugs.mysql.com/bug.php?id=49445)

 * Creating or dropping a table with 1023 transactions active
   caused an assertion failure.
   (Bug#49238: http://bugs.mysql.com/bug.php?id=49238)

 * mysql-test-run.pl now recognizes the MTR_TESTCASE_TIMEOUT,
   MTR_SUITE_TIMEOUT, MTR_SHUTDOWN_TIMEOUT, and MTR_START_TIMEOUT
   environment variables. If they are set, their values are used
   to set the --testcase-timeout, --suite-timeout,
   --shutdown-timeout, and --start-timeout options, respectively.
   (Bug#49210: http://bugs.mysql.com/bug.php?id=49210)

Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.




--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.43 has been released

[Karen Langford]

/bug.php?id=48983)

* On Fedora 12, strmov() did not guarantee correct operation for
  overlapping source and destination buffer. Calls were fixed to
  use an overlap-safe version instead.
  (Bug#48866: http://bugs.mysql.com/bug.php?id=48866)

* Incomplete reset of internal TABLE structures could cause a
  crash with eq_ref table access in subqueries.
  (Bug#48709: http://bugs.mysql.com/bug.php?id=48709)

* Re-execution of a prepared statement could cause a server
  crash. (Bug#48508: http://bugs.mysql.com/bug.php?id=48508)

* The error message for ER_UPDATE_INFO was subject to buffer
  overflow or truncation.
  (Bug#48500: http://bugs.mysql.com/bug.php?id=48500)

* SHOW BINLOG EVENTS could fail with a error: Wrong offset or
  I/O error. (Bug#48357: http://bugs.mysql.com/bug.php?id=48357)

* Valgrind warnings related to binary logging of LOAD DATA
  INFILE statements were corrected.
  (Bug#48340: http://bugs.mysql.com/bug.php?id=48340)

* An aliasing violation in the C API could lead to a crash.
  (Bug#48284: http://bugs.mysql.com/bug.php?id=48284)

* The InnoDB Monitor could fail to print diagnostic information
  after a long lock wait.
  (Bug#47814: http://bugs.mysql.com/bug.php?id=47814)

* Queries containing GROUP BY ... WITH ROLLUP that did not use
  indexes could return incorrect results.
  (Bug#47650: http://bugs.mysql.com/bug.php?id=47650)

* If an invocation of a stored procedure failed in the
  table-open stage, subsequent invocations that did not fail in
  that stage could cause a crash.
  (Bug#47649: http://bugs.mysql.com/bug.php?id=47649)

* On Solaris, no stack trace was printed to the error log after
  a crash. (Bug#47391: http://bugs.mysql.com/bug.php?id=47391)

* The first execution of STOP SLAVE UNTIL stopped too early.
  (Bug#47210: http://bugs.mysql.com/bug.php?id=47210)

* When the mysql client was invoked with the --vertical option,
  it ignored the --skip-column-names option.
  (Bug#47147: http://bugs.mysql.com/bug.php?id=47147)

* It was possible for init_available_charsets() not to
  initialize correctly.
  (Bug#45058: http://bugs.mysql.com/bug.php?id=45058)

* Comparison with NULL values sometimes did not produce a
  correct result.
  (Bug#42760: http://bugs.mysql.com/bug.php?id=42760)

* Crash recovery did not work for InnoDB temporary tables.
  (Bug#41609: http://bugs.mysql.com/bug.php?id=41609)

* The mysql_upgrade command would create three additional fields
  to the mysql.proc table (character_set_client,
  collation_connection, and db_collation), but did not populate
  the fields with correct values. This would lead to error
  messages reported during stored procedure execution.
  (Bug#41569: http://bugs.mysql.com/bug.php?id=41569)

* When compressed MyISAM files were opened, they were always
  memory mapped, sometimes causing memory-swapping problems. To
  deal with this, a new system variable, myisam_mmap_size, was
  added to limit the amount of memory used for memory mapping of
  MyISAM files.
  (Bug#37408: http://bugs.mysql.com/bug.php?id=37408)

* A race condition on the privilege hash tables allowed one
  thread to try to delete elements that had already been deleted
  by another thread. A consequence was that SET PASSWORD or
  FLUSH PRIVILEGES could cause a crash.
  (Bug#35589: http://bugs.mysql.com/bug.php?id=35589,
  Bug#35591: http://bugs.mysql.com/bug.php?id=35591)

* ALTER TABLE with both DROP COLUMN and ADD COLUMN clauses could
  crash or lock up the server.
  (Bug#31145: http://bugs.mysql.com/bug.php?id=31145)

Thanks,
MySQL RE Team

Karen Langford, Hery Ramilison, MySQL Release Engineers
Database Group, Sun Microsystem Inc.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.0.89 has been released

[Karen Langford]

Dear MySQL users,

MySQL Community Server 5.0.89, a new version of the popular Open Source
Database Management System, has been released. This Community release 
shares the
version number with its MySQL Enterprise Server counterpart. Please note 
this is

the last release of 5.0 before it exits active maintenance.

The release is now available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

and mirror sites.  Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc.:

http://forge.mysql.com/wiki/Contributing

This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.88).

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-89.html

If you would like to receive more fine-grained and personalized
update alerts about fixes that are relevant to the version and
features you use, please consider subscribing to MySQL Enterprise
(a commercial MySQL offering). For more details please see
http://www.mysql.com/products/enterprise/advisors.html.

Enjoy!

-- 


C.1.1. Changes in MySQL 5.0.89

Bugs fixed:

  * Privileges for stored routines were ignored for mixed-case
routine names.
(Bug#48872: http://bugs.mysql.com/bug.php?id=48872)
See also Bug#41049: http://bugs.mysql.com/bug.php?id=41049.

  * Building MySQL on Fedora Core 12 64-bit would fail due to errors in
comp_err. (Bug#48864: http://bugs.mysql.com/bug.php?id=48864)

  * DISTINCT was ignored for queries with GROUP BY WITH ROLLUP and
only const tables.
(Bug#48475: http://bugs.mysql.com/bug.php?id=48475)

  * Loose index scan was inappropriately chosen for some WHERE
conditions.
(Bug#48472: http://bugs.mysql.com/bug.php?id=48472)

  * A bad typecast could cause query execution to allocate large
amounts of memory.
(Bug#48458: http://bugs.mysql.com/bug.php?id=48458)

  * When running mysql_secure_installation, the command would fail
if the root password contained multiple spaces, \, # or quote
characters.
(Bug#48031: http://bugs.mysql.com/bug.php?id=48031)

  * Output from mysql --html did not encode the , , or 
characters.
(Bug#27884: http://bugs.mysql.com/bug.php?id=27884)


Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.0.88 has been released

[Karen Langford]

Dear MySQL users,

MySQL Community Server 5.0.88, a new version of the popular Open Source
Database Management System, has been released. This and future releases
in the MySQL Community Server 5.0 series share version numbers with
their MySQL Enterprise Server counterparts.

The release is now available in source and binary form for a number of
platforms from our download pages at

http://dev.mysql.com/downloads/

and mirror sites.  Note that not all mirror sites may be up to date at
this point in time, so if you can't find this version on some mirror,
please try again later or choose another download site.

We welcome and appreciate your feedback, bug reports, bug fixes,
patches etc.:

http://forge.mysql.com/wiki/Contributing

This section documents all changes and bugfixes that have been
applied since the last MySQL Community Server release (5.0.87).

http://dev.mysql.com/doc/refman/5.0/en/news-5-0-88.html

If you would like to receive more fine-grained and personalized
update alerts about fixes that are relevant to the version and
features you use, please consider subscribing to MySQL Enterprise
(a commercial MySQL offering). For more details please see
http://www.mysql.com/products/enterprise/advisors.html.

Enjoy!

-- 




C.1.1. Changes in MySQL 5.0.88


 Bugs fixed:

   * Security Fix: MySQL clients linked against OpenSSL did not
 check server certificates presented by a server linked against
 yaSSL. (Bug#47320: http://bugs.mysql.com/47320)

   * MySQL Cluster: When a data node had written its GCI marker to
 the first page of a megabyte, and that node was later killed
 during restart after having processed that page (marker) but
 before completing a LCP, the data node could fail with
 filesystem errors. (Bug#44952: http://bugs.mysql.com/44952)
 See also Bug#42564: http://bugs.mysql.com/42564,
 Bug#44291: http://bugs.mysql.com/44291.

   * Replication: When a session was closed on the master,
 temporary tables belonging to that session were logged with
 the wrong database names when either of the following
 conditions was true:

   1. The length of the name of the database to which the
  temporary table belonged was greater than the length of
  the current database name.

   2. The current database was not set.
 (Bug#48216: http://bugs.mysql.com/48216)
 See also Bug#46861: http://bugs.mysql.com/46861,
 Bug#48297: http://bugs.mysql.com/48297.

   * Error handling was missing for SELECT statements containing
 subqueries in the WHERE clause and that assigned a SELECT
 result to a user variable. The server could crash as a result.
 (Bug#48291: http://bugs.mysql.com/48291)

   * An assertion could fail if the optimizer used a SPATIAL index.
 (Bug#48258: http://bugs.mysql.com/48258,
 Bug#47019: http://bugs.mysql.com/47019)

   * mysys/mf_keycache.c requires threading, but no test was made
 for thread support. (Bug#47923: http://bugs.mysql.com/47923)

   * If the first argument to GeomFromWKB() function was a geometry
 value, the function just returned its value. However, it
 failed to preserve the argument's null_value flag, which
 caused an unexpected NULL value to be returned to the caller,
 resulting in a server crash.
 (Bug#47780: http://bugs.mysql.com/47780)

   * The GPL and commercial license headers had different sizes, so
 that error log, backtrace, core dump, and cluster trace file
 line numbers could be off by one if they were not checked
 against the version of the source used for the build. (For
 example, checking a GPL build backtrace against commercial
 sources.) (Bug#46216: http://bugs.mysql.com/46216)

   * During the build of the Red Hat IA64 MySQL server RPM, the
 system library link order was incorrect. This made the
 resulting Red Hat IA64 RPM depend on
 libc.so.6.1(GLIBC_PRIVATE)(64bit), thus preventing
 installation of the package.
 (Bug#45706: http://bugs.mysql.com/45706)

   * Failure to treat BIT values as unsigned could lead to
 unpredictable results.
 (Bug#42803: http://bugs.mysql.com/42803)


Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.41 has been released

[Karen Langford]

 if the query was waiting for a lock.
 (Bug#28141: http://bugs.mysql.com/28141)


Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.



--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.0.87 has been released

[Karen Langford]

 to
 replication failure because statements were written in the
 wrong order to the binary log.
 (Bug#42108: http://bugs.mysql.com/42108)

   * myisamchk performed parameter value casting at startup that
 generated unnecessary warning messages.
 (Bug#33785: http://bugs.mysql.com/33785)

   * When building MySQL on Windows from source, the
 WITH_BERKELEY_STORAGE_ENGINE option would fail to configure
 BDB support correctly.
 (Bug#27693: http://bugs.mysql.com/27693)

   * Changing the size of a key buffer that is under heavy use
 could cause a server crash. The fix partially removes the
 limitation that LOAD INDEX INTO CACHE fails unless all indexes
 in a table have the same block size. Now the statement fails
 only if IGNORE LEAVES is specified.
 (Bug#17332: http://bugs.mysql.com/17332)


Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.1.40 has been released

[Karen Langford]

 ... WHERE ... IN (NULL, ...) was executed using a full
 table scan, even if the same query without the NULL used an
 efficient range scan. (Bug#44139: http://bugs.mysql.com/44139)
 See also Bug#18360: http://bugs.mysql.com/18360.

   * LOAD DATA INFILE statements were written to the binary log in
 such a way that parsing problems could occur when re-executing
 the statement from the log.
 (Bug#43746: http://bugs.mysql.com/43746)

   * Selecting from the process list in the embedded server caused
 a crash. (Bug#43733: http://bugs.mysql.com/43733)

   * Attempts to enable large_pages with a shared memory segment
 larger than 4GB caused a server crash.
 (Bug#43606: http://bugs.mysql.com/43606)

   * A test for stack growth failed on some platforms, leading to
 server crashes. (Bug#42213: http://bugs.mysql.com/42213)

   * The mysql-stress-test.pl test script was missing from the
 noinstall packages on Windows.
 (Bug#41546: http://bugs.mysql.com/41546)

   * Privileges for SHOW CREATE VIEW were not being checked
 correctly. (Bug#35996: http://bugs.mysql.com/35996)

   * Different invocations of CHECKSUM TABLE could return different
 results for a table containing columns with spatial data
 types. (Bug#35570: http://bugs.mysql.com/35570)

   * myisamchk performed parameter value casting at startup that
 generated unnecessary warning messages.
 (Bug#33785: http://bugs.mysql.com/33785)

   * When building MySQL on Windows from source, the
 WITH_BERKELEY_STORAGE_ENGINE option would fail to configure
 BDB support correctly.
 (Bug#27693: http://bugs.mysql.com/27693)


Thanks,
MySQL RE Team

Hery Ramilison, Karen Langford, MySQL Release Engineers
Database Group, Sun Microsystem Inc.





--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org

MySQL Community Server 5.0.82 has been released

[Karen Langford]

 that enabled support for * filename pattern expansion.
   (Bug#29248: http://bugs.mysql.com/29248)

 * COMMIT did not delete savepoints if there were no changes in
   the transaction. (Bug#26288: http://bugs.mysql.com/26288)

 * Several memory allocation functions were not being checked for
   out-of-memory return values.
  (Bug#25058: http://bugs.mysql.com/25058)

Thanks,
Karen


Karen Langford, MySQL Release Engineer
Database Group, Sun Microsystem Inc.


--
MySQL General Mailing List
For list archives: http://lists.mysql.com/mysql
To unsubscribe:http://lists.mysql.com/mysql?unsub=arch...@jab.org