3. Change log
Prev |  | Next

## 3. Change log

Changes from build 129 to build 130

#### Enhancements

- It's now possible to search the settings dialog for specific labels.
- Storing a workspace in a directory, rather than a ZIP archive (.wksp) is now supported.
- Storing macros as SQL scripts in a directory, rather than an XML file is now supported.
- For DB2 (LUW), tablespace information is now included in the generated DDL for tables.
- WbSchemaDiff now writes a drop-constraint tag for indexes supporting unique constraints.
- For DB2 (LUW), the table for a trigger was not shown in the DbExplorer's trigger list
- For PostgreSQL, COPY ... FROM STDIN did not work if no row data was provided
- POI 5.2 introduced new memory limits when reading XLSX. The built-in limits have been increased and can now be configured.
- It's now possible to include column comments in the HTML output of "Save Data As" and "Copy data to clipboad".
- Code completion now shows comments for tables and columns.
- Connection profile groups can now be nested.
- WbExport will now generate a unique sheet name when exporting to an Excel sheet and using -append and no sheet name was specified.

#### Bug fixes

- The space for the execution time in the status bar was incorrectly calculated with some fonts
- If macros where filtered when saving them, only the filtered ones were saved (regression from 129.6)
- The parameter -ignoreMissingColumns was not honored by WbImport when importing Excel files
- Selected rows were no longer highligted in a result grid (regression from 129.5)
- Connection profiles could not be loaded if the stored list of expanded groups contained a non-existing group.
- Column comments were always retrieved for queries, even if disabled.
- On Linux, external formatters could not be called due to incorrect quoting of the executable (Issue #39)
- For PostgreSQL, columns with the data type time could not be exported or copied
- Variables defined through WbVarDef in a "after connect" script were not set when using "Separate variables per window"
- The SQL formatter did not treat CREATE OR REPLACE statements properly
- Formatting statements using CREATE OR REPLACE TABLE was not correct
- Loading of profiles did not work if the last profile selected contained a / in its name.
- The macro popup window did not show the macros any more.
- For MySQL, the DDL for columns with the data type binary(n) was not generated correctly
- For PostgreSQL, partitioned tables could not be dropped through the DbExplorer or DbTree
- Loading of old profiles didn't work if some (or all) were still using the "Default Group"
- When using real tabs in the editor, the position of the following characters wasn't calculated correctly
- The statements in the script from "Show script" when using the DROP dialog in the DbExplorer were not terminated with a semicolon.
- Table names that contain a dot (e.g. "some.table") were not handled correctly when generating queries for them.
- For PostgreSQL, retrieving event triggers did not work any more.

The full release history is available at the SQL Workbench/J homepage

Prev |  | Next
2. Software license | Home | 4. Installing and starting SQL Workbench/J