DbWrench Changelog

New in version 3.0.1

October 10th, 2013
  • General:
  • Further improvements to the memory footprint and memory usage of the application. Particularly for larger data models.
  • Diagrams:
  • A new table linking algorithm for diagrams. Tables are linked using right angle lines. Select Right Angle Connecting Lines strategy in the diagram edit panel.
  • Foreign key lines on diagrams can now be moved and positioned. Must set the link strategy of the diagram to the new Right Angle Connecting Lines strategy.
  • New rectangle fill algorithm for diagram table glyphs. Select the new Header Gradient Fill in the Misc tab of the Diagram Edit panel. Only the header and footer of each table is colored the rest of the glyph is white, which we think improves readability.
  • Details Panel is not automatically shown in the bottom of the application any more. Instead it is shown either by opening it explicity using the Windows menu or by clicking on the details icon in the top left corner of the table glyph itself. Then it will display in a popup dialog. It is hoped that this will keep more space open for viewing diagrams.
  • Table Data Viewer:
  • Table Data Viewer now shows only the first 1000 rows by default. Sometimes invoking it with large tables caused timeouts.
  • The data row editor of Table Data Viewer had a bug which did not allow entry of negative numbers. This is now fixed.

New in version 3.2.2 (December 6th, 2012)

  • This version focused on reducing the application memory footprint, in particular regarding the design diagrams.
  • Also, rendering performance and responsiveness of diagrams was improved.
  • Other bugs were addressed too.

New in version 3.2.0 (May 8th, 2012)

  • Diagram click actions have been implemented.
  • These allow database tables, columns, notes, etc. to be edited directly from the diagram.
  • Support for unique constraints has been added.
  • The formatting of generated DDL SQL scripts and tree structure have been streamlined.
  • There were also other enhancements and resolutions for several key bugs.

New in version 2.1.0 (August 16th, 2011)

  • The main features of this major release include support for Oracle databases, new printing and print preview features, upgraded JDBC drivers for all the supported database management systems, and updated support for the latest versions of these database management systems.
  • In addition, the user interface look and feel has been enhanced and numerous bugs have been addressed.

New in version 1.6.6 (October 13th, 2010)

  • This version focused on a small number of fixes to almost all parts of this application. This includes the ability to specify optional parameters for database connections.
  • This should help with connecting to SQL Server named instances and specifying Unicode options for MySQL connections.
  • In addition, some reverse engineer changes were made to comply with the new escape character requirements for PostgreSQL 9.
  • Other significant changes were made to the custom data editing panels, making their layout more consistent across the various looks and feels of the various platforms DbWrench runs on.

New in version 1.6.5 (August 25th, 2010)

  • This version focused on adding support for fairly common database features that DbWrench did not support previously.
  • The new features include support for custom data types (or user defined types), unique constraints, and MySQL routines (procedures and functions).
  • The secondary focus of this release was to fix a bunch of bugs related to the user interface.

New in version 1.6.3 (March 4th, 2010)

  • General:
  • Sort Columns panel now has Up and Down buttons as an alternative to using drag and drop.
  • Removal of most elements no longer shows a Delete Confirmation message box since the removal of these elements is undo-able.
  • Renaming a schema by double clicking on it's tree node resulted in it's schema objects being lost. This is now fixed.
  • If the database design does not use sequences or procedures the folder nodes of these items can be hidden. Select this option in the Database Explorer section of Preferences.
  • General GUI:
  • Database Explorer tracks which nodes were expanded prior to exiting and re-expands them the next time DbWrench is started.
  • DbWrench tracks which editors and diagrams were open when it was closed and only re-opens those editors and diagrams the next time it is started.
  • Undo/Redo toolbar is no longer embedded within the File toolbar. It is now it's own distinct toolbar.
  • Undo/Redo can be performed using Ctrl+Z and Ctrl-Y respectively.
  • Editor tabs can be closed using Ctrl-W.
  • The DbWrench Log window shows up in front of the Forward Engineer Log window by default.
  • Database Properties panel now has an Update button which can be used to make sure that edits are applied.
  • Trigger Edit panel incorrectly displayed in a pop-up dialog, now it displays properly as a tabbed editor.
  • New mnemonic keys to navigate Table Details panel's tabs.
  • Diagrams:
  • DbWrench now supports Notes in diagrams.
  • DbWrench now supports Zones in diagrams allowing for more visual grouping of tables.
  • The Delete key can be used to remove foreign keys directly from diagrams.
  • Diagram glyphs have gradient backgrounds now.
  • The highlight border for selected table glyphs and foreign key links is thicker and brighter making it easier to see which diagram items are selected.
  • When diagram glyphs are being dragged to a new location the mouse cursor displays a proper Move cursor.
  • Auto-layout of tables on a diagram has been improved to make the layout more balanced with fewer large empty areas.
  • Link corners drawn on Key to Key link strategy diagrams are now rounded making it easier to see the direction of link when several links overlap or cross over.
  • Ctrl++ and Ctrl-- can now be used to zoom in and zoom out diagrams, respectively.
  • Reverse Engineering:
  • Errors were generated if PostgreSQL table names contained 'pg_' somewhere other then the start. This is now fixed.
  • Cosmetic and layout improvements to Reverse Engineer panel.
  • Forward Engineering
  • Enclosing mixed case entity names in double quotes for PostgreSQL are now supported. Ensure this option is selected in Preference's PostgreSQL options.
  • Script Explorer tracks which nodes were expanded prior to script recalculation and re-expands them after the calculation.
  • SQL Editors:
  • Layout improvements to SQL Results panel.
  • Database Documentation:
  • 'DbWrench' is removed from the header in HTML docs. Now it's displayed in the 'Documentations Created...' line.
  • Cosmetic and layout improvements to Database Documentation panel.

New in version 1.6.2 (November 12th, 2009)

  • General GUI:
  • The Details panel did not update when the Database Explorer tree nodes were navigated to using keyboard actions, only with mouse clicks. Now it updates with either type of action.
  • Glyphs can no longer be moved off the screen (to negative coordinates), preventing them from becoming unretrievable.
  • If an entity editor panel had an asterisk in the tab title (see Figure 1), that editor panel would not be re-located and a duplicate editor panel would be opened. This is now fixed.
  • DbWrench Output Log window was erroneously displaying v1.6.0, even with newer versions. This is now fixed.
  • Diagrams:
  • Can now specify that a diagram display only primary key and/or foreign key columns for tables, in addition to displaying all table columns. See Figure 2.
  • Diagrams didn't retain their last viewport position when switching between diagrams, this is now fixed.
  • Changes made to diagram properties are now undoable.
  • The diagram redrawing process has been made slightly more efficient and faster.
  • Diagram edit panels, when displayed from tree nodes, wouldn't default to (remember) the last used font and link strategy. This is now fixed.
  • Diagram edit panels didn't default to (remember) previous settings of 'Display' values, this is now fixed.
  • Reverse Engineering:
  • Reverse engineer of extremely large MySQL tables would hang sometimes, this is now fixed.
  • Reverse engineer of PostgreSQL 8.2 and newer sometimes would miss a pair of parenthesis in the default field of a column. This is now fixed.
  • Reverse engineer of PostgreSQL databases would place an unnecessary set of brackets around negative numerical default values. This is now fixed.
  • If the source code of a stored procedure specified a different schema than the schema containing the stored procedure (within DbWrench) a null pointer error occured. This error is now handled.
  • An error occurred if two entities of different types (i.e. views and stored procedures) had the same name and were in the same schema. This is now fixed.
  • If an error occurred during reverse engineer, the reverse engineer status bar would reset and erroneously display 'Reverse Engineer Started', this is now fixed.
  • Reverse Engineer status bar would display 'Reverse Engineer Started' when more detailed status messages were available, this is now fixed.
  • Forward Engineering:
  • Unlimited VARCHAR for PostgreSQL can now be created by setting the datatype to VARCHAR and not specifying a length, resulting in a VARCHAR(). See Figure 3.
  • In Reverse Synchronize, indexes were added before the columns they depended on were added, resulting in an error message. Now the columns are added first.
  • Table Data Viewer:
  • Data grid is cleared while a data refresh is in progress.
  • When a refresh of data fails, the 'Data Retrieval Error' message for the failure is now more informative.
  • Database Documentation:
  • The Clear button has been removed from the Database Documentation panel to save space, since the documentation Log clears automatically when appropriate.

New in version 1.6.1 (September 9th, 2009)

  • This release focused on minor enhancements and feature implementations.
  • Some of these new enhancements include object counters for folder nodes in Database Explorer, improved error handling during reverse engineering, improvements to the responsiveness of various panels, and improved storage of table data.
  • Also, there were several smaller improvements to the user interface.