Aginity Workbench for Redshift provides new functionality and improvements in stability and quality of the software over previous versions. These release notes summarize the new features and changes that apply to version 4.4.
- A built-in Workbench SQL Formatter is available in Workbench. In addition to using the built-in Workbench SQL Formatter, users can provide an alternative Windows Executable or .NET Assembly formatter. They can do so in Application Options > SQL Formatters.
This section contains details of specific functions and changes that are included in Aginity Workbench 4.4.
Upgrading from Prior Versions
Workbench automatically checks for new updates and displays a dialog box if an update is available. In the dialog box, select Install this update now to download and install the update.
You can also choose to postpone installation of the update until the next time you run Workbench or suppress the update alert.
You can also check for updates manually by clicking Check for Updates on the Help menu and then install an available update by following the instructions in a wizard.
- Windows XP or later
- Windows Installer 3.1
- .NET Framework 3.5 SP1
- Memory: 256 MB RAM
- Disk space: 100 MB, plus any necessary space for .NET Framework and Windows Installer
|APD-6844||An option for ignoring SQL errors. Select Continue on error in the Query Options dialog box.|
|WPD-1||A simple SQL format tool is available.|
|APD-6910||Support for DISTSTYLE (ALL) was added to Workbench.|
Bug Fixes in Build 4.4.2183
|Severity||Reference||Description||Existed Since Version||Resolution|
|Major||APD-8795||After import from a JSON file that contains a dataset, only one record is added for the entire dataset.||4.3||Fixed. Data imported from a JSON file is now parsed into the correct number of records.|
|Major||APD-8086||A flat data structure is incorrectly parsed after import from a JSON file.||4.3||Fixed. A flat structure is parsed into the correct number of records after import.|
|Major||WPD-170||An error appears when a user attempts to turn off "Group by Schema."||4.3||Fixed.|
|Major||WPD-68||In some cases when a user attempts to browse columns in a table, an error occurs indicating that an object reference is not set to an instance of an object.||4.3||Fixed.|
|Moderate||WPD-48, WPD-142||Querying large data sets on a Redshift server in SSL "Require" mode causes a "Connection is broken" error.||4.3||Fixed.|
|Minor||WPD-88||Typo in the Restore Connections dialog box.||4.0||Fixed.|
|Minor||APD-7285||During a SELECT statement, dates in the format “01-01-01” cause the error “One of the identified items was in an invalid format.”||4.3||Fixed.|
|Moderate||APD-4093||Import of a file from the S3 file explorer fails because invalid data types are set for the columns in the file.||Set all column data types as VARCHAR and re-import the file.|
|Moderate||APD-3788||The Abort feature in Redshift Workbench does not terminate a query that is currently running.||Use the SQL at http://docs.aws.amazon.com/redshift/latest/dg/r_CANCEL.html to find the process ID of the running query and cancel it.|
|Minor||APD-4090||If you begin a download using a file system explorer (such as Amazon S3) and abort the download, a small portion of the file remains on your target system.||Manually delete the file on your target system.|
|Trivial||APD-3711||When the field type is Date, the year 0 (for example, 0000-01-01) causes an error “Year, Month, and Day parameters describe an un-representable DateTime.”||Either cast the date as a VARCHAR or do not use the year 0.|