I Use This!
High Activity

News

Analyzed about 4 hours ago. based on code collected about 8 hours ago.
Posted 14 days ago by Daniel Horecki
Dear MySQL users, The MySQL developer tools team announces 6.3.9 as our GA release for MySQL Workbench 6.3. For the full list of changes in this revision, visit http://dev.mysql.com/doc/relnotes/workbench/en/changes-6-3.html For discussion ... [More] , join the MySQL Workbench Forums: http://forums.mysql.com/index.php?152 Download MySQL Workbench 6.3.9 GA now, for Windows, Mac OS X 10.10+, Oracle Linux 7, Fedora 24 and 25, Ubuntu 16.04 and 16.10 or sources, from: http://dev.mysql.com/downloads/tools/workbench/ Enjoy! Changes in MySQL Workbench 6.3.9 (2017-02-07, General Availability) Functionality Added or Changed * Support was added for many MySQL 8.0 features. Note that configuration-file support for MySQL 8.0 is not available and a warning banner is displayed during attempted use. (Bug #24908593, Bug #83422) * With MySQL 5.7, several new instruments were added to the performance section including the following for Memory Usage: Total Memory, Top Memory by Event, Top Memory by User, Top Memory by Host, Top Memory by Thread, User Resource Usage, and the following for User Resource Usage: Overview, I/O Statistics, and Statement Statistics. (Bug #21491775) * With MySQL 5.7, GTID_MODE can now be set online. (Bug #20712931) * Workbench is now aware of the innodb_optimize_point_storage option that was added in MySQL Server 5.7.5, and later removed in MySQL Server 5.7.6. Note that MySQL Server 5.7.9 was the first 5.7 GA release. (Bug #20661496) * Mroonga storage engine support is now available for tables. (Bug #20058280, Bug #74367) * A new DDL tab was added to show the complete create statement of a table or view. Click the table inspector (info) button next to the table or view in the Schemas Navigator to display the new information. (Bug #19889537, Bug #74554) * Dropped support for DBDesigner 4. * Dropped Fabric support. * Dropped support for MySQL 5.1. Minimum version is now MySQL 5.5. * Changed to C++11. * Changed to GTK 3 on Linux. * OS X: Version 10.7 (Lion) and 10.8 (Mountain Lion) support was dropped. Now supporting 10.9 (Mavericks), 10.10 (Yosemite), 10.11 (El Capitan), and 10.12 (Sierra). * Windows: Zip packages and 32-bit binaries are no longer published. The .NET Framework version 4.5 is now required. * Linux: Fedora 23 support dropped and Fedora 25 support added. Oracle Linux 6 support was dropped. * The option to specify an alternative application data directory, instead of the default location, was added. * The JSON editor was improved with better parsing and error checking. * A new Log Level preference (under Others) was added to alter the log verbosity level. As before, this can still be set by passing in the log-level (http://dev.mysql.com/doc/workbench/en/wb-command-line-op tions.html) command-line argument into Workbench at runtime, and doing so overrides the Log Level setting. * The bundled sakila_full.mwb model now uses a dedicated 5.7 version to allow for 5.7 specific features, regardless of the version setting in the preferences. * Full MySQL 5.7 language support was added, which affects grammar, syntax highlighting, preferences, behavior, and more. * The Home screen was modified: the connections, models, and starters were split into individual pages. Bugs Fixed * With multiple tabs open in the SQL Editor, using the context-sensitive menu to close all other tabs caused MySQL Workbench to exit unexpectedly. (Bug #25466086, Bug #84643) * Objects sorted in the schema inspector and then selected for an operation, such as Drop Table, generated a statement for the wrong object. (Bug #25464011, Bug #84697) * MySQL Workbench supports the option to require a CA certificate or identity validation. (Bug #25408639) * If a full backup added warning messages to the backup log file, then running an incremental backup later failed. (Bug #25315796) * No JSON tab appeared for the Open Value in Editor command if the field contained an empty array. (Bug #25222455, Bug #84106) * Schema names were not escaped properly in resulting DROP TRIGGER statements when a trigger was created or edited. (Bug #25036458, Bug #83655) * In some cases, executing a query caused MySQL Workbench to become unresponsive when the host was macOS Sierra. (Bug #25036263, Bug #83658) * Having a single quotation mark (') in the text field of a table caused the MySQL Schema Transfer wizard to fail. (Bug #24978403, Bug #83616) * Simple and complex queries executed from SQL Editor failed to complete and return control to MySQL Workbench. This behavior was observed for both local and remote queries and was often intermittent. (Bug #24977018, Bug #82951) * Deleting rows while connected to a remote server caused the connection to fail and for MySQL Workbench to exit unexpectedly. (Bug #24947899, Bug #81019) * The Selected schema drop-down list in the New Schema Privilege Definition dialog failed to display newly added schema names unless MySQL Workbench was restarted. (Bug #24798254, Bug #83111) * The bundled OpenSSL library was upgraded to version 1.0.2J. (Bug #24753390) * Tooltips failed to operate properly in the Visual Explain panel. (Bug #24577687, Bug #82816) * Deleting selected rows from the Result Grid caused MySQL Workbench to become unresponsive. (Bug #24411733, Bug #82466) * Connecting to the server resulted in the following exception: Parameter is not valid. (Bug #24394987) * Queries returning more than 1000 rows on an SSH connection to AWS failed and caused MySQL Workbench to become unresponsive. (Bug #24330588, Bug #82291) * Adding a password with the Store in Vault option caused Workbench to fail and exit. (Bug #23987798, Bug #82190) * Opening a saved .mwb model file with MySQL Workbench generated the following error intermittently: Error unserializing GRT data string too long. The same file, when opened directly from the file system, started MySQL Workbench and displayed the model correctly. (Bug #23857478, Bug #80017) * Query statements executed from the SQL Editor did not remain selected when the focus returned to the query area. (Bug #23760790, Bug #79580) * The schema navigator incorrectly opened a previously viewed database, instead of the one selected, after the schema filter in the Navigator panel was used to find and list multiple databases. (Bug #23760745, Bug #71699) * Selecting TCP/IP over SSH for existing or new connections caused MySQL Workbench to fail and exit. (Bug #23743373, Bug #82113) * Changes made with the Options File editor were committed to my.cnf correctly, but also generated an error. (Bug #23741731, Bug #82102) * Stored procedures containing valid CASE statements reported syntax errors when created or edited. (Bug #23617646, Bug #81932) * Graphs in the performance dashboard reported negative values when the server instance was stopped and restarted during the analysis. (Bug #23103677, Bug #81067) * The Migration Wizard successfully migrated the schema, but failed to migrate the data, when the data source was SQL Anywhere 16 using ODBC. (Bug #22987681, Bug #79140) * Selecting too many tables when attempting to reverse engineer an EER diagram caused MySQL Workbench to fail and exit. This fix sets the permitted threshold to 1000 objects and displays a warning message when the number of objects exceeds the threshold. (Bug #22828056, Bug #80516) * The import operation failed to import valid CSV files. (Bug #22817059, Bug #80472) * New connections configured with the Standard TCP/IP over SSH connection method failed and caused MySQL Workbench to become unresponsive or to exit. (Bug #22728573, Bug #80359) * EER diagram tables were locked to a fixed location in the window for some .mwb files. This fix enables users to unlock the tables within the diagram and to persist those changes by first changing the size of the diagram (click Model, Diagram Properties and Size) and then saving the file. (Bug #22722596, Bug #71533) * Performance reports generated by the Export button did not enclose in quotes and escape any string values in the CSV file, making it difficult to read the output when the strings contained commas. (Bug #22700858) * Check for Updates from the Help menu failed to detect new releases. (Bug #22578656, Bug #80074) * The Filter Rows value set in the Result Grid of a query was not reapplied when the query was changed or refreshed. (Bug #22566018, Bug #80050) * When running large queries over an SSH tunnel, MySQL Workbench became unresponsive. (Bug #22494755, Bug #79840) * The Export Data operation emitted an unhandled exception when the user connecting to the server lacked privileges on the mysql schema, but had full privileges on the database identified by the operation. (Bug #22478388, Bug #79807) * Adding or editing fields in the Table Templates window for a user-defined template caused MySQL Workbench to fail and exit. (Bug #22449752, Bug #79721) * Data exported from the Inserts tab of a table in an EER diagram generated invalid JSON syntax. (Bug #22381735, Bug #79673) * Some GRANT statements were parsed incorrectly. (Bug #22370783) * The Audit Inspector failed to initialize in MySQL Workbench when the locations of the audit log file and data directory were different. (Bug #22277384) * GEOMETRY table data failed to export properly into CSV file format and failed to export at all into JSON file format (with an error). (Bug #22269646) * Stopping a query before it finished executing often caused MySQL Workbench to stop working. (Bug #22071120, Bug #78881) * The placeholder row (last row of the Result Grid with NULL values) was hidden when new rows were inserted and applied. (Bug #22065173, Bug #78294) * Saving a reverse-engineered model caused MySQL Workbench to fail and exit. (Bug #21980722, Bug #78357) * The cost and data process information added to "EXPLAIN JSON" in MySQL Server 5.7.2 can now be viewed in Workbench. (Bug #21848024) * The autocomplete feature did not offer suggestions as expected. The CTRL+SPACEBAR keyboard shortcut can be used to activate this feature. (Bug #21685267, Bug #78185) * Some help text was hidden from the Schema Editor in the EER Diagram. (Bug #21630661, Bug #78021) * When MySQL Workbench performed a copy-back restore operation, it reported incorrectly to the mysqlbackup log that a copy-back-and-apply-log operation was performed. (Bug #21496475) * The require_secure_transport system variable that was added in MySQL Server 5.7.8 is now supported and can be modified using MySQL Workbench. This variable enables administrators to require all client connections to the server to be made using some form of secure transport. (Bug #21484632) * A dialog showing the wait time of an attempted connection now displays earlier for improved visibility. (Bug #21264710) * Some routine database operations caused MySQL Workbench to fail and exit intermittently. (Bug #21231450, Bug #77286) * The slash character (/) when used in the name of a new connection separated a group from the real connection name by default without first notifying the user. This fix gives the user an option to keep the slash character and create a connection group or to replace all slash characters in the connection name with underscore characters. (Bug #21158191, Bug #77175) * In a query, UNION and UNION ALL statements that contained data from different tables or different databases returned data in the Result Grid that could be edited and applied to the wrong table. This fix returns read-only data that cannot be edited directly for such queries. (Bug #21046384, Bug #76964) * The identifier quote character (`) was missing from the DROP statement when an attempt was made to drop the existing trigger on a database with an illegal character in the name. A syntax error resulted. (Bug #20978108, Bug #76869) * The property values of a table in an EER diagram could not be edited from the Properties Editor. (Bug #20930134) * Stored procedures containing valid query syntax produced syntax errors. (Bug #20929172, Bug #76761) * Some characters could not be inserted into cells of the result grid and displayed the following text-truncation error message: Inserted data has been truncated as the control's limit was reached. Please use the value editor instead for editing such large text data. (Bug #20927915, Bug #76760) * SQL Editor did not permit the use of DUAL in a derived-table subquery. (Bug #20800341) * When the resultset grid in SQL Editor was set to a font type and size that exceeded the default row height, the output from a query hid a portion the row content instead of increasing the row height to accommodate the font value. (Bug #20794106, Bug #76520) * The binlog_group_commit_sync_delay and binlog_group_commit_sync_no_delay_count options that were added in MySQL Server 5.7.5 are now supported, and can be modified using Workbench. (Bug #20712947) * Russian language connection names failed to load and display properly in the home screen. (Bug #20697403, Bug #76015) * The innodb_page_size MySQL Server system variable can now be changed to either 32k or 64k in Workbench, in addition to the current options. Support for these larger innodb_page_size values was added in MySQL Server 5.7.6. The default value in MySQL 5.7 is 16k. (Bug #20661249) * Executing the current statement of a query by using the CTRL+ALT+ENTER keyboard shortcut (Vertical Text Output) partially or fully hid the output. (Bug #20573658, Bug #75959) * When closing a tab in the SQL Editor, the focus always returned to the first tab regardless of the number of tabs open. This fix returns focus to the preceding tab (to the left) of the closed tab. (Bug #20351753, Bug #75490) * A valid server connection was required before a script or model file could be viewed or edited. (Bug #20326028, Bug #75452) * Starting MySQL Workbench from the command line with an optional argument of a script or model file required the absolute (or fully qualified) path name of the file. (Bug #20268606, Bug #75305) * SQL Editor identified syntax errors in valid statements that executed properly. (Bug #20116982, Bug #74183) * Font sizes were increased in the Home screen for improved readability. (Bug #19982157, Bug #74721) * The MySQL Table Editor did not display the name of a selected table within an EER diagram when the editor was first opened. (Bug #19693466, Bug #74102) * Because the sys schema is installed by default as of MySQL server 5.7.7, MySQL Workbench now checks for and uses it. Otherwise, MySQL Workbench (as it has since 6.1) provides the option to install it. References: See also: Bug #71207. On behalf of the MySQL Workbench and the MySQL/ORACLE RE Team Daniel Horecki [Less]
Posted 27 days ago by Jocelyn Ramilison
Dear MySQL users, MySQL MySQL Utilities 1.6.5 is a GA version of 1.6 release series. It can be used for production environments. MySQL Utilities version 1.6.5 GA is compatible with MySQL Server versions 5.5 and greater. Python v2.6 and v2.7 are ... [More] supported. It 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. MySQL Utilities provides a collection of command-line utilities that are used for maintaining and administering MySQL servers, including: • Admin Utilities (Clone, Copy, Compare, Diff, Export, Import, User Management) • Replication Utilities (Setup, Configuration, Verification) • General Utilities (Disk Usage, Redundant Indexes, Manage Meta & Audit Data) • And more Changes in MySQL Utilities 1.6.5 (2017-01-25) Bugs Fixed * Corrected a problem when using a --exec-before script that failed causing the mysqlfailover utility to fail silently. (Bug #25030151) * Added corrections to the message text of some utilities to eliminate typographical errors. (Bug #24742356, Bug #83173) * The mysqldbcopy utility failed to copy views that refer other views in the list of databases to be copied. (Bug #24657793) * Corrected an issue when using anonymous hosts. (Bug #24624716, Bug #82636) * The mysqlfrm utility failed to parse some .frm files properly. This fix ensures that the utility can parse tables with many columns in the field list. (Bug #24613794, Bug #82907) * The mysqldbcopy utility failed to copy tables with a primary key set to zero and with AUTO_INCREMENT applied. This fix enables the copy and export of auto-increment columns with an initial value of zero. For export, the user is warned to turn on the NO_AUTO_VALUE_ON_ZERO mode for the import and suggested SQL statements to enable the mode are provided. For copy, the mode is turned on automatically and turned off after the copy. (Bug #23598948, Bug #81866) * Permits IPv4 address parsing to include values of 0-255 rather than 0-254. Thanks to Erol Guven for the patch. (Bug #23578714, Bug #81834) * Tables with BLOB data in fields marked NOT NULL restricted the operation of the mysqldbcopy utility. This fix enables the utility to copy these tables by temporarily altering the columns on the destination to remove the NOT NULL option and then to restore it after the copy. (Bug #23335753, Bug #81553) * Corrected an issue with reading strings from configuration files when run with Python 2.6. (Bug #22738248) * Corrected the error message stating the --discover-slaves-login option is not used with the failover command for the mysqlrpladmin utility. (Bug #22616847, Bug #80082) * Corrected the problem when socket files are used in replication utilities. Previously, the port defaulted to 3306 instead of the actual port for the servers. The code now retrieves the port from the connected servers so that connections of slaves are directed to the correct port. (Bug #22543116) * Added context to errors resulting from server startup for the mysqlserverclone utility. Messages recommend using the -vvv option to find the actual error from the server startup sequence. (Bug #22457829) * The mysqlfrm utility failed when the --verbosity option was used. This fix replaces the --verbosity option with --verbose, the correct option name, and uses it consistently in error messages and code. (Bug #22254445, Bug #79382) * The mysqlserverinfo utility required connection parameters to show all MySQL servers running on the local host. This fix removes that restriction when the --show-servers option is specified. (Bug #22215626, Bug #79135) * Corrected a problem in the mysqldbimport utility where specifying the --skip option with a valid type failed to skip the intended object or objects during the operation. (Bug #22155217, Bug #79128) * The mysqldbcopy utility failed to copy grants for anonymous users. (Bug #22093518, Bug #78940) * Improved the --quiet option to silence all informational messages for the mysqldbcompare utility. (Bug #22093453, Bug #78938) * Corrected a problem using a single database name in the mysqldiff utility when comparing the same database on two servers. (Bug #21764003) * The DEB packages did not create the required /usr/share/pyshared/mysql directory. (Bug #21626041, Bug #78054) * Added error handling to ensure only one slave is specified for the --slave option for the mysqlreplicate, mysqlrplcheck, and mysqlrplms utilities. (Bug #21497923) * Enabled the use of the --exclude option for the mysqlrplsync utility. (Bug #21270853, Bug #77359) * Corrected a logic error when detecting and setting READ_ONLY mode on the candidate server during promotion for failover. (Bug #21201454, Bug #76522) * When the mysqldiff utility compared columns for indexes, it failed to take into account cardinality changes. That is, if the cardinality of one column differed from the corresponding column in the compared table, the index was considered different. This fix eliminates unnecessarily changes to indexes by the utility when cardinality differences are detected. (Bug #20857151, Bug #76619) * Removed password() function usage in the MySQL Utilities library for MySQL 5.7.6 or later. (Bug #20807296) * The mysqlfailover utility did not remove the failover_console table correctly on exit when run with the --daemon=start option. (Bug #20524886) * Improved the --force option for the mysqldiff utility to allow checks to continue when missing objects are detected. (Bug #20511130, Bug #75822) * Removed an extraneous difference in GRID format output of the mysqldbcompare utility when column sizes differ. (Bug #18763591) * Corrected PEP8 warnings and errors on the utilities code base. (Bug #18755438) * Corrected an issue in which the mysqldbexport utility produced output with inconsistent table and database names. (Bug #18733683) Reporting Bugs -------------- We welcome and appreciate your feedback and bug reports: http://bugs.mysql.com/ Enjoy! On Behalf of the MySQL/ORACLE RE Team Hery Ramilison [Less]
Posted about 1 month ago by Andy Bang
We are pleased to announce that MySQL Enterprise Monitor 3.2.6 is now available for download on the My Oracle Support (MOS) web site. This is a maintenance release that includes a few enhancements and fixes a number of bugs. You can find more ... [More] information on the contents of this release in the change log: http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/news-3-2-6.html (also included at the end of this note for convenience) You will find binaries for the new release on My Oracle Support: https://support.oracle.com Choose the "Patches & Updates" tab, and then choose the "Product or Family (Advanced Search)" side tab in the "Patch Search" portlet. IMPORTANT: MySQL Enterprise Monitor (MEM) 3.3 offers many significant improvements over MEM 3.2 and we highly recommend that you consider upgrading. More information on MEM 3.3 is available here: What's New in MySQL Enterprise Monitor 3.3 http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-comparison-3-2.html MySQL Enterprise Monitor http://www.mysql.com/products/enterprise/monitor.html MySQL Enterprise Monitor Frequently Asked Questions http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-faq.html MySQL Enterprise Monitor Change History http://dev.mysql.com/doc/relnotes/mysql-monitor/3.3/en/ Please open a bug or a ticket on My Oracle Support to report problems, request features, or give us general feedback about how this release meets your needs. If you are not a MySQL Enterprise customer and want to try the Monitor and Query Analyzer using our 30-day free customer trial, go to http://www.mysql.com/trials, or contact Sales at http://www.mysql.com/about/contact. Useful URLs * My Oracle Support - http://support.oracle.com/ * What's New in 3.2 - https://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-comparison-3-2.html * Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.2/en/ * Installation documentation - http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-installing.html * Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.2/en/ * Product information - http://www.mysql.com/products/enterprise/monitor.html * FAQs - http://dev.mysql.com/doc/mysql-monitor/3.2/en/mem-faq.html * Download - http://support.oracle.com/ Thanks and Happy Monitoring! - The MySQL Enterprise Tools Development Team ========== Changes in MySQL Enterprise Monitor 3.2.6 Functionality Added or Changed * The value defined in Show entries on the Event Handlers page is saved as default. (Bug #24347638) * The bundled JRE was updated to 1.8.0_112 for both the Agent and Service Manager. * The OpenSSL libraries used by the MySQL Enterprise Monitor installers and MySQL Enterprise Monitor Aggregator have been upgraded to 1.0.2j. * The Slave Master Info/Relay Log Info Not Crash Safe is removed in this version. Its functionality is rolled into the Replication Configuration advisor. * The specific operating system version is now displayed in the Host Details section of the MySQL Instances dashboard. * The MySQL database, bundled with the MySQL Enterprise Service Manager, has been upgraded to MySQL 5.6.35. Bugs Fixed * Under certain circumstances, the asset selector list would not load on the Assets tab of the Groups page. (Bug #25051693) * Under certain circumstances, if a notification group contained one or more invalid email addresses, the notification failed. As of this release, the invalid address exception generated by the email server is handled correctly, the invalid email address is removed, and the notification is resent. If the notification group contains multiple invalid addresses, they are removed and the message resent until either the notification is sent or no email addresses remain. Errors are logged to the Action Log. (Bug #25037204) * If the backup directory was set to the same directory as the installation directory, the upgrade installer removed the installation, and the upgrade process failed. As of this release, the installers check if the backup directory is set to the same directory as the installation directory. This issue affected the upgrade installers for the MySQL Enterprise Service Manager, MySQL Enterprise Monitor Agent, and the MySQL Enterprise Monitor Proxy and Aggregator. (Bug #25027413, Bug #25078184, Bug #25078204) * The Show n entries drop-down menu on the Query Analyzer page was too small. This affected the Google Chrome browser, only. (Bug #24948388) * Comma-separated external role definitions were not correctly parsed on the Roles page. (Bug #24918199) * The External Role field on the Roles and Settings pages, was too small. (Bug #24917944) * The fields on the Encryption Settings tab of the Add MySQL Instance or Edit Instances dialogs did not reflect the actual configuration. (Bug #24833411) * The Group Settings tab on the Edit Instance dialog was too small to properly display its contents. (Bug #24481474) * Resume Event Handler dialog was too small for its contents. (Bug #24481411) * Duplicate actions were taken, and notifications sent, if multiple event handlers used the same advisor. As of this release, duplicate actions and notifications are combined into a single action or notification. However, each event handler is logged as handling the event. (Bug #24341371) * The Line and Stack graph controls were not displayed for graphs with many series. (Bug #22378850) * The auto-update parameter of the MySQL Enterprise Service Manager configuration utilities, config.sh, did not behave as expected. * Fields of the Add Instance dialog, for unmonitored instances, did not auto-populate with the correct, agent, hostname, or port number. [Less]
Posted about 1 month ago by Andy Bang
We are pleased to announce that MySQL Enterprise Monitor 3.1.6 is now available for download on the My Oracle Support (MOS) web site. This is a maintenance release that includes a few enhancements and fixes a number of bugs. You can find more ... [More] information on the contents of this release in the change log: http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/news-3-1-6.html (also included at the end of this note for convenience) You will find binaries for the new release on My Oracle Support: https://support.oracle.com Choose the "Patches & Updates" tab, and then choose the "Product or Family (Advanced Search)" side tab in the "Patch Search" portlet. IMPORTANT: MySQL Enterprise Monitor (MEM) 3.3 offers many significant improvements over MEM 3.1 and MEM 3.2 and we highly recommend that you consider upgrading. More information on MEM 3.3 is available here: What's New in MySQL Enterprise Monitor 3.3 http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-comparison-3-2.html MySQL Enterprise Monitor http://www.mysql.com/products/enterprise/monitor.html MySQL Enterprise Monitor Frequently Asked Questions http://dev.mysql.com/doc/mysql-monitor/3.3/en/mem-faq.html MySQL Enterprise Monitor Change History http://dev.mysql.com/doc/relnotes/mysql-monitor/3.3/en/ Please open a bug or a ticket on My Oracle Support to report problems, request features, or give us general feedback about how this release meets your needs. If you are not a MySQL Enterprise customer and want to try the Monitor and Query Analyzer using our 30-day free customer trial, go to http://www.mysql.com/trials, or contact Sales at http://www.mysql.com/about/contact. Useful URLs * My Oracle Support - http://support.oracle.com/ * What's New in 3.1 - https://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-comparison-3-1.html * Change log - http://dev.mysql.com/doc/relnotes/mysql-monitor/3.1/en/ * Installation documentation - http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-installing.html * Complete documentation - http://dev.mysql.com/doc/mysql-monitor/3.1/en/ * Product information - http://www.mysql.com/products/enterprise/monitor.html * FAQs - http://dev.mysql.com/doc/mysql-monitor/3.1/en/mem-faq.html * Download - http://support.oracle.com/ Thanks and Happy Monitoring! - The MySQL Enterprise Tools Development Team ========== Changes in MySQL Enterprise Monitor 3.1.6 Functionality Added or Changed * The configuration menu item Event Handling was renamed Event Handlers. * The bundled JRE was updated to 1.8.0_112 for both the Agent and Service Manager. * The OpenSSL libraries used by the MySQL Enterprise Monitor installers and MySQL Enterprise Monitor Aggregator have been upgraded to 1.0.2j. * The specific operating system version is now displayed in the Host Details section of the MySQL Instances dashboard. * The MySQL database, bundled with the MySQL Enterprise Service Manager, has been upgraded to MySQL 5.6.35. Bugs Fixed * Under certain circumstances, the asset selector list would not load on the Assets tab of the Groups page. (Bug #25051693) * Under certain circumstances, if a notification group contained one or more invalid email addresses, the notification failed. As of this release, the invalid address exception generated by the email server is handled correctly, the invalid email address is removed, and the notification is resent. If the notification group contains multiple invalid addresses, they are removed and the message resent until either the notification is sent or no email addresses remain. Errors are logged to the Action Log. (Bug #25037204) * If the backup directory was set to the same directory as the installation directory, the upgrade installer removed the installation, and the upgrade process failed. As of this release, the installers check if the backup directory is set to the same directory as the installation directory. This issue affected the upgrade installers for the MySQL Enterprise Service Manager, MySQL Enterprise Monitor Agent, and the MySQL Enterprise Monitor Proxy and Aggregator. (Bug #25027413, Bug #25078184, Bug #25078204) * The Show n entries drop-down menu on the Query Analyzer page was too small. This affected the Google Chrome browser, only. (Bug #24948388) * Comma-separated external role definitions were not correctly parsed on the Roles page. (Bug #24918199) * The External Role field on the Roles and Settings pages, was too small. (Bug #24917944) * The fields on the Encryption Settings tab of the Add MySQL Instance or Edit Instances dialogs did not reflect the actual configuration. (Bug #24833411) * The Group Settings tab on the Edit Instance dialog was too small to properly display its contents. (Bug #24481474) * Resume Event Handler dialog was too small for its contents. (Bug #24481411) * Duplicate actions were taken, and notifications sent, if multiple event handlers used the same advisor. As of this release, duplicate actions and notifications are combined into a single action or notification. However, each event handler is logged as handling the event. (Bug #24341371) * The Line and Stack graph controls were not displayed for graphs with many series. (Bug #22378850) * The auto-update parameter of the MySQL Enterprise Service Manager configuration utilities, config.sh, did not behave as expected. * Fields of the Add Instance dialog, for unmonitored instances, did not auto-populate with the correct, agent, hostname, or port number. [Less]
Posted about 1 month ago
Posted about 1 month ago by Jocelyn Ramilison
Dear MySQL Users, MySQL Cluster 7.5.5 (GA) is a GA release for MySQL Cluster 7.5. MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional ... [More] checkpointing to disk) - Transparent Auto-Sharding - Read & write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.5.5, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.5/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.5.5 (5.7.17-ndb-7.5.5) (2017-01-17) MySQL Cluster NDB 7.5.5 is a new release of MySQL Cluster NDB 7.5, based on MySQL Server 5.7 and including features in version 7.5 of the NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) storage engine, as well as fixing recently discovered bugs in previous MySQL Cluster releases. Obtaining MySQL Cluster NDB 7.5. MySQL Cluster NDB 7.5 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL Cluster NDB 7.5, see What is New in MySQL NDB Cluster 7.5 (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster-what-is-new.html). This release also incorporates all bugfixes and changes made in previous MySQL Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.7 through MySQL 5.7.17 (see Changes in MySQL 5.7.17 (2016-12-12) , General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.7/en/news-5-7-17.html)). Bugs Fixed * Packaging: The RPM installer for the MySQL Cluster auto-installer package had a dependency on python2-crypt instead of python-crypt. (Bug #24924607) * Microsoft Windows: Installation failed when the Auto-Installer (ndb_setup.py) was run on a Windows host that used Swedish as the system language. This was due to system messages being issued using the cp1252 character set; when these messages contained characters that did not map directly to 7-bit ASCII (such as the ä character in Tjänsten ... startar), conversion to UTF-8---as expected by the Auto-Installer web client---failed. This fix has been tested only with Swedish as the system language, but should work for Windows systems set to other European languages that use the cp1252 character set. (Bug #83870, Bug #25111830) * No traces were written when ndbmtd received a signal in any thread other than the main thread, due to the fact that all signals were blocked for other threads. This issue is fixed by the removal of SIGBUS, SIGFPE, SIGILL, and SIGSEGV signals from the list of signals being blocked. (Bug #25103068) * The rand() function was used to produce a unique table ID and table version needed to identify a schema operation distributed between multiple SQL nodes, relying on the assumption that rand() would never produce the same numbers on two different instances of mysqld. It was later determined that this is not the case, and that in fact it is very likely for the same random numbers to be produced on all SQL nodes. This fix removes the usage of rand() for producing a unique table ID or version, and instead uses a sequence in combination with the node ID of the coordinator. This guarantees uniqueness until the counter for the sequence wraps, which should be sufficient for this purpose. The effects of this duplication could be observed as timeouts in the log (for example NDB create db: waiting max 119 sec for distributing) when restarting multiple mysqld processes simultaneously or nearly so, or when issuing the same CREATE DATABASE (http://dev.mysql.com/doc/refman/5.7/en/create-database.html) or DROP DATABASE (http://dev.mysql.com/doc/refman/5.7/en/drop-database.html) statement on multiple SQL nodes. (Bug #24926009) * The ndb_show_tables utility did not display type information for hash maps or fully replicated triggers. (Bug #24383742) * Long message buffer exhaustion when firing immediate triggers could result in row ID leaks; this could later result in persistent RowId already allocated errors (NDB Error 899). (Bug #23723110) References: See also: Bug #19506859, Bug #13927679. * when a parent NDB (http://dev.mysql.com/doc/refman/5.7/en/mysql-cluster.html) table in a foreign key relationship was updated, the update cascaded to a child table as expected, but the change was not cascaded to a child table of this child table (that is, to a grandchild of the original parent). This can be illustrated using the tables generated by the following CREATE TABLE (http://dev.mysql.com/doc/refman/5.7/en/create-table.html) statements: CREATE TABLE parent( id INT PRIMARY KEY AUTO_INCREMENT, col1 INT UNIQUE, col2 INT ) ENGINE NDB; CREATE TABLE child( ref1 INT UNIQUE, FOREIGN KEY fk1(ref1) REFERENCES parent(col1) ON UPDATE CASCADE ) ENGINE NDB; CREATE TABLE grandchild( ref2 INT, FOREIGN KEY fk2(ref2) REFERENCES child(ref1) ON UPDATE CASCADE ) ENGINE NDB; Table child is a child of table parent; table grandchild is a child of table child, and a grandchild of parent. In this scenario, a change to column col1 of parent cascaded to ref1 in table child, but it was not always propagated in turn to ref2 in table grandchild. (Bug #83743, Bug #25063506) * The NDB binlog injector thread used an injector mutex to perform two important tasks: 1. Protect against client threads creating or dropping events whenever the injector thread waited for pollEvents(). 2. Maintain access to data shared by the injector thread with client threads. The first of these could hold the mutex for long periods of time (on the order of 10ms), while locking it again extremely quickly. This could keep it from obtaining the lock for data access ("starved") for unnecessarily great lengths of time. To address these problems, the injector mutex has been refactored into two---one to handle each of the two tasks just listed. It was also found that initialization of the binlog injector thread held the injector mutex in several places unnecessarily, when only local thread data was being initialized and sent signals with condition information when nothing being waited for was updated. These unneeded actions have been removed, along with numerous previous temporary fixes for related injector mutex starvation issues. (Bug #83676, Bug #83127, Bug #25042101, Bug #24715897) References: See also: Bug #82680, Bug #20957068, Bug #24496910. * When ndbmtd was built on Solaris/SPARC with version 5.3 of the GNU tools, data nodes using the resulting binary failed during startup. (Bug #83500, Bug #24941880) References: See also: Bug #83517, Bug #24947597. * MySQL Cluster failed to compile using GCC 6. (Bug #83308, Bug #24822203) * When a data node was restarted, the node was first stopped, and then, after a fixed wait, the management server assumed that the node had entered the NOT_STARTED state, at which point, the node was sent a start signal. If the node was not ready because it had not yet completed stopping (and was therefore not actually in NOT_STARTED), the signal was silently ignored. To fix this issue, the management server now checks to see whether the data node has in fact reached the NOT_STARTED state before sending the start signal. The wait for the node to reach this state is split into two separate checks: + Wait for data nodes to start shutting down (maximum 12 seconds) + Wait for data nodes to complete shutting down and reach NOT_STARTED state (maximum 120 seconds) If either of these cases times out, the restart is considered failed, and an appropriate error is returned. (Bug #49464, Bug #11757421) * CMake now avoids configuring the -fexpensive-optimizations option for GCC versions for which the option triggers faulty shift-or optimizations. (Bug #24947597, Bug #83517) On Behalf of the MySQL/ORACLE RE Team Hery Ramilison [Less]
Posted about 1 month ago by Gipson Pulla
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & ... [More] write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http and Memcached) MySQL Cluster 7.2.27, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.2/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Changes in MySQL NDB Cluster 7.2.27 (5.5.54-ndb-7.2.27) (2017-01-17) MySQL NDB Cluster 7.2.27 is a new release of NDB Cluster, incorporating new features in the NDB storage engine, and fixing recently discovered bugs in previous MySQL NDB Cluster 7.2 development releases. Obtaining MySQL NDB Cluster 7.2. MySQL NDB Cluster 7.2 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.5 through MySQL 5.5.54 (see Changes in MySQL 5.5.54 (2016-12-12, General availability) (http://dev.mysql.com/doc/relnotes/mysql/5.5/en/news-5-5-54.html)). Bugs Fixed * A number of potential buffer overflow issues were found and fixed in the NDB codebase. (Bug #25260091) References: See also: Bug #23152979. * ndb_restore did not restore tables having more than 341 columns correctly. This was due to the fact that the buffer used to hold table metadata read from .ctl files was of insufficient size, so that only part of the table descriptor could be read from it in such cases. This issue is fixed by increasing the size of the buffer used by ndb_restore for file reads. (Bug #25182956) On Behalf of MySQL Release Engineering Team, Gipson Pulla [Less]
Posted about 1 month ago by Nawaz Nazeer ahamed
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance (with optional checkpointing to disk) - Transparent Auto-Sharding - Read & ... [More] write scalability - Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.3.16, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.3.16 (5.6.35-ndb-7.3.16) (2017-01-17, General Availability) MySQL NDB Cluster 7.3.16 is a new release of NDB Cluster, based on MySQL Server 5.6 and including features from version 7.3 of the NDB storage engine, as well as fixing a number of recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.3. MySQL NDB Cluster 7.3 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.3, see What is New in NDB Cluster 7.3 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what-is -new-7-3.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.35 (see Changes in MySQL 5.6.35 (2016-12-12, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news-5-6-35.html)). Bugs Fixed * ndb_restore did not restore tables having more than 341 columns correctly. This was due to the fact that the buffer used to hold table metadata read from .ctl files was of insufficient size, so that only part of the table descriptor could be read from it in such cases. This issue is fixed by increasing the size of the buffer used by ndb_restore for file reads. (Bug #25182956) * The rand() function was used to produce a unique table ID and table version needed to identify a schema operation distributed between multiple SQL nodes, relying on the assumption that rand() would never produce the same numbers on two different instances of mysqld. It was later determined that this is not the case, and that in fact it is very likely for the same random numbers to be produced on all SQL nodes. This fix removes the usage of rand() for producing a unique table ID or version, and instead uses a sequence in combination with the node ID of the coordinator. This guarantees uniqueness until the counter for the sequence wraps, which should be sufficient for this purpose. The effects of this duplication could be observed as timeouts in the log (for example NDB create db: waiting max 119 sec for distributing) when restarting multiple mysqld processes simultaneously or nearly so, or when issuing the same CREATE DATABASE or DROP DATABASE statement on multiple SQL nodes. (Bug #24926009) * Long message buffer exhaustion when firing immediate triggers could result in row ID leaks; this could later result in persistent RowId already allocated errors (NDB Error 899). (Bug #23723110) References: See also: Bug #19506859, Bug #13927679. * when a parent NDB table in a foreign key relationship was updated, the update cascaded to a child table as expected, but the change was not cascaded to a child table of this child table (that is, to a grandchild of the original parent). This can be illustrated using the tables generated by the following CREATE TABLE statements: CREATE TABLE parent( id INT PRIMARY KEY AUTO_INCREMENT, col1 INT UNIQUE, col2 INT) ENGINE NDB; CREATE TABLE child( ref1 INT UNIQUE, FOREIGN KEY fk1(ref1) REFERENCES parent(col1) ON UPDATE CASCADE ) ENGINE NDB; CREATE TABLE grandchild( ref2 INT, FOREIGN KEY fk2(ref2) REFERENCES child(ref1) ON UPDATE CASCADE ) ENGINE NDB; Table child is a child of table parent; table grandchild is a child of table child, and a grandchild of parent. In this scenario, a change to column col1 of parent cascaded to ref1 in table child, but it was not always propagated in turn to ref2 in table grandchild. (Bug #83743, Bug #25063506) On Behalf of MySQL Release Engineering Team, Nawaz Nazeer Ahamed [Less]
Posted about 1 month ago by Sreedhar S
Dear MySQL Users, MySQL Cluster is the distributed, shared-nothing variant of MySQL. This storage engine provides: - In-Memory storage - Real-time performance - Transparent Auto-Sharding - Read & write scalability - ... [More] Active-Active/Multi-Master geographic replication - 99.999% High Availability with no single point of failure and on-line maintenance - NoSQL and SQL APIs (including C++, Java, http, Memcached and JavaScript/Node.js) MySQL Cluster 7.4 makes significant advances in performance; operational efficiency (such as enhanced reporting and faster restarts and upgrades) and conflict detection and resolution for active-active replication between MySQL Clusters. MySQL Cluster 7.4.14, has been released and can be downloaded from http://www.mysql.com/downloads/cluster/ where you will also find Quick Start guides to help you get your first MySQL Cluster database up and running. The release notes are available from http://dev.mysql.com/doc/relnotes/mysql-cluster/7.4/en/index.html MySQL Cluster enables users to meet the database challenges of next generation web, cloud, and communications services with uncompromising scalability, uptime and agility. More details can be found at http://www.mysql.com/products/cluster/ Enjoy ! Changes in MySQL NDB Cluster 7.4.14 (5.6.35-ndb-7.4.14) (2017-01-17 , General Availability) MySQL NDB Cluster 7.4.14 is a new release of MySQL NDB Cluster 7.4, based on MySQL Server 5.6 and including features in version 7.4 of the NDB storage engine, as well as fixing recently discovered bugs in previous NDB Cluster releases. Obtaining MySQL NDB Cluster 7.4. MySQL NDB Cluster 7.4 source code and binaries can be obtained from http://dev.mysql.com/downloads/cluster/. For an overview of changes made in MySQL NDB Cluster 7.4, see What is New in NDB Cluster 7.4 (http://dev.mysql.com/doc/refman/5.6/en/mysql-cluster-what -is-new-7-4.html). This release also incorporates all bugfixes and changes made in previous NDB Cluster releases, as well as all bugfixes and feature changes which were added in mainline MySQL 5.6 through MySQL 5.6.35 (see Changes in MySQL 5.6.35 (2016-12-12, General Availability) (http://dev.mysql.com/doc/relnotes/mysql/5.6/en/news -5-6-35.html)). Bugs Fixed * ndb_restore did not restore tables having more than 341 columns correctly. This was due to the fact that the buffer used to hold table metadata read from .ctl files was of insufficient size, so that only part of the table descriptor could be read from it in such cases. This issue is fixed by increasing the size of the buffer used by ndb_restore for file reads. (Bug #25182956) * Queries against the ndbinfo.memory_per_fragment table when running with a large number of data nodes could produce unexpected results for the highest-numbered nodes. (Bug #25176404) * The rand() function was used to produce a unique table ID and table version needed to identify a schema operation distributed between multiple SQL nodes, relying on the assumption that rand() would never produce the same numbers on two different instances of mysqld. It was later determined that this is not the case, and that in fact it is very likely for the same random numbers to be produced on all SQL nodes. This fix removes the usage of rand() for producing a unique table ID or version, and instead uses a sequence in combination with the node ID of the coordinator. This guarantees uniqueness until the counter for the sequence wraps, which should be sufficient for this purpose. The effects of this duplication could be observed as timeouts in the log (for example NDB create db: waiting max 119 sec for distributing) when restarting multiple mysqld processes simultaneously or nearly so, or when issuing the same CREATE DATABASE or DROP DATABASE statement on multiple SQL nodes. (Bug #24926009) * The ndb_show_tables utility did not display type information for hash maps or fully replicated triggers. (Bug #24383742) * Long message buffer exhaustion when firing immediate triggers could result in row ID leaks; this could later result in persistent RowId already allocated errors (NDB Error 899). (Bug #23723110) References: See also: Bug #19506859, Bug #13927679. * when a parent NDB table in a foreign key relationship was updated, the update cascaded to a child table as expected, but the change was not cascaded to a child table of this child table (that is, to a grandchild of the original parent). This can be illustrated using the tables generated by the following CREATE TABLE statements: CREATE TABLE parent( id INT PRIMARY KEY AUTO_INCREMENT, col1 INT UNIQUE, col2 INT ) ENGINE NDB; CREATE TABLE child( ref1 INT UNIQUE, FOREIGN KEY fk1(ref1) REFERENCES parent(col1) ON UPDATE CASCADE ) ENGINE NDB; CREATE TABLE grandchild( ref2 INT, FOREIGN KEY fk2(ref2) REFERENCES child(ref1) ON UPDATE CASCADE ) ENGINE NDB; Table child is a child of table parent; table grandchild is a child of table child, and a grandchild of parent. In this scenario, a change to column col1 of parent cascaded to ref1 in table child, but it was not always propagated in turn to ref2 in table grandchild. (Bug #83743, Bug #25063506) * When a data node running with StopOnError set to 0 underwent an unplanned shutdown, the automatic restart performed the same type of start as the previous one. In the case where the data node had previously been started with the --initial option, this meant that an initial start was performed, which in cases of multiple data node failures could lead to loss of data. This issue also occurred whenever a data node shutdown led to generation of a core dump. A check is now performed to catch all such cases, and to perform a normal restart instead. In addition, in cases where a failed data node was unable prior to shutting down to send start phase information to the angel process, the shutdown was always treated as a startup failure, also leading to an initial restart. This issue is fixed by adding a check to execute startup failure handling only if a valid start phase was received from the client. (Bug #83510, Bug #24945638) On behalf of the MySQL Release Team -Sreedhar S [Less]
Posted about 1 month ago by Piotr Obrzut
Dear MySQL Users, A new GA (general availability) version of MySQL Connector/C has been made available: MySQL Connector/C 6.1.9 GA. The MySQL Connector/C provides a C API for connecting client applications to the MySQL Server 5.5 or newer. You ... [More] can download the production release at: http://dev.mysql.com/downloads/connector/c/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. 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! ====================================================================== Changes in MySQL Connector/C 6.1.9 (2017-01-10, General Availability) Security Notes * OpenSSL is ending support for version 1.0.1 in December 2016; see https://www.openssl.org/policies/releasestrat.html. Consequently, Connector/C Commercial builds now use version 1.0.2 rather than version 1.0.1, and the linked OpenSSL library for the Connector/C Commercial has been updated from version 1.0.1 to version 1.0.2j. For a description of issues fixed in this version, see https://www.openssl.org/news/vulnerabilities.html. This change does not affect Oracle-produced MySQL Community builds of Connector/C, which use the yaSSL library instead. (Bug #24753384) * A new MYSQL_OPT_TLS_VERSION option is available for the mysql_options() C API function to indicate the protocols permitted by the client for encrypted connections. For more information, see mysql_options() (http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html). (Bug #22932026) * A new MYSQL_OPT_SSL_MODE option is available for the mysql_options() C API function to indicate the security state to use for the connection to the server. For more information, see mysql_options() (http://dev.mysql.com/doc/refman/5.7/en/mysql-options.html). (Bug #22931973) Functionality Added or Changed * Previously, Connector/C permitted user names up to a maximum of 16 characters. Connector/C now permits longer user names (up to 32 characters) if the server does. (Bug #22931954) * Connector/C now includes support for the server GTID session tracker, introduced in MySQL 5.7.6. This tracker is exposed through the session_track_gtids system variable. (Bug #21040741) * Connector/C now includes support for additional ranges of server errors, introduced in MySQL 5.7.6. (Bug #21040703) On Behalf of the MySQL/ORACLE RE Team Piotr Obrzut [Less]