Changes from build 109 to build 110
Enhancements
- The (self-written) Windows launcher has been dropped and replaced with executables from Winrun4J, including suppport for 64bit executables (thanks to Markus for testing this).
- EXPLAIN is now supported for auto-completion (PostgreSQL, Oracle, MySQL)
- The DbExplorer will now show the status of Oracle stored procedures.
- The DbExplorer now includes information about partitioned tables and indexes for Oracle in the generated source.
- The possibility to influence the generated INSERT statement for WbImport is now available as a commandline parameter (previously this was only possible through a property in workbench.settings).
- Two new options for the SQL Formatter are available that control the placement of the comma when line breaks are inserted. Thanks to Andreas for this patch.
- The option "Allow empty line as statement delimiter" has been moved into the settings dialog and is now also being used when detecting the current statement in the editor.
- The font size of the editor can now be changed dynamically using Ctrl-Numpad Plus/Ctrl-Numpad Minus or via the scroll wheel of the mouse (holding down the Ctrl Key). The font size of a result table can be changed using the scroll wheel or through the context menu in the table header.
- It is now (optionally) possible to modify the text in the editor while a statement is running. Statement and error highlighting will not be available if the editor contents was modified during execution.
- When the option "Show Max. Rows warning" is enabled, the warning is now shown using an icon in the tab header (instead of changing the color).
- The join condition inside a JOIN part of a SELECT statement can now be generated automatically (if the tables involved are using foreign keys) using SQL -> JOIN completion
- Primary key columns are now shown in bold face in the auto-completion popup window. If comments are defined for columns, tables or view, these will be shown as a tooltip for the entry in the popup
- A new parameter -skipTargetCheck is available for WbCopy to disable checking of the target table. This is useful if the target table is not visible by the JDBC driver (e.g. temporary tables for Informix)
- A new parameter (-tableType) is available for WbCopy to control what kind of table is created when using -createTarget. The parameter value selects a SQL "template" that is defined in workbench.settings
- When using WbExport and -quoteAlways=true, null values are no longer escaped. The parameter can now be use with WbImport to distinguis between null values and empty strings.
- The escaping of embedded quotes can now also be selected when using "Save Data as" or "Import file".
- When connected to an Excel Spreadsheet, [] are now also recognized as quote characters (to allow a semicolon in a "table" name).
- The JDBC driver templates can now be loaded from an external a file named "DriverTemplates.xml" that has to be stored in the directory where the jar file is located.
- When starting the console mode without specifying a password or when using a profile without a password, the application now prompts to enter a password
- A new option "Connection Timeout" has been added to the connectioin profiles.
- A new option to log all executed SQL statements to the logfile has been added (Tools -> Options -> General -> Log all SQL statements).
- The DataPumper now remembers the settings for importing text or XML files
- A new SQL formatter option has been added, to insert a space after a comma when processing IN (...) lists.
- The "Delete data" dialog in the DbExplorer now correctly commits for DBMS where TRUNCATE is transaction safe. The CASCADE option for PostgreSQL is also supported.
Bug fixes
- Changing the font size in the editor would corrupt the display of the caret
- When exporting data, two tabs could not be defined as a separator (only a single tab)
- Oracle Procedures with the status "INVALID" where not shown in the DbExplorer
- The JOIN completion did not always detect the FKs correctly.
- Cancelling an import did not rollback the changes.
- When reloading the table list in the DbExplorer while "editing" mode was active, the table list was not retrieved correctly.
- Using WbCopy with schema qualified table names did not work properly when the target connection was using a different default schema.
- The rowcount in the statusbar was not always showing the correct values when more than one result was present
- JOIN completion did not work
- WbCall did not work for functions that were using OUT parameters
- When using a query as the source for WbCopy that used column aliases between databases that store object names in different case a wrong isnert or update statement was created
- When changing the current database, the object cache was not updated correctly
- "Filter by selected value" did not work for boolean columns
- For PostgreSQL, columns defined as bit(x) with x > 1 where not displayed correctly.
- When running a statement there was a built-in limit on 15 warnings that would be displayed by SQL Workbench. That limited the output of messages with RAISe NOTICE to 15 as well in PostgreSQL.
- The datatype for parameters in Oracle stored procedures was not always displayed correctly.
- When selecting JdbcOdbc bridge as the Driver class, SQL Workbench incorrectly showed an error message that the driver could not be found.
- Copying a table's column definitions into the clipboard did not work.
- When using WbCopy and -createTarget with a fully qualified table name (otherschema.sometable) the table was not created in the specified schema
- Postgres DOMAINs where not displayed if the DOMAIN was created in a schema that is not in the schema search_path
- A selection of '*' in the DbExplorer's schema selector was not restored if "Remember DbExplorer schema" was enabled for the workspace
- -quoteCharEscaping=duplicate was not working for WbImport if a quote character other than " was used.
- Procedures were no longer displayed in DbExplorer for DB2.
- A workaround for an Oracle driver bug was implemented, where the datatype for TIMESTAMP(3) was reported incorrectly.
- The generated XML content was not valid for ODS or OpenXML export if the generating SQL contained characters that needed escaping in XML.
- Statements where not closed properly when retrieving Oracle Object type information.
- Oracle RAW columns were not displayed correctly if the automatic data conversion was turned on.
- Using WbDataDiff (and WbSchemaDiff) with the -referenceSchema parameter or selecting specific tables for comparison did not work.
- Optimize column width calculated a width that was too wide (and increased with the total number of columns)
- When using the DataPumper to import xml files, non-standard column names were not quoted properly in the UPDATE statement
- When saving and loading the same file an empty line was appended each time the file was loaded.
- The console interface was no longer working.
- Importing multiple zipped text files into tables with BLOB columns did not work when using a batch size > 1
- When copying data to the clipboard, the data was always copied in the column order as retrieved from the database. If the column order was changed, this was not reflected in the copied data
- If a stored procedure in Oracle with the same name existed as a standalone procedure and a packaged procedure, the procedure columns for the standalone procedure where not displayed correctly in the DbExplorer
- When using the new lobsPerDirectory parameter for WbExport, the directory numbering did not restart with a new table.
- WbSchemaReport created invalid SQL if column names contained characters that needed a replacement with an XML entity.
The full release history is available at the SQL Workbench/J homepage