- XERCOMPARE.EXE - comparator of 2 XER models (more info)

- Support of DB2 and Informix and Mimer

- Graphical object for database object VIEW

- Model settings: Hide relationships to another submodel

- Escape physical names in Show SQL as well as in SQL script (model settings, optional)

- Default owner of the tables (model settings, optional)

- Align entities (menu Align)

- The function "Delete and map" is used to remove the duplicate attribute which has been introduced into the table by some relationship, and to remap the relationship to another attribute which exists in the table.

- You can change color of a single entity (context menu on entity object), or change color of group of objects (menu Edit - Colors of selected objects)

- The synchronization between following settings is ensured in 2.3.3:
    - relationship cardinality at the parent side
    - combobox no nulls / allow nulls
    - NN flag at the appropriate FK attributes
(e.g. if you change the relationship cardinality on the parent side from "1" to "1 or 0", the NOT NULL flag is automaticaly switched off at the appropriate FK attributes in the child entity. Similarly backwards.)

The version 2.3.4 of Data Modeller will feature the new redesigned model of attribute repository. The idea of the former model of the repository was that every logical attribute (eg. customer_id) is always the same attribute in all the tables, even in the tables where it has been introduced by a relationship.
This is not always good. Take for example default values. If there is default value max+1 defined for the original PK attribute in the source table, there usually should not be the same default rule defined for this FK attribute in the target table. This can be solved by using derived attribute in the current version.
The new repository will be designed the way that every attribute is just in one table which will eliminate the problems of setting up the advanced properties of attributes.
There will be also a new and much requested feature added - the naming of PK and NN constraints.