Version 3.3.41 – 2024.04.26

Fixed bugs

• An issue where all created diagrams were not displayed when creating multiple diagrams using the diagram creation wizard has been corrected.
• An issue where long notes were not sorted in the model view after adding them to the diagram has been fixed.
• The problem in which the value of the sort attribute among the additional attributes of an index could not be modified in Oracle DBMS has been fixed.
• The issue of duplicate creation of DDL for child node indexes when creating an XML index in SQLServer DBMS has been fixed.
• The problem in which DDL statements regarding physical properties are not generated for XML indexes with child node indexes in SQLServer DBMS has been fixed.
• The problem in SQLServer DBMS where DDL statements are created with blank spaces when table comments are blank has been fixed.
• The problem in SQLServer DBMS that DDL syntax is not generated depending on the view comment creation option setting has been fixed.
• The issue where foreign key indexes could not be reverse engineered in Oracle DBMS has been fixed.
• The problem that DDL syntax is not generated when setting the FK index creation option alone in Oracle DBMS has been fixed.
• The problem in Oracle DBMS that DDL syntax is not generated based on the value of the sort property among the additional properties of the index has been fixed.
• The problem in which DDL syntax is generated in Cubrid DBMS by linking the table comment creation option to the delimiter setting has been fixed.
• The problem in which DDL statements are generated even though there is no partition method setting value in Cubrid DBMS has been fixed.
• In Tibero DBMS, the problem in which DDL statements are generated for table and column comments even if the table creation option is not set has been fixed.
• In Tibero DBMS, an issue where DDL syntax was not generated for a trigger belonging to a table according to the trigger creation option has been fixed.
• The issue where the delete view trigger option could not be selected in Tibero DBMS has been fixed.
• The problem in PostgreSQL DBMS where schema comments do not generate DDL syntax according to the schema creation option setting has been fixed.
• The problem in PostgreSQL DBMS where DDL syntax for foreign key index comments is not generated depending on the foreign key index creation option setting has been fixed.
• In PostgreSQL DBMS, an issue in which DDL statements are generated for table and column comments even when the table creation option is not set has been fixed.
• The issue where DDL syntax is not generated when setting the primary key index creation option alone in PostgreSQL DBMS has been fixed.
• The issue where comment DDL syntax of tablespace is invalid in MySQL DBMS has been fixed.
• The issue in which DDL statements are not generated according to the Delete Check Constraints option in MySQL DBMS has been fixed.
• The problem in MySQL DBMS where the list of index type combo boxes does not change depending on the type of index has been fixed.
• The problem in which DDL syntax is not output depending on the values set in the Parser and Key block size properties among index properties in MySQL DBMS has been fixed.
• The problem in MySQL DBMS that DDL statements are not generated according to the value of the wait property among the physical properties of the table space has been fixed.

Enhanced Contents

• In DB2 DBMS, the “Create/Delete Unique Constraint Index” option has been removed and integrated into the “Create/Delete Unique Index” function.
• In Tibero DBMS, the “Create/Delete Unique Constraint Index” option has been removed and integrated into the “Create/Delete Unique Index” function.
• The “Create/Delete Unique Constraint Index” option has been removed from SQLServer DBMS and integrated into the “Create/Delete Unique Index” function.
• Since PostgreSQL DBMS does not support the oids property among the physical properties of tables after PostgreSQL12, the DDL statement has been improved to be expressed differently depending on the version selected by the user.

Version 3.3.39 – 2024.01.24

Fixed bugs

• Reverse columns that have a history of name changes among columns belonging to foreign keys in PostgreSQL DBMS Fixed an issue where foreign keys could not be configured during engineering.
• DDL for unique index or general index where Oracle or Tibero DBMS restrictions are not set. Fixed an issue where syntax could not be generated.
• When modifying the logical name, physical name, and method of an index in PostgreSQL DBMS, the logical name and physical name of the constraint The issue where physics name and physics properties could not be specified has been fixed.
• The problem in which the Deferrable and Deferred check states of Relationship (Foreign Key) > Physical Properties were not maintained in PostgreSQL DBMS has been fixed.
• An issue where DDL was not generated according to the specified options during forward engineering in PostgreSQL DBMS. Edited.
• In PostgreSQL DBMS, you can change the sorting method of the index column in the Table > Index > Index Column Properties window. The issue where settings could not be set has been fixed.
• eXERD Preferences > eXERD > Diagram Editor > Edit Automation > Compound Word > Smart option is specified When there is a column, the longer the logical name or physical name, the longer it takes to use the dictionary reverse engineering function or the function to find compound words. The problem has been fixed.
• The issue where some links in the help did not work has been fixed.

Enhanced Contents

• Tibero reverse engineering has been improved to proceed faster than before.
• Improved to allow reverse engineering of PostgreSQL to proceed faster than before.
• Improved to allow reverse engineering of SQL Server to proceed faster than before.

Version 3.3.37 – 2023.11.08

Fixed bugs

• Fixed an issue where an error occurred while reverse engineering TableSpace in Oracle DBMS.