SQL Workbench/J - Known bugs

In the DbExplorer's "Procedure" tab, functions defined in Oracle packages are no longer listed. (fixed in 108.1)
The display of triggers in PostgreSQL is no longer working if the trigger does not have a comment.
As a quickfix, please download this XML file and copy it to your Configuration directory. (fixed in 108.2)
When exporting TIME columns (including copying to the clipboard) the value was converted to a date, not a time (fixed in 108.2)

When upgrading from an earlier build to 107, the internal properties for the DDL generation (in DbExplorer) are not always migrated properly. Please start SQL Workbench/J with the parameter -Dworkbench.db.resetdefaults=true to reset the properties and fix the problem. Use -J-Dworkbench.db.resetdefaults=true when using the Windows launcher (fixed in 107.1)
When moving the DbExplorer to a position other than the last, the tabs will not be restored correctly when the workspace is loaded the next time (fixed in 107.1)
When editing the data of columns with the data type inet, macaddr or cidr in PostgreSQL, wrong update statements are generated when the changes are saved to the database (fixed in 107.1)
On MacOS starting SQL Workbench through the application icon does not work if Java 5 and Java 6 are installed together The stub that starts the Java virtual machine seems to pick the wrong Java installation (fixed in 108)

To fix this problem, copy the stub from the Java 6 application into the SQL Workbench/J directory using the following command (on a single line)
cp /System/Library/Frameworks/JavaVM.framework/Resources/MacOS/JavaApplicationStub /Applications/SQLWorkbench/SQLWorkbenchJ.app/Contents/MacOS/