Version History

What's New

Version 6.3.3

When importing from a SQL file and a foreign key constraint has no name, then the relationship will now be automatically given a name.
When importing from MS SQL Server, the Set Null and Set Default values for update and delete actions on foreign key constraints did not import correctly.
Extended the list of predefined function names for MySQL and PostgreSQL that can be used in an attribute’s default value.
When switching to or from MS Access, there was a problem converting the MS Access TEXT datatypes. With MS Access, the TEXT datatype has a maximum limitation of 255 characters.
Enhanced the definition files for SQLite.
Primary key constraint options are now enabled for Oracle data models.
In the Search and replace data type screen, the data types are now being sorted in alphabetic order.
When trying to connect to a MySQL 5.5.12 database it gave a Bad Handshake error.

Version 6.3.2

Improved model validation. Check for unique object names will now exclude nameless objects.
Importing SQL files. Improved support for importing IF EXISTS definitions for indexes, views, triggers and procedures.
Extended the list of predefined function names that can be used in an attribute’s default value.
Fixed an issue with reverse engineering multi-column relationships. This issue was introduced in V6.3.1.
When reverse engineering a postgresql database, '::regclass' and '::character varying' constants in default values and check constraints are removed now.
Added code formatting to data model reports for view code, trigger code and procedure code.
Fixed an issue with incorrect formatting of large views, triggers and procedures when importing MS SQL Server 2005 and MS SQL Server 2008 databases.
Fixed an issue with a DROP PROCEDURE statement instead of a DROP FUNCTION statement in the generated drop script.
Added support for foreign key constraint options for MS SQL Server 2005 and 2008.
Removed variable %arrayoptions% from PostgreSQL definition files. Array options are defined on data type level.
Added missing info to Import database dialog when importing a PostgreSQL database.
Fixed an issue with missing quotes in the default value when you apply a sequence to an attribute in PostgreSQL.
Changed the defaults for ignore indexes on keys when comparing model and database. These are now by default ignored.
Added the option to ignore sequence seed values when comparing your model to the database.
Fixed a reverse engineering issue with wrong automatic replacement of object name with a variable in code objects such as triggers, views and procedures. The object name could not be found in the code when the code contained a reference to another object with a similar, but shorter name.

Version 6.3.1

Fixed a problem with importing SQL files when quotes were used inside comments.
When reverse engineering triggers, sometimes the table name in the trigger code was wrongly replaced by the table name variable.
Fixed an issue when importing SQL files with missing CONSTRAINT keyword in foreign key constraint definitions. When the CONSTRAINT keyword could not be found, the constraint was not imported.
Fixed an issue with reverse engineering relationships with duplicate names.
When reverse engineering a MySQL database it will now correctly determine if an index is of type FREETEXT.
In the Import database dialog the default setting for importing alternate key indexes has been changed. The new default is not ignore indexes on alternate keys.
Forward engineering. Tables are now generated in logical order (if a logical order can be determined).
Fixed an issue with importing PostgreSQL 9 triggers.
Added a version check when connecting to a PostgreSQL database. This to be sure the correct driver will be used.
When editing relationships and %relname% is used in FK constraint name, it did not immediatly change the FK constraint name when the relationship name was edited.
Fixed a problem with importing comments when importing a MS SQL Server script.
When generating a database, and a data type had no length specified (length is optional), it generated () behind the data type. eg VARCHAR() where it should be VARCHAR.
The conditional generation options are now also applied to table options.
Fixed a problem with importing MS SQL Server foreign key constraints when the parent column was part of a unique constraint and a primary key constraint.
Fixed a problem when the Compare to database and update database function was used while connecting to an Oracle database. If a binary type datatype was changed to another datatype, the "ALTER Table MODIFY Column" command was not valid (Oracle error #22859). In this case it will now create a temporary table using the new entity structure, copy the current data from the original table to the temporary table, drop the original table and then rename the temporary table to the original table name.
Fixed a problem when the Compare to database and update database function was used while connecting to an Oracle database. When generating the alter script for renaming an Oracle table, the schema name may not be used in the target.
Fixed an issue with changing the scale on the Print preview dialog.
Added support for MS Access 2010.
Type group of the MS SQL Server SQL_Variant data type was change from Exact Numeric to String.
When comparing databases, and the "Ignore
constraint names" option was used, then the order in which constraints were displayed was not correct.

Version 6.3.0

Improved data type conversion rules to and from database independent models.
Fixed an issue with missing slash in output folder when generating HTML reports.
Fixed a memory leak when importing SQL files.
Fixed an issue with importing MS SQL Server SQL scripts. Data type was accidently converted to the default data type.
SQL file import. Fixed an issue with importing function and procedures for PostgreSQL.
Altering databases. When re-creating a MS SQL Server table, it must copy the data as well. It must not copy data for the TIMESTAMP data type.
When you scroll while the status column in the Details part of the Comparison results screen is highlighted, the columns on both sides did not scroll.
Modified definition files. Added variable for terminator.
Added support for PostgreSQL 9.
Fixed an issue with MS SQL Server's float data type. It was using a length where it should be using a precision.
Fixed a windows display issue with multiple monitors where a monitor was moved from the right side to the left side of the base monitor.
Enhanced the "Working with templates" section in the help file.
Added the %column% variable for index name templates. Variable will be replaced with the first column in the index.
In update indexes on keys new variables are made available for naming foreign key indexes.
Fixed an issue with deleting data types in the Edit data types dialog.
Improved the Edit data type screen. When the data type's list name was edited, you could not edit that entry again.
Added %parentcolumn% and %childcolumn% variables for relationship name and foreign key constraint name templates.

Version 6.2.1

Ignore case for compare to database and update model and compare archived models and update database did not work. Fixed.
When switching from a schema/owner supporting database to a database that does not support schemas, it kept the schema names. Fixed.
Fixed an issue with comparing versions (Access violation).
Fixed an issue with merging projects (Access violation).
Added support for PostgreSQL array data types.

Version 6.2.0

Renamed columns were not always found when comparing model to database. This could result in a incorrect alter script. Fixed.
The default schema/owner name in project options was not used when creating a new entity. Fixed.
Error when opening a project with Sub Categories and relationships with a routing different than auto-routing. Fixed.
Schema name not editable for MS SQL Server 2000 models. Fixed.
Fixed an issue with attribute defaults. The square brackets were ignored and caused function names to become quoted. Fixed.
Fixed an issue with missing foreign key constraints in the generated SQLite 3 SQL.
For PostgreSQL, there was a problem when sequences was applied to an attribute. It will now use nextval() in the default when you apply a sequence to an attribute.
When creating new sequences, the cache code was always blank by default. It will now use the first entry from seqcachecodes variable specified in the in the database definition file.
Added support to map schemas when comparing your data model to an existing database. You can map schema in the compare options dialog.
Domains were not displayed in the Object browser when the target DBMS did not support domains. Fixed.
Reporting: Sequence descriptions were not added to the generated report. Fixed.
Reporting: The lists of selectable properties for each object are now filtered based on what's supported for the target DBMS.
Reporting: Object details did not appear directly after the "Details" heading but on a new page in MS Word and PDF reports. Fixed.
When importing a new database a new subdiagram was created when no schemas were found. Fixed.
No Alter statement was generated when the CLUSTERING of a Primary key constraint changed. Fixed.
Added the option for case insensitive comparison of model and database.
Added the option to ignore empty lines when comparing model and database.
Fixed an issue with importing CREATE TYPE statements for PostgreSQL when reverse engineering from SQL file.
Reporting: Fixed an issue with missing table borders for PDF reports.
Reporting: Improved quality of image of diagram in PDF reports.

Version 6.1.3

Fixed an issue with incorrect replacement of "value" keyword in check constraints.
Performance improvements when zooming in and out.
Fixed an issue with data model/database comparisons. You could get an comparison error when foreign keys/relationships were deleted but not the parent and the child of such a relationship.
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.
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.
When comparing, the indexes are now sorted within the comparison results.
When using the Smart relationship finder from the tools menu, it did not draw the new relationships on the diagram. Fixed.
When importing from a SQL file, it ignored the Character Set. Fixed.
Fixed an issue where Collate was not generated for MySQL when generating scripts.
Data type conversion rules enhanced.
When data type conversion rules were used, it had a problem with the order in which the rules were saved. Fixed.
Fixed an issue with importing sequences from a SQL file. Cache, order and cycle settings were ignored. Fixed.
When dragging and dropping an object from the Object browser to a subdiagram, the object was not placed at the position of your mouse pointer. Fixed.
When importing from a SQL file, the constraint name for defaults defined in and ALTER TABLE statement was not imported. Fixed.
When you have a model based on a database type that does not support procedures (ie SQLLite), and you import from a database that does support procedures (ie Firebird) into the model, it gives an error. Fixed.
Fixed an issue when using multiple monitors.

Version 6.1.2

MySQL table type is now set as ENGINE = when importing MySQL 4.1 (or higher versionnumber) database.
Text objects and sub category objects get a shadow after exporting a diagram and/or generating a report. Fixed.
Fixed an issue with generating, comparing or altering a database when unique constraints or check constraints were deleted. These constraints are deleted when the Alternate keys option was turned off and/or when you selected not to generate/compare check constraints.

Version 6.1.1

Subcategories were not displayed in the list of objects under the add/remove objects tab in the Diagram properties dialog. Fixed.
"on update CURRENT_TIMESTAMP" for a TIMESTAMP column was not imported for MySQL databases. Fixed.
Attribute/column options for MySQL (such as "on update CURRENT_TIMESTAMP") can now be specified in the attribute's property editor in the Entity dialog.
Added support for generating attribute/column options for MySQL databases.
Importing MySQL databases. Defaults defined as an empty string ('') are not imported. Fixed.
When importing a database with column default containing a string with only spaces the default value was emptied. Fixed.
Fixed several formatting issues for imported database object comments.
Default values will not be unquoted automatically when the text was found in the file with the list of reserved words.
Generated SQL scripts were saved in UNICODE (introduced in v6.1.0). Files are now saved as normal text files again.
When importing MySQL databases, table comments could include storage settings when table type is INNODB. Fixed.
Reintroduced the "-generate" command line option.
Import of MySQL SQL files. ON UPDATE CURRENT_TIMESTAMP attribute option now imported.
Import of SQL files. Fixed several issues when removing comments in SQL code.
Import of SQL files. Foreign key constraint could not be imported when the table definition of the parent table appeared later in the file. Fixed.
Report generation. Column names for default value constraints were missing in the list of constraints. Fixed.
MySQL database generation. INTEGER(10) was automatically generated as INTEGER. Fixed.
Fixed an issue with changed sequences when updating your data model after comparing it to a database or SQL file.
MS SQL Server database generation. XML(CONTENT table.column) was exported as XML(CONTENT .). Fixed.
Comments in SQL code option in the Compare options dialog was not saved and not used. Fixed.
Added a default filter (*.sql) to the Open file dialog in the Compare options dialog.
The SQL file you selected in the Compare options dialog in a previous compare session is now remembered.
You can now start the Smart Relationship Finder for existing projects. Tools | Smart relationship finder...
Extended the number of available paper types for the diagram window in the Page settings dialog.
Fixed a printing bug when selecting a paper type in the printer dialog that was not in the list of available design time paper types. From now on, you can select all paper types that are supported by the selected printer.
Database alter scripts. Fixed an issue with a missing drop and create statement for foreign key constraints when the parent table changed.

Version 6.1.0

Improved Smart Relationship Finder. Smart Relationship Finder now also finds identifying relationships.
Improved Smart Relationship Finder. New relationships found by the Smart Relationship Finder will now get names based on the project's name templates.
When printing a model in landscape, it always printed as portrait. Fixed.
When printing a model, and Landscape was used with 'fit to print', then the result was not correct. Fixed.
When using the report generator, it did not show the default value of an attribute.
When using the report generator and selecting "Only objects of active diagram", then the ER diagram in the HTML result is non clickable. Fixed.
Code editor cannot be minimized anymore.
Code editor now has horizontal and vertical scrollbars.
When using a single monitor after using multiple monitors, it looked like the application froze when a dialog was opened. Fixed.
Fixed a memory leak when using the undo functionality.
When converting a database to a Firebird database, all VARCHAR columns where converted to VARCHAR(40). Fixed.
Fixed an issue with default values of domains. Default value was added to the column definition when generating the database.
When environment does not use shadows, and Export as image is used, then shadows never appeared in the image. Fixed.
When using the Query builder, it did not use schema names. Fixed.
Tabsize in the code editors changed from 8 to 4.
Added support for defining, forward engineering and reverse engineering clustered or nonclustered primary key constraints for MS SQL Server.
When using the undo function, it could result in duplicate id's for objects. Fixed.
Added horizontal scrollbars to the listboxes with table names in the Select tables to import dialog.
Fixed an issue with missing help text in the Schema manager dialog.
Importing SQL files. Fixed an issue with multiline and inline comments.
Importing SQL files. Added support for the primary key constraint's clustered property.
Importing SQL files. Fixed an issue with replacing the name of a view, procedure or trigger. When a schema name was found in the code it was not replaced correctly.
Importing SQL files. Quoted strings in SQL code of views, procedures and triggers are now correctly dequoted when needed.
Database/model compare. Compare options now displayed in a tree.
Database/model compare. Added the option to ignore check constraints.
Database/model compare. Added the option to ignore default values.
Database/model compare. Added the option to ignore triggers.
Database/model compare. Added the option to ignore non key indexes.
Database/model compare. Added the option ignore comments in SQL for views, procedures and triggers.
Database/model compare. Added the option auto-format the SQL code for views when comparing a database to a model.
Altering MS Access database fails when the table was used by another database object. Removing and recreating all foreign key constraints fixes this.
When comparing a MySQL data model to a database, the length value for integer data types is ignored when the length is the database's default length. Implemented for INTEGER, SMALLINT and TINYINT data types.
Improved comparison of check constraints. We get better comparison results when sorting column and table check constraints on the name of the constraint.
Added case insensitive comparison of MS SQL Server data types with length set to "MAX".
Fixed a problem for comparing a data model to a database and then updating it. Problem could occur when target DBMS does not support domains and the model contains domains. Problem only occurs when data type display level was set to show domains in the diagram.
When importing a database, the name of an object will be replaced with a variable/template in the code of a view, procedure or trigger. Now, only the first occurrence of the object name will be replaced.
When importing a PostgreSQL 8.3 database, some procedures were imported twice. Fixed.
View code is now automatically formatted when importing MySQL databases.
View code is now automatically formatted when importing PostgreSQL
Importing views, procedures and triggers from MS SQL Server removed leading Tabs. Fixed.
For MS SQL Server 2005 and 2008 it only imported schema names for domains if the domain was in schema 'dbo'. Fixed.
Generate database and alter database options in the Generate database dialog now displayed in a tree.
Fixed an Out of memory issue when generating/altering very large databases.
Performance improvements when generating/altering databases.
Generate database/alter database. Added the option to ignore check constraints.
Generate database/alter database. Added the option to ignore default values.
Generate database/alter database. Added the option to ignore triggers.
Generate database/alter database. Added the option to ignore non key indexes.
Fixed an issue with the generation of SQLite primary key autoincrement columns.
Help function was not working on the Alter database dialog. Fixed.
Quotes were removed from index expressions when generating a database. Fixed.
Commands to change an existing foreign key definition were missing when the old and new table had no other differences. Fixed.
When generating create/drop scripts it did not use schema names when using domains. Fixed.
When generating database scripts and triggers, procedures or functions have no code, then the empty triggers, procedures or functions will be ignored.
No SQL was generated for Informix, Pervasive, SQLite and Sybase databases. Fixed.
When there was an error while adding an object to an MS Access database, the log still mentioned the object was added. Fixed.
Name of foreign key constraint in the log now contains the name of its child entity.
Primary key constraint options were not generated for MS SQL Server databases. Fixed.

Version 6.0.0. Changes Compared to V5

Reverse Engineering

When importing a database that supports schemas, you can choose to automatically create a subdiagram for each schema and add imported schema objects to the approriate subdiagram.
Added the option to ignore indexes on keys when reverse engineering a database. You can set this option in the Import database dialog.
Import attribute options for MS SQL Server.
Import index options for MS SQL Server.
Added MS SQL Server 2008 support.
System sequences are no longer imported for Oracle databases.
For some data types a wrong value for length of non-numeric data types was imported. Fixed.
DB2 system schemas are not imported anymore.
Short object names in code of views, procedures and triggers wrongly replaced by variables (e.g. %viewname%). Fixed.
Added support for reverse engineering unicode SQL scripts.
Added schema/owner support to the SQL parser that is used when reverse engineering SQL scripts.
Added support for PostgreSQL 8.3.
New faster and more reliable driver used for connection to PostgreSQL databases. DLL in bin folder are not needed anymore.
PostgreSQL: Text "::regclass" in default values and check constraints no longer imported for PostgreSQL.
Added functionality to import attribute options.
Added functionality to import index options.
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.
InterBase+Firebase: Combined trigger events like "BEFORE INSERT OR UPDATE" or "AFTER INSERT OR DELETE" now imported when reverse engineering InterBase or Firebird databases.
Redesigned Import database dialog.
Selection of objects to generate now stored.
When importing SQL files, domains with names starting with a "N" were not imported correctly. Fixed.
Expression for computed fields was not imported correctly when reverse engineering a SQL file.
Importing SQL files. Missing schema/owner name when a table name is similar to the schema name. Fixed.
Descriptions/comments not found when importing MS SQL Server SQL file. Fixed.
Importing SQL files. Terminator (GO) at the end of the SQL code for MS SQL Server triggers and procedures was not always deleted from the code. Fixed.
Importing SQL files. MS SQL Server triggers and procedures created with procedure "dbo.sp_executesql" were not found. Fixed.
Importing SQL files. Import fails when script contains definitions for indexes on views. Fixed.
Importing SQL files. Added support for importing collation settings.
Importing SQL files. Default values with brackets were not imported. Fixed.
Importing SQL files. Fixed an issue importing references to domains when domain names included schema name and object name.
Importing SQL files. Fixed an issue with importing XML types.
Importing SQL files. Added support for importing domains created with the CREATE TYPE command.
Importing SQL files. Removed superfluous messages about missing check constraint clauses from the log file.
Importing SQL files. Constraint name for default not found in column definition. Fixed.
Importing SQL files. Removed superfluous brackets from check constraints in MS SQL Server SQL files.

Forward Engineering and Altering Databases

New. Generate an alter/update database script for differences between your data model and a live database (or SQL script).
Added the option to ignore indexes on primary keys, foreign keys and/or alternate keys when generating and altering databases.
Added conditional generation functionality. This lets you generate selected parts of your data model. You can define the generation directives that must be used for schema generation. You can use generation directives in code of database objects.
Redesigned alter script generator. The new alter script generator fixes some object dependencies issues and generates smaller and more reliable alter scripts.
New generate database and alter database options. New options enable you to ignore indexes on keys, ignore constraint names (for primary keys, foreign keys etc), ignore descriptions, character sets, collation settings, etc. when generating create or alter scripts.
When generating or altering a database, default values for string and date data types were automatically quoted when the default value did not contain a reserved word. DeZign for Databases now does not quote the default when it contains a function like for example TO_DATE.
Fixed a problem with a wrong drop order of tables in the generated drop script. This could occur when not all tables were selected in the Generate database dialog.
Selection of objects to generate has been enhanced. You can now select individual constraints, indexes, views, procedures, domains and sequences.
When generating a MS Access 2007 database, it created a *.accdb file but used the JET engine. It will now use the ACE engine.
MS Access 2007 password was ignored. Fixed.

Comparing Data Models/Databases

New. Compare your data model to a live database or a SQL script, view and select the differences you want to update in the database. Generate an alter/update database script for the selected differences.
Improved routine to automatically detect and map renamed database objects such as entities, attributes etc. is used when comparing data model and database.
Added compare data model versions functionality for dBase, Paradox, DBISAM and FoxPro projects.
Added compare and update model from database functionality for dBase, Paradox, DBISAM and FoxPro projects.
Added the option to sort on object type in the comparison results dialog.
New comparison results summary dialog. This dialog will be displayed after comparing a model with a database.
Added the option to ignore indexes on primary keys, foreign keys and/or alternate keys when comparing models/databases.
Readability of the differences between objects in the comparison results dialog has been improved.
New. When no relationships are defined in your database and you compare this database to your model, you are asked whether you want to maintain the relationships in your data model.
New compare options. Define what you want to see as a difference when comparing data models and databases. New compare options enable you to ignore indexes on keys, ignore constraint names (for primary keys, foreign keys etc), ignore descriptions, character sets, collation settings, etc.
Improved readability for HTML differences reports. Added linebreaks to long lines.

Collaboration

Added compare and merge projects wizard (File | Compare and merge projects).

Modeling

New Note property for all database objects. Note can be used to describe the object. The note contents will not be changed when you synchronize your data model with the database.
New Update indexes on keys dialog. You can now add, delete or update indexes on keys. You can do this individually for primary key indexes, foreign key indexes or alternate key indexes. For new key indexes you can define a name template.
Added support for database-independent data models. When you work with database-independent data models, you select a target DBMS when generating, altering or comparing your data model.

Diagramming Environment

Entities, text areas and group boxes now all have a gradient. This gradiency will be turned on by default. You can define the gradient setting for each subdiagram in the Display preferences dialog.
Flexible line routing. Added two new line routing styles: C-style and U-style line routing.
New default color for new diagrams.
The page divider does not honor the "Landscape" page orientation in the diagram window. Fixed.
You can now define the page settings for the diagram window in the Page setting dialog (File | Page settings).

User Interface

New undo functionality lets you go back. Undo entity changes, diagram changes, object renaming and more.
Added the option to display schema/owner names in the Object Browser. You can change this setting in the Options dialog.
Added the option to insert an attribute in the Entity dialog.
Generate database and modify database setting have been removed from the Project options dialog. These settings are now available in the Generate database dialog and the Alter database dialog.
New Progress dialog.
Begin and end database scripts have been removed from the Project options dialog. You can now edit these scripts in the Begin/end database scripts dialog (Dictionary | Begin/end database scripts).
Fixed an issue with opening the Entity dialog in the indexes, triggers or constraints tab when no indexes, triggers or constraints were defined.

Reporting

Tables in PDF reports were align to the right border without a margin. Fixed.
Redesigned Generate reports dialog. New options allow you to select the fonts, colors and elements to include.
You can now save your report settings to a reusable template.
New title page for MS Word and PDF reports. You can define the contents of title page in the Report dialog.
Improved handling of long lines and long words for MS Word and PDF reports.
Performance improvements for generating reports of large models.
Fixed an out of memory issue when generating large PDF reports.
Improved quality of included image of diagram in MS Word and PDF reports.
To avoid that images of diagrams become too large, they are automatically resized to a proper size now.

Model Validation

Check model before generating the database option added. This option is available in the Generate database dialog.
Performance improvements for validating data models.
Removed the question whether you want to give nameless constraints a name when generating and altering your database.
Validation error when a table with the same name appeared in more than one schema. Fixed.
Constraint names are now also checked for uniqueness when validating your model.

Miscellaneous

Performance improvements for loading projects. Up to 4 times faster.
New data type conversion rules editor. You can open this editor through the menu: Tools | Resources.
The file format of the .dez file has changed to accommodate new features.
When adding a table constraint in the Entity dialog the name template for table constraints was not assigned. Fixed.
Added support for foreign key constraint options support to postgreSQL 8 and 8.3.
Added support for constraint options for unique constraints in Oracle 10 databases.
Improved the description of Default and Not Null constraint values in reports.
Added a vertical scrollbars to the table options fields and the primary key constraint options field in the entity dialog.
You will now see a message when the alter database operation failed.
Fixed problem w.r.t. Windows Data Excecution Prevention (DEP).
Template for Not null constraint names changed to 'NN_%table%_%column%'

Discontinued Functionality

Removed ElevateDB support.
Removed NexusDB V2 support.