Datanamic SchemaDiff MultiDB 2011
Comparison and synchronization
of database schemas
Version History
Version 2011.02
- Fixed an issue with connecting to a MySQL 5.5.12 database (Bad Handshake error).
Version 2011.01
- New Compare dialog. From now on you can select the data sources you want
to compare in the Compare dialog.
- New comparison results summary dialog. This dialog will be displayed
after comparing a model with a database.
- Removed the New project wizard. This wizard is replaced by the Compare
dialog.
- Added comparison options to let you tweak the way the comparison works (
e.g. case insensitive comparison, ignore comments, ignore key index,
pre-format code in views, etc...)
- Added the option to sort on object type in the comparison results grid.
- Readability of the details of the differences between objects in the
comparison results grid has been improved.
- Comparison results summary has been extended and can be copied to
clipboard now.
- From now on you can compare your database to SQL scripts that represent
the structure of your database.
- Improved differences reports are being generated.
- Added support for comparing column and index options.
- For some data types a wrong value for length of non-numeric data types was
imported. Fixed.
- Improved routine to automatically detect and map renamed database objects
such as tables, columns etc. is used when comparing databases.
- Fixed an issue with comparison of check constraints. We get better
comparison results when sorting column and table check constraints on the
name of the constraint.
- Schema mappings are now also visible in the difference details.
- Fixed an issue with column default containing a string with only spaces.
Default value was deleted then.
- New synchronization script generator. The new synchronization script
generator fixes some object dependencies issues and generates more
reliable scripts.
- Added synchronization options to let you tweak the way the synchronization
is done. You can now for example ignore certain types of constraints etc.
- Added the option to define pre/post synchronization SQL.
- Redesigned Synchronize dialog.
- Added support for synchronizing column and index options.
- When synchronizing, default values for string and date data types were
automatically quoted when the default value did not contain a reserved
word. Datanamic ShemaDiff now does not quote the default when it contains
a function like for example TO_DATE.
- Improved memory usage when synchronizing large databases.
- Added a command line utility. Create a comparison project with the GUI
version and run that project with the command line utility.
- Added MS Access 2000, 2003, 2007 and 2010 support.
- Added MS SQL Server 2008 support.
- Added support for MS SQL attribute options.
- Added support for MS SQL index options.
- Added case insensitive comparison of MS SQL data types with length set to
"MAX".
- When importing a PostgreSQL 8.3 database, some procedures were imported
twice. Fixed.
- For MS SQL Server it only imported schema names for domains if the domain
was in schema 'dbo'. Fixed.
- For MS SQL, the FLOAT datatype was using length where it should be
using precision.
- Added support for PostgreSQL 8.3 and PostgreSQL 9.
- PostgreSQL: Text "::regclass" in default values and check constraints no
longer imported for PostgreSQL.
- New faster and more reliable driver used for connection to PostgreSQL
databases. DLLs in bin folder are not needed anymore.
- System sequences are no longer imported for Oracle databases.
- Foreign key information in table description when using INNODB will now be
removed when importing a MySQL database.
- MySQL functions no longer imported as procedures. Function will have the
CREATE FUNCTION header.
- "on update CURRENT_TIMESTAMP" for a TIMESTAMP column was not imported for
MySQL databases. Fixed.
- Importing MySQL databases. Defaults defined as an empty string ('') are
not imported. Fixed.
- When retrieving Foreign keys in MySQL, the default value for ON DELETE
and ON UPDATE is RESTRICT.
- When retrieving Foreign keys in MySQL, when the ON DELETE is SET NULL,
then the ON UPDATE was ignored. Fixed.
- Fixed a problem in MySQL for updating an existing database. When an
attribute that changed is AutoNumber and PK, then the Autonumber was
added before adding the Primary Key constraint.
- InterBase+Firebase: Combined trigger events like "BEFORE INSERT OR UPDATE"
or "AFTER INSERT OR DELETE" now imported when reverse engineering
InterBase or Firebird databases.