SQL Workbench/J Change Log

This document only shows the release history for the last 10 releases.
The full release history is available at the SQL Workbench/J homepage

Build 110 (2011-02-13)

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.

Build 109 (2010-08-15)

Enhancements

• The context menu of the procedure list now has a new item "Put WbCall into..." (similar to the "Put SELECT into") for tables. Thanks Andreas for contributing this.
• When exporting LOB data into external files using WbExport, the generated LOB files can now be distributed over several directories to avoid directories with too many files
• WbExport now supports two new literal formats for PostgreSQL when exporting SQL statements using binary data (pgDecode and pgEscape)
• For MySQL table comments can now be shown in the DbExplorer by setting the property workbench.db.mysql.tablecomments.retrieve=true in workbench.settings
• WbDataDiff now outputs differences for foreign key in their own tag listing all FK columns instead of listing the foreign key as a modification for each column.
• A new option in the DataPumper is available to automatically select a matching entry in the target table dropdown when the source table is changed
• Changesets for WbRunLB can now also be selected by specifying an author (not only the ID)
• WbExport now only exports TABLEs (views, synonyms and similar objects where included by default until now). To include other types than tables, a new parameter -types has been added.
• When editing a value in the result set, the value can now be set to NULL (either through the popup menu or a shortcut)
• Sequences and UDTs in Derby 10.6 are now supported
• A new editor option to disable "Execute selected" when no text is selected is available.
• A new commandline option (-lbDefaults) is available to read connection information from an existing Liquibase defaults file
• Commandline options (e.g. for batch mode) can now also be stored in a properties file. A new option -arguments defines the file to be used
• For WbImport, select statements (referencing columns from the input file) can be defined in the -columnConstants argument. See the manual for details
• A new option (includeColumnComments) for WbExport is available to include column comments in the output (all formats except text files)
• A new command WbRunLB to extract and run the SQL statements from a Liquibase changeSet (<sql> or <createProcedure> tags) is available
• Window sizes and position are now stored separately per screen resolution
• When displaying the SQL for a view or table in PostgreSQL, associated RULEs are not included
• The quickfilter in the DbExplorer can now be changed to accept "normal" wildcards instead of regular expressions
• WbSchemaDiff now detects renamed foreign keys and indexes
• When using -continueOnError WbImport does not treat missing or empty files as an error, it only shows a warning.
• MySQL's syntax for changing autocommit mode is now also supported (SET AUTOCOMMIT = 1 instead of SET AUTOCOMMIT ON)
• A new command WbFetchSize is available to change the default fetch size of the current connection without the need to change the connection profile
• Workspaces loaded with "Workspace -> Load Workspace" are now added to a "Recent Workspaces" menu
• When an import with multiple files fails, the error message now includes the parameter to skip the successfully imported files, when re-running the WbImport command
• A new option to exclude tables for WbExport using -excludeTables is available.

Bug fixes

• The panel selection for "Put SELECT into" in the DbExplorer included DbExplorer panels if the DbExplorer was not at the end.
• For Oracle, overloaded procedures and functions (in packages) are now displayed correctly in the DbExplorer.
• For PostgreSQL 8.4 and above the source for procedures without parameters was no longer displayed.
• DESCRIBE did not longer work for Informix
• Fixed sequence, view and procedure display in the DbExplorer for DB2 on iSeries (AS/400)
• The source code for Postgres TYPEs was not show correctly.
• The source code for Postgres functions returning SETOF or TABLEs was not show correctly.
• WbDataDiff failed with no clear error message when the columns from the source table were missing in the target table.
• WbSchemaDiff did not work when indexes were included (-includeIndex=true)
• When the maximum number of backups for workspaces was reached, the newest backup was overwritten instead of the oldest
• Auto completion of column names did not work for table or column names that contained spaces (and thus needed qutoes)
• The width of the header was not evaluated correctly for all look and feels when optimizing column widths
• When initiating editing a column that is rendered as multiline column by using the DELETE key, a non-printable character was inserted into the text field
• When exporting text columns from PostgreSQL, they are now properly recognized as CLOB columns (e.g. for the -clobAsFile parameter)
• The SQL console did not start if a profile was passed (using -profile) on the commandline that did not exist
• Fixed some initialization problems with the DbExplorer which caused errors when using SQL Server with the Microsoft Driver
• The generated WbCopy command in the DataPumper was wrong, if * was selected as the schema
• Values of TIME columns were exported (incl. copy to clipboard) as dates
• When entering an invalid expression in the quickfilter of the DbExplorer, the filter was no longer working
• Postgres rules with the name _RETURN were not displayed in the DbExplorer
• For Oracle, WbCall did not work for stored procedures with ref cursors that were accessible only through a synonym
• Fixed a problem with an endless loop when displaying foreign key references when multiple FK constrained built a cycles
• Tried to make detection of Oracle packaged procedures more robust in WbCall
• The reverse engineered source code for views contained a wrongly placed semicolon
• Cancelling a connect due to an unsaved file did not work
• WbRun was always using the alternate delimiter to parse the file
• The tooltip for a column heder was not displaying the correct information if the column order was changed using drag and drop
• WbCall did not work with Oracle functions returning a REF CURSOR
• When the option "Confirm tab close" was enabled, no confirmation was needed when using "Close other tabs"
• The display of trigger functions in Postgres that did not have a comment was not working
• Specifying a config directory using -configDir that needed quoting did not work
• Statements with character literals and embedded single quotes (e.g. ' test ''') were not formatted correctly
• Oracle Package functions were no longer displayed in the procedure tab of the DbExplorer
• The "Object Info" function did not display information about TYPEs (e.g. Oracle, Postgres)
• For Oracle object TYPEs, member variables declared with the data type "NUMBER" where not displayed correctly

Build 108 (2010-04-05)

Enhancements

• The argument parser for Workbench specific commands has been changed in order to recognize empty values (e.g. -replaceWith=' ') Existing scripts should work, but it could be that some combinations of parameter values are not covered by my tests. So please verify that your scripts still work with the new version.
• A new option for WbExport (-replaceValues) is available to replace text (using regular expressions) in all character columns during export.
• For Oracle the DbExplorer will now also show OBJECT TYPEs
• For DB2 the list of procedures is no longer retrieved through the driver, so that functions will also be shown in the DbExplorer.
• When using a JDBC 4.0 compliant driver the table definition in the DbExplorer will now also display the IS_AUTOINCREMENT flag. (with pre-JDBC 4.0 drivers the column will always display NO)
• For SQL Server, column and table remarks that are defined through sp_addextendedproperty() are now retrieved and displayed in the DbExplorer.
• Computed/Virtual columns are now shown in a table's SQL for Firebird, H2 Database, HSQLDB 2.0, Oracle 11g, DB2 (LUW) and SQL Server 2005
• The DbExplorer will now show the (correct) source code for user defined AGGREGATEs in PostgreSQL
• When running stored procedures with parameters, the name of the parameters are now shown in the parameter input dialog if available. If running stored procedures with out parameters, the result tabs will be named after the parameters now (if the parameter names are available)
• The minimum version for POI (XLS export) has been raised to 3.5 in order to support Microsoft's new OfficeOpen XML Format. Therefor the naming of export types has been changed: xls still writes the old (Pre 2003) binary format, xlsx now writes the new OOXML format (Office 2007) and the (new) type xlsm writes the Office 2003 XML format (xlsm is equivalent to the previous xlsx type). To be able to use the new xlsx format, additonal libraries (apart from poi.jar) are needed: poi-ooxml.jar, dom4j-1.6.1.jar, geronimo-stax-api_1.0_spec-1.0.jar, ooxml-schemas-1.0.jar and xmlbeans-2.3.0.jar
• Two new options for spreadsheet export have been added. An option to turn on the auto-filter for ODS and Excel XML exports (-autoFilter). An option -fixedHeader to freeze header row which is available for all three formats. Both options are turned on by default.
• A new option has been added to highlight the result tab when the number of rows defined in the "Max. Rows" setting has been reached. (Tools -> Options -> Data display -> Show Max Rows. warning)
• A new commandline option for specifying the connection in batch mode has been added. Using -connectionProperties extended properties for the JDBC driver can be passed on the commandline. As the properties need to be specified as key value pairs the value has to be quoted, e.g. -connectionProperties='myprop=somevalue'
• A new entry to control the usage of the table's schema in an SQL export (WbExport -type=sqlinsert) has been added. This overwrites the default setting from the options dialog (Tools -> Options -> SQL Generation)
• For results the row numbers can now also be displayed (similar to the line numbers in the editor)
• Oracle object type columns are now displayed correctly. As this is a generic solution to display JDBC "Struct" values, it should work for any driver that returns the correct type.
• Integrated the JLine library to allow command line editing for console mode on Linux (and other Unix like systems).
• A new command WbListSchemas is available.
• A new option (-infoSheet=true) is available for spreadsheets exports (ods, xlsx, xls) to append an additional worksheet that contains the SQL that generated the export.
• A new option (-tableWhere="....") is available for WbExport to append a WHERE clause to all tables that are exported (e.g. WHERE modified_date > DATE '2010-01-01')
• The behaviour of the quick search for the auto-completion can now be configured. A new option "Partial match" will allow search anywhere in the listed objects (not just at the start). Another option allows to filter the displayed items according to the quick search value (instead of simply jumping to the first matching item). Alphabetic sorting of table columns can now be disabled (in that case, the columns are listed in the order as returned by the database). The new options have been moved to a separate page in the options dialog
• When toggling the option "Allow table altering" for the DbExplorer, this is now immediately reflected in any open DbExplorer (previously after changing the option the DbExplorer had to be closed and re-opened)
• For query results, the column comments can now also be retrieved. The column comments (if available) are then displayed in the tooltip of the result's column header. The retrieval can be enabled in Tools -> Options -> Data display -> Retrieve column remarks for queries
• WbExport can now also write a "control" file for DB2's IMPORT command (-formatFile=db2)
• A message box can now be displayed when all running scripts have been finished. If the application is minimized, displaying the message box will also restore the application's main window.

Bug fixes

• Setting the loglevel for the built-in logger was no longer working
• Displaying the definition for cross-schema synonyms was no longer working.
• WbSchemaDiff did not run in batch mode when procedures where included. Thanks to Denis for finding this.
• Activating the column filter in a table's column list in the DbExplorer did not work when hitting enter in the input field.
• When quoting column names for WbCopy's column mapping, the quoted columns where not detected properly (e.g. -columns='name/"Name", id/"Id"')
• The new "show max rows warning" option does not work for all Look & Feels. Some ignore the setting of a background color. If changing the background color is not supported the text of the result tab is now displayed in the chosen color.
• Fixed some more corner cases where the new row number display was not in sync with the result.
• The new row number display was not always in sync with the result table.
• Defined schema or catalog filters in the connection profile were not displayed correctly (even though they were stored correctly).
• Exporting only some of the columns of a result using "Save As" did not work.
• When using "Save Data As" to export a result set, the settings for an Excel export where not saved
• The current schema and database of the DbExplorer were not always saved correctly in the workspace.
• Stored procedures that used a REF CURSOR as an INOUT parameter could not be executed using WbCall
• If a table with the same name existed in two schemas, the DataPumper would show the coloumns for both tables, not just the selected one.
• The option to display row numbers for results was not saved from within the options dialog
• WbSchemaDiff reported the compared sequences as procedure-info in the diff summary
• The dialog to choose the update table for a multi-join SELECT result can now be resized
• When moving a macro from one group to another using drag and drop (instead of Cut & Paste) the change was not applied.
• When copying the data of a result set into the clipboard, the column headers were not copied when the keyboard shortcut was used.
• When moving a DbExplorer away from the end, the tabs were not restored correctly when loading the workspace later.
• Some properties for SQL generation were not migrated correctly from previous versions
• Setting the editor color for datatypes changed the color for the cursor (and vice versa)
• When changing inet, macaddr or cidr columns in the result set, wrong statements were generated for PostgreSQL

Build 107 (2009-12-16)

Enhancements

• SQL Workbench/J now requires Java 6.
• Changing column definitions or renaming tables directly in the DbExplorer can be now disabled in the Options dialog.
• The connection profile has a new option to filter schema and catalog names from the dropdown in the DbExplorer.
• A new option to keep the highlight when using "Highlight current statement" has been added (Tools -> Options -> Editor)
• A new option to set the default value for the Max. Rows field when opening new tabs is available (Tools -> Options -> Data Display)
• UTF and ISO encodings can now be entered (e.g. for WbExport or WbImport) without dashes: UTF8, UTF16, iso88591. They will be converted internally to the correct names.
• Log4J logging can also be turned on by supplying a configuration file as a parameter for workbench.log.log4j so that log4j.xml does not need to be in the directory where sqlworkbench.jar is located.
• Peter Franken contributed a Log4J integration for SQL Workbench/J. In order to use Log4j, the library log4j.jar (without a version number) must be present in the directory where sqlworkbench.jar is located. The log4j.xml must also be placed into that directory. To turn on log4j logging, the property workbench.log.log4j must be set to true (either in workbench.settings or as a system property) If log4j is used, none of the logging properties from workbench.settings will be applied. Log4j must be completely configured through log4j.xml.
• Blobs can now be exported and imported as "text values" by encoding the binary values (hex or unicode).
• sqlwbconsole.exe can now also be used to run SQL Workbench in batch mode (e.g. sqlwbconsole.exe -script=do_something.sql)
• A new menu item "File -> Close Window" is available to close the current window.
• For JDBC 4 drivers that support the SQLXML type, XML columns are now displayed directly (without the need to use casting or similar methods). Currently it seems that only Postgres and DB2 have implemented this properly in their driver.
• A new option to control the behaviour when closing a tab has been added. If "Activate the last used tab" is enabled, closing a tab will no longer select the "next" tab, but the previously used one. The new option is enabled by default.
• When opening a file from the the main menu (File -> Open), the file can now be opened in a new editor tab.
• Columns can now be added from within the DbExplorer's table definition panel
• The generated source for inherited tables in Postgres now shows the parent table
• WbSchemaDiff and WbReport now include triggers.
• WbDataDiff can now output the result as XML files.
• The WbXslt command can now handle stylesheets that include other stylesheets.
• In the macro editor auto completion is now enabled (if the main window is connected)
• workbench.settings will now only retain those properties that differ from the built-in defaults. This makes rolling out changes to the defaults easier. Any property that has been customized will remain in workbench.settings (but will not benefit from bugfixes made to the default properties)
• Result tabs, can now be re-orderd using drag and drop.
• The column definition of tables in the DbExplorer can now be edited and the approriate ALTER statement can be generated for the changes. Primary keys can be dropped and created from within the column definition.
• Tables (and other objects if the database supports this) can now be renamed from within the table list of the DbExplorer. The comment for a table can also be changed. To apply the changes a new menu option in the context menu is available to generate and run the necessary ALTER statements.
• The editor and resultset tabs can now have their own close button. (Tools -> Options -> General)
• For SQL Server 2005 and above, synonyms are now retrieved in the DbExplorer.

Bug fixes

• The trigger list panel (where all triggers where shown) was not working any longer.
• When copying a column name from the header's popup, the wrong name was copied when the columns where re-arranged using drag&drop.
• Fixed wrong formatting of multiple common table expressions (WITH .. AS) and multiple tuples for a VALUES expression.
• The (search) history dropdowns were filled in the wrong order (the oldest entry was the first entry)
• Using WbCall with a fully qualified procedure that returned a REF CURSOR did not work.
• The navigation for referencing/referenced rows was no longer available in the DbExplorer's data tab.
• Domain and Enum information was not displayed in the DbExplorer for Postgres versions before 8.4
• When using WbDataDiff with tables where the column names differed in their case "FirstName" vs. "firstname" the generated UPDATE or INSERT statements were wrong. WbDataDiff now considers column names that only differ in their case as identical.
• The new "Add column" feature was only configured for PostgreSQL
• Retrieving columns with type "timestamp" did not work for SQL Server.
• When adding a new column in the DbExplorer, column comments were not included.
• When reformatting statements, workbench variables that contained an underscore (e.g. $[my_id]) where not detected correctly (and thus the statement was not formatted correctly)
• The (table independent) trigger list panel in the DbExplorer did not show the trigger source correctly if multiple triggers had the same name.
• Execute current was not working for MySQL connections.
• If tables were created using double quotes (e.g. CREATE TABLE "MyTable"), the table details were no longer displayed in the DbExplorer
• If a connection script was defined in the connection profile, an error was displayed during connect (even though the connection script was executed correctly)
• The settings of the DbExplorer where not saved when the DbExplorer was opened as a separate window.
• When using "Highlight Current statement" and executing the statement at the cursor (Execute Current), the statement was not highlighted when an error occurred.
• "Execute current" was not working any longer.
• The editor color for datatypes selected in the options dialog was not used.
• The "Show Single Record Dialog" menu item in the table's popup menu was not always enabled.
• When copying a macro, the keyboard shortcut was copied as well.
• When cancelling the prompt to define an update table for a multi-table SELECT statement, an error was displayed.
• WbGrepData did not work if tables were listed explicitely using the -tables parameter.
• Auto completion was not working properly with Postgres and tables that were stored in the public schema.
• "WbMode confirm" was not working if the profile was set to read only.
• The BLOB dialog could not be opened from within a result set if the connection profile was set to read only.
• Formatting UPDATEs with Sub-Select was not working properly
• WbCopy now removes any trailing semicolon from the SQL query when using query based copying.

Build 106 (2009-08-31)

Bug fixes

• Connections to DB2 were no longer working

Build 105 (2009-08-31)

Enhancements

• Added support for H2 domains and constants
• For Postgres, if a SEQUENCE is tied to a column, this is now shown in the sequence's source and a comment is added for non serial columns in the table's source.
• Postgres RULEs are now displayed in the DbExplorer
• A new command WbMode is available which can change the "read only" and "confirm updates" setting for the current connection without modifying the underlying connection profile.
• Values for non-Standard datatypes can now be edited in the result set provided the DBMS supports some kind of function of cast to convert a string literal to that datatype. Default casts for the following PostgreSQL datatypes have been added: inet, cidr, macaddr
• A new help menu is available to display the online manual for the current DBMS. Default configurations (URLs) for PostgreSQL, Oracle, H2, HSQLDB, MySQL and Microsoft SQL Server have been added.
• A new command WbGrepSource is available to search the source code of all database objects for specific values (patterns). A GUI for this is also available at "Tools -> Search in object source".
• The table search panel can now search with more sophisticated conditions. This is done by searching in the application rather than using a LIKE condition in a SELECT query. Both search types are available in the "Search Table Data" tab of the DbExplorer. The functionality of the client side search is now also available through the new Workbench command WbGrepData
• Added support for SQL Server TYPEs in DbExplorer
• The default label used for new tabs can now be configured using the property workbench.gui.tabs.defaultlabel in workbench.settings.
• Added support for Postgres DOMAINs and ENUMs in DbExplorer
• The text and background color for the editor, the message area and the data tables can now be configured
• A new menu item to close all result tabs at once is available.
• In the table definition display (columns) in the DbExplorer, a new popup menu item is available to create a default INSERT or SELECT statement for the selected columns.
• A new parameter for WbExport is available: -sourceTablePrefix that defines a common prefix for all tables defined through -sourceTable. The prefix will be appended to all table names without any changes.
• A new option to display information about database objects is available through "SQL -> Object Info". If text is selected in the editor, this action will try to find a DB object with the name that is indicated by the selected text. It will look for tables, views, synonyms, sequences, procedures/functions and triggers. If something is found the definition (e.g. the list of columns) is displayed as a result set in the current SQL tab (the result will be appended). For objects with only a SQL source (e.g. a procedure) the source will be written into the messages tab.
• When specifying date/time format string (e.g. when importing a file or in the options dialog), the input is now validated and an error message is shown.
• The SQL Macros can now be displayed in a floating window. Double clicking a macro will run the macro in the currently selected SQL tab.
• The generation of the source SQL for a table can now be configured in order to use the functions the DBMS supports (e.g. SHOW CREATE TABLE for MySQL), so that incompatibilities of the DBMS with the ANSI SQL standard can be worked around. A detailed description is in the manual in the section "Customize table source retrieval" of the chapter "Properties in the .settings file"
• When using WbExport to generate HTML two new parameters can be used to specify HTML code that is added before and after the actual export data (-preDataHtml, -postDataHtml)

Bug fixes

• Exporting a table's data from within the table list in the DbExplorer was no longer working.
• The default fetch size of a connection profile could not be reset (empty).
• Fixed the autocompletion if a table was specified using schema.something.
• Shortcut keys which involved the Enter could not be defined.
• The Save As dialog to save result data now only checks for the update table and primary keys if needed.
• Using PostgreSQL's DELETE ... RETURNING did not work.
• Formatting a statment that used "AS ofx" for a column alias, would treat AS OF as a keyword and the formatted created a wrong syntax (AS OF x)
• Dropping a function from within the DbExplorer generated the wrong SQL for Postgres
• DESCRIBE is no longer handled by SQL Workbench/J when connected to a MySQL database.
• When using WbImport with -header=false but no column definitions, the import would fail if the table had more columns than the import file. The additional columns of the table are now ignored as in previous versions.
• "Create index" from within the table definition display in the DbExplorer was no longer working.
• The "Object Info" feature did not work on Postgres if the selected object was a view.
• In Oracle running a SELECT using a table name that was also used as a global symbol, the generated statements for changes in the result set referenced the schema PUBLIC instead of the current schema.
• When re-ordering the columns using drag-and-drop and then displaying the single-record dialog, the content of the columns was mixed up.
• When re-ordering the columns using drag-and-drop, the order was reset when changing data in the result.
• The alternate delimiter was not always processed correctly.
• When using the DataPumper to import text files and an invalid date format was specified, no table columns could be selected.
• The -schemas parameter for WbReport was ignored.
• When loading a new file into the editor while an error selection was present, the selection was still shown after the new file was loaded.
• When prompting vor variables, entering an empty value would remove the variable from the internal variables pool. It is now stored with an empty string as its value.
• (Un)Comment selection did not work if the cursor was in the very first column and no lines where selected.
• For WbCopy -createTarget was not working if the source was a query.

Build 104 (2009-05-06)

Enhancements

• All fonts can now be reset to their defaults in the options dialog.
• A result tab can now be reloaded (by re-running the original SQL) through the context menu of the result tab.
• It is now possible to cycle through the tabs using Ctrl-Tab and Ctrl-Shift-Tab
• The keyboard shortcuts for editor movements can now be configured. The defaults have been adjusted to comply with the Apple guidelines on Mac OS
• The generating SQL query of a result tab can now be displayed by double-clicking on the tab or through the context menu of the result tab.
• WbCopy (and the DataPumper) now optionally ignores any error that occurs when dropping the target table. For that, a new parameter is available -ignoreDropError which defaults to false
• When using XSLT to transform output of e.g. WbReport or WbSchemaDiff, the name of the stylesheet can now be specified without a pathname if located in the xslt subdirectory or the config directory.
• When assigning a keyboard shortcut to a macro, the shortcut's character would be inserted into the editor when the macro was executed.
• CHECK constraints are now reported individually in the output of WbReport and WbSchemaDiff. WbSchemaDiff has a new parameter to match check constraints by name or by expression only.
• A result name (defined using @wbresult) is now used as the header when printing the result.
• The editor can now be configured to either uses spaces or real tab characters (as before)
• The editor can now be scrolled without moving the caret by using Ctrl-Down and Ctrl-Up
• Autocompletion is now supported for the SQL statement EXEC and will show a list of stored procedures. WbCall and CALL are also recognized.
• When showing the sequence definition for an Oracle sequence the column LAST_NUMBER is now also displayed in the DbExplorer
• When defining a new filter for a result set, the currently selected column is now pre-selected in the dropdown if no filter is defined.
• When using WbCopy's -createTarget=true, data type mappings can now be specified in workbench.settings that enhance or overwrite the data type mapping returned by the driver. Details can be found in the manual.
• Manually changed column order in the table data of the DbExplorer can now be saved. Either manually through the popup menu of the table header, or automatically through an option for the DbExplorer.
• When defining the jar library for a Look & Feel, the application now scans the libraries for the approriate classes
• Removed the limitations that DbExplorer panels must be the last tabs and cannot be the only tab.
• A new option is available to customize how external files that are loaded in an editor tab are remembered in the workspace.
• A single record dialog is now available to edit data in a result set (Data -> Single record dialog)
• A new option to control the use of uppercase keywords for the SQL formatter is available (Tools -> Options -> SQL Formatter)

Bug fixes

• Versioned backup of a profile's workspace did not work, if the workspace was not specified with a full name in the connection profile.
• Fixed a repainting issue on MacOS in the toolbar when switching between DbExplorer tab and editor tabs
• When displaying Oracle Packages the selected procedure/function was not highlighted in the source view of the package.
• Ctrl-C was no longer working in the source display of the DbExplorer if it was opened as a separate window
• Double clicking in the status bar would open a new SQL tab
• Tabs could not be renamed if more than one window was open.
• The list of SELECT columns in the autcompletion popup was not displayed correctly (e.g. for GROUP BY) when the DISTINCT keyword was used.
• The source of the index definition was not displayed in Postgres, if a table had a primary key and one additional index.
• If a profile did not have a name, SQL Workbench failed to display the connection dialog.
• The current database was not selected in the DbExplorer for DBMS using Catalogs instead of Schemas (e.g. MySQL)
• Reformatting WbVarDef would incorrectly replace it with WbVarDefine
• Workspace -> Assign Workspace was no longer working
• When "Automatically optimize row height" was enabled, sorting a result set would not redraw the table correctly.
• Sequences were no longer displayed for DB2 on Windows/Linux
• User defined PK mappings were not remembered
• When running WbImport, errors where not shown any more.
• Fixed a problem when formatting inline views that contained unions and redundant brackets
• The driver dropdown in the connection dialog was not updated when a new driver was added while the connection dialog was open.
• The About Dialog was not displayed on MacOS when more than one application window was open.
• The quick filter in the Trigger panel was no longer working
• Copy & Paste shortcuts were not working on MacOS
• "Save Data As" was not working if it has never been called before
• Fixed displaying the PDF manual on MacOS (Thanks Markus!)
• Some workspaces were not loaded properly and editor tabs would be removed upon loading.
• When refreshing the source for a table or a view, the column definition was not reloaded from the database.
• When selecting a different view in the DbExplorer while the view source was displayed, the wrong source code was displayed for the newly selected view.
• When MySQL was not set to ANSI mode, primary key columns that needed quoting were not detected properly due to MySQL's non-standard quoting character (in non-ANSI mode)

Build 103 (2009-01-31)

Enhancements

• Removed the need to specify the columns of the source query for WbCopy. If -columns is not specified when using -sourceQuery it is assumed that the names of the query columns match the names of columns in the target table.
• Closing of editor tabs can now be confirmed (General Options)
• The display strategy for the tabs in the main window can now be changed between scrolling and stacked ("Scroll tabs" in the general options)
• Individual SQL panels can now be locked to prevent accidental closing of the panel.
• A new option to close all other tabs has been added to the popup menu of the tabs.
• Comment lines in workbench.settings where the very first character is a # are now preserved if immediately followed by a property line. A comment line that is followed by an empty line will still be removed.
• Display SQL source for comments for additional object types such as views, sequences, procedures where possible.
• The "Manage Drivers" dialog now searches the selected jar file for a JDBC driver if a new library is selected.
• The placement of the details tabs in the DbExplorer's table list can now be configured through the options dialog, not only in the settings file.
• The syntax highlight colors can now be configured through the options dialog
• The "select expression" replacement is now also used inside the "Search table data" tab.
• For specific datatypes, data retrieval in the DbExplorer can now be done by applying expressions to the column when building the SQL to select the data. The replacement is defined per database and datatype in workbench.settings. For details please refer to the manual ("Customize Data Retrieval" in the chapter about the DbExplorer)
• A new option to make versioned backups of the workspace is now available (Tools -> Options -> General -> Create Workspace Backup)
• The removal of comments when the "remove comments" option is active has been moved to a later stage in the statement processing. This way the new feature to name result sets can be used with DBMS that do not support embedded comments in SQL statements.
• The dropdowns for schema/database can now be reloaded in the DbExplorer
• The result set tabs can now be closed or renamed through their context menu.
• Completely reworked the macro handling. Macros can now be grouped, manually sorted, hidden from the menu and can be assigned a shortcut. Once the old WbMacros.xml has been opened and saved with the new version, older versions of SQL Workbench cannot read that file any longer!
• Result sets can now be named by specifying a keyword in the comment prior to the statement to distinguish different result tabs. Please refer to the manual for details ("Displaying Results" in the chapter "Using SQL Workbench/J")
• Added 'WbListTriggers' commands to list all triggers in the database (showing the information from the "Triggers" panel in DbExplorer) and WbTriggerSource to display the source of a trigger. The DESCRIBE command now also returns the list of triggers for a table.
• When importing a text file, WbImport does no longer tries to guess different timestamp or date formats if the default format leads to an error. Instead an error is reported immediately.
• A new commandline argument -interactive is available when running in batch mode. This enables parameter prompting and execution confirmation if necessary.
• WbInclude can now be called with just a filename. If no parameter switch is present, it is assumed that the rest of the commandline is the filename. In that mode, no further parameters can be specified (WbInclude will use defaults then)
• The HTML manual is now also distributed as a single HTML page The display of the single page from within the application can be enabled by setting the property workbench.help.singlepage=true in workbench.settings
• A new workbench command to show the source of a stored procedure is available (WbProcSource)
• WbList has been extended so that the object names and/or types can be specified.
• WbCopy now also supports -truncateTable (not only -deleteTarget)
• When using a line filter for a text import the matching is less strict now. The pattern does not need to match exactly the line but must occur in the line (technically it was changed from matches() to find()) to make filtering complete lines easier.
• SQL Workbench/J can now be run interactively in console mode To start the SQL Workbench/J console, use the supplied scripts sqlwb.cmd or sqlwb.sh
• The status bar will now display the number of selected rows If numberic values from a single column are selected, the sum of the values will be displayed. This can be turned off in the Options dialog ("Data Display" section)
• The messages in the message tab can now be deleted manually (Edit -> Clear messages)
• A new option for WbExport is available (-writeEmptyResults) to surpress the creation of the outputfile if the result set is empty. The default is -writeEmptyResults=true
• The values for search & replace in the editor are now saved and available as a dropdown in the dialogs
• The logfile can now be displayed directly from within the application using Help -> View logfile
• The location of the settings file and the log file are now displayed in the Options dialog
• The collation to be used when sorting a result set can now be selected in the options panel ("Data Display" page)

Bug fixes

• The placement of the NULL and DEFAULT keywords were not correct in the generated table source in the DbExplorer
• When displaying the source for views or tables in the DbExplorer grants that were made to the current user were not displaye (thanks to Marcus for pointing that out)
• When the tabs in the mainwindow where displayed on two or more lines, the context menu to rename a tab was no longer displayed.
• Fixed several issues with retrieving object sources for DB2 on z/os (thanks to Frank!)
• When selecting data from another user's schema, and updating the result set, the generated SQL to update the table did not contain the schema.
• The -sourceDir parameter for WbImport was not working with relative directories if WbImport was called from within a script using WbInclude
• The "Tab" key was no longer working in the editor
• "SQL -> Export Query result" was not working
• The shortcuts for Copy, Cut & Paste can now be defined through the shortcut definition dialog.
• WbCopy (and DataPumper) did not work with tables that had non-standard column names that needed quoted (either because the names consited of mixed-case or they contained special characters that required quoting.
• Changing the background of the connection information in the toolbar only worked with the Nimbus look and feel.
• When a macro was invoked using a shortcut with "Shift" the current text in the editor was replaced.
• The replacement of macro parameters (e.g ${current_statement}$) was broken after the macro rework
• The multi-page HTML manual was no longer displayed
• "Remove comments" was not working properly if the comments contained quote characters
• When copying a connection profile, the property "Remove comments" was not copied.
• Removed the brackets from the application name that is set in the connection properties to work around the strange limitation in the current Oracle drivers (11.1.0.7.0)
• Drop Trigger from within the DB Explorer was no longer working
• WbExport with -outputDir did not work any longer if only a single table was specified.
• Using WbExport with -writeEmptyResults=false together with -append=true did not produce the expected result.
• Fixed some errors in the german localisation
• When using multiple windows together with "Separate Connection Per Tab" the application could lock up.
• When changing database or schema in the DbExplorer the table information was not cleared properly
• A hack has been implemented to display SQL Server's timestamp columns (which are returned as a byte array) as a hex string (the same way the Query Analyzer displays the timestamp column)
• The list of stored procedures was not displayed
• When reformatting SQL Statements, Workbench variables where not treated correctly
• WbCopy did not work when specifying multiple source tables with -deleteTarget and -checkDependencies
• Column names with Chinese characters were not displayed correctly
• WbCopy incorrectly assumed that the JDBC driver does not support batched updated and disabled JDBC batching
• -excludeFiles for WbImport did not work if the filename contained a dot (e.g. dbo.table.txt)
• Editing result sets that were retrieved from more than one table was no longer working.
• Tried to make the application more robust against out of memory errors.
• The parameter -delimiter for WbInclude now uses a colon as the delimiter to specify a single line delimiter, e.g. -delimiter=GO:nl in order make quoting of the parameter not necessary and avoid confusion with an actual semicolon in the definition. The old style is still supported but will be removed in the future.
• When a profile is set to "Read Only", in place editing of results is now disabled.
• When using a WbExport together with a SELECT statement, the "Max. Rows" option (lower right corner of the MainWindow) is not longer used for the SELECT.
• The status column was not always displayed if something was changed in the result set
• The setting to sort with a language specific collation was not working any longer.
• -excludeTables did not work properly in all cases for WbSchemaDiff
• If the definition for a Look & Feel was not complete (e.g. a missing classname) the "Look & Feel" panel in the Options window could no longer be displayed.

Build 102 (2008-09-15)

Bug fixes

• The connection dialog showed a wrong label for the "Remove comments" property