Lost connection to MySQL server during query". As a result, Workbench could lose the connection and result in errors similar to "Error Code: 2013. The DBMS connection keep-alive interval option did not function properly. In other words, adding a default value of "" resulted in Workbench reporting "No changes detected". The Alter Table functionality did not detect a default value change from no default value to an empty string. Import and export to JSON format failed if the table had column names that were keywords such as key or value. The "Limit to Hosts Matching" field in the user manager would incorrectly report a "Host name contains incorrect characters" error if the host named contained numeric characters. The Test Connection functionality only functioned for existing or new connections. Attempting to test custom connection details (a connection not yet created by Workbench) caused Workbench to fail and exit. The Workbench interface would incorrectly orient itself to display as Right-To-Left (RTL) when a system's language is set to a RTL language, despite Workbench not being translated to that language. The PostgreSQL migration wizard could fail with an "pg_catalog.pg_enum does not exist" error. The Server Status page reported incorrect (inflated by about 3x) values The Dashboard and Server Status reported different Select per second values. The PostgreSQL migration wizard could fail to migrate PostgreSQL databases that were generated with tryton. When executing Data Export using a remote MySQL connection, the error resulting from a missing mysqldump binary was unclear. After successfully executing the database migration wizard, executing it a second time required Workbench to be restarted. Under Reverse Engineering, the information provided in the wild card description to select objects contained a typo. In this case, some columns would be hidden from the editor. Workbench's Alter Table functionality did not behave correctly when a column was defined using a TIMESTAMP with fractional seconds, such as TIMESTAMP(1). An new option is available to specify a path to the SSH configuration and/or known hosts file. The generated SQL generated by the forward engineering wizard would incorrectly output "VIRTUALCOMMENT" instead of "VIRTUAL COMMENT". The database migration wizard database field was described as "Leave blank to select it later" but this text was updated to read as "Cannot be blank" because it is a required field The Schema filter was slow (poor performance) when a lot (1000+) of schemas were present. For example, it was not possible to use the JSON data type for variables inside the stored procedure editor as JSON was added in MySQL 5.7.7. Selecting "5.7" from Default target MySQL version did not take into account changes to newer versions, as 5.7 behaved like 5.7.0 instead of a newer version. Migrating a MySQL source to a MySQL target database would fail for tables that had generated columns, as the target server rejected attempts to insert data into generated columns. When viewing the code for an existing view (SQL to create the view), hexadecimal values were truncated. Under Users and Privileges, Workbench did not allow hyphens for host names in the "limit to hosts matching" field. Exporting data to JSON was exporting NULL values as NULL instead of null, thus breaking the JSON output. Editing a remote MySQL options file via the Options File management tool would emit an unhandled exception after clicking Apply. The MySQL Enterprise Backup Restore functionality could emit an unhandled exception under some circumstances. On Linux, the Table Data Export wizard failed to complete the export process. Executing Data Import/Restore would emit an unhandled exception with Import from Self-Contained File enabled. On OS X, after creating a new model, and new diagram, right-clicking on the empty diagram background would freeze Workbench. A typo was fixed on the Configure Server Management page. For example, rather than choosing a version such as "5.7", you can now enter a specific version such as 5.7.12. The Default target MySQL version model preference is now an open text field instead of a dropdown select box.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |