DTP 1.5 Release
News and Noteworthy
Added API for supporting off-line connection mode at the framework level.
Added migration hooks into profile loading code (including import).
Expanded integration of connection profile repository support (still experimental).
Connection Profile Selection Components
Many extenders of DTP need to select connection profiles, potentially based on filter conditions. DTP now has a set of components to make connection profile selection easier to integrate with such tools. See Bugzilla 170130 for details.
Open Data Access (ODA)
Integrate connection profile framework with ODA runtime
By maintaining a dynamic reference to a connection profile in the ODA runtime framework, an ODA consumer application can automatically pick up any changes made to the profile's connection properties.
ODA Web Services Data Source provider
The new ODA provider allows a client to specify a WSDL URL or file location. In addition, a custom Java connection class can be specified to allow refined control of how the SOAP request is made. Once the data source is set up, a client can build a web services data set responsible for sending the SOAP request and parsing the SOAP response.
ODA API Enhancements
Adds support of "boolean" data type in result set columns and parameters
Provides explicit setting of a null value to an input parameter
Exposes the Name of a Parameter in its Runtime Meta Data
See ODA API Change Specification for details.
Relational Database Support
Added support for the following object types to the generic DDL generator:
User defined functions
User defined types
Sybase SQL Anywhere v9 and v10 Enablement Support
DTP 1.5 contains the first drop of Enablement support for the Sybase SQL Anywhere database, versions 9 and 10. Following the intention of the Enablement project in DTP, these components deliver support for this database directly from DTP, and provide a sophisticated example of how DTP can be extended for relational databases.
Note the additional folders under the database node. The Sybase SQL Anywhere Enablement components demonstrate specialized catalog loading of such database objects.
SQL Development Tools
Table Creation Wizard
In DTP 1.5, NEC Soft (Japan) joined the DTP team and contributed a (relational) table creation wizard. This generates the DDL necessary to create a given database table, and supports Apache Derby data types and primary keys. The DDL generated can be executed directly in the DTP SQL editor to create the table and saved for later reference.
Easier Connection Selection in SQL Editor
The SQL editor has controls at the top of the edit area for selection the target connection profile:
SQL Scrapbook Editor is added for quick ad hoc SQL statement execution. The SQL Scrapbook can be invoked from the workbench toolbar (). It has the same functionality as the SQL (file) Editor (content assist, templates, etc.), and the ability to save the SQL contents to a file. User can execute the SQL against a chosen connection profile and see the results in the results view.
DTP provides a standalone SQL Editor. With the introduction of this multi-page editor aware/ready framework change, the DTP community developers/vendors will be able to utilize it to implement their multiform editors.
The following usability enhancements are added:
Supports double click to open routine editor;
Links routine editor with the Data Source Explorer. ( Link with editor)
Use a non-UI thread to run a procedural object in order not to block UI.
The SQL statement execution is carried out in a new Job now so that it will no longer block the UI any more.
A global preference is added for user to specify the default connection info.
Connection info composite is added on top of the SQL Scrapbook/File Editor for user to quickly switching connection info.
User can select a connection profile first before specifying the server type, which will be automatically detected by the software.
SQL Tools will no longer ping the server for version info, instead it will get version from driver template if it's not already cached in connection profile properties.
Connection in the launch configuration dialog is made only when the user attempts to run the procedural object.
Consumers will have a unified API (instead of various utility classes) to handle data types (both predefined and UDT) and the default implementation can be customized freely by extenders.
Prompt user to save procedural objects before launch;
Prompt user to switch perspective when a procedural object breakpoint is hit;
Correctly initialize the database debug perspective layout.
When deleting/renaming a connection profile error will occur.