dbForge Schema Compare for MySQL のリリース
Released: Dec 9, 2021
V5.0.539 での更新項目
機能
- Added support for new privileges during syntax checking.
- Improved performance when opening a connection.
不具合の修正
- Fixed an issue that occurred when generating scripts for tables.
- Fixed an issue with reading table metadata.
- Fixed an issue with reading session variables when opening a connection.
Released: Dec 1, 2021
V5.0.533 での更新項目
不具合の修正
- Fixed a false syntax check that hindered the comparison of views.
- Fixed a synchronization issue for a table with PARTITION BY RANGE COLUMN.
- Fixed the selection of encoding when writing synchronization scripts to a file.
- Fixed an issue that occurred when processing scripts containing syntax in versioned comments.
- Fixed a primary key synchronization issue.
- Fixed a synchronization issue for a table with partitioning.
Released: Sep 8, 2021
V5.0.491 での更新項目
不具合の修正
- Fixed an error with reading the default values.
- Fixed a error with displaying a warning about the absence of unique keys in the Data Editor.
Released: Aug 5, 2021
V5.0.471 での更新項目
不具合の修正
- Fixed error with quotation of Default values for the ENUM type.
Released: Jul 28, 2021
V5.0.466 での更新項目
不具合の修正
- Fixed incorrect work with the default TIMESTAMP column.
- Fixed a problem with generating a script for virtual columns.
Released: Jul 8, 2021
V5.0.448 での更新項目
不具合の修正
- Column persistency settings are incorrectly detected within DDL scripts.
- Error with comparing the DEFAULT value for columns with a BIT(1) data type has been fixed.
- Error with comparing automatically generated index names has been fixed.
- Error with searching dependencies has been fixed.
Released: Apr 22, 2021
V5.0.389 での更新項目
不具合の修正
- Error in ignoring spaces through the command line when working with options.
Released: Feb 2, 2021
V5.0.335 での更新項目
不具合の修正
- Minor user reported bugs have been fixed.
Released: Nov 25, 2020
V5.0.318 での更新項目
機能
- Improved connection via SSL.
Released: Oct 10, 2020
V5.0.293 での更新項目
不具合の修正
- Fixed error when analyzing index dependencies.
- Fixed issue with incorrect reading of the DEFAULT values if it was not specified as CURRENT_TIMESTAMP().
