What's new in DbWrench 1.6.2:

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.

What's new in DbWrench 1.6.1:

· 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.

What's new in DbWrench 1.5.2:

· This release did not focus on any one or two large items, but instead addressed several smaller outstanding items.
· These included improved font rendering on LCDs, improved SQL code generation, and bugfixes for PostgreSQL 8.3 support.
· There were several other improvements to usability and appearance, along with several significant bugfixes.

What's new in DbWrench 1.5.1:

· This release focuses on improving Unicode support and the appearance and usability of several panels.
· DbWrench now supports Central and Eastern European characters within the application itself and in the HTML database documentation it generates.
· The appearance and layout of several panels has been changed, with goal of improving usability.