Here are some of the highlights of the fix pack.
Speedy pureQuery application iterative testing - As part of pureQuery development, you are always changing your SQL in the annotated style interfaces. You now have the ability to generate JUnits for those interfaces and speed up testing. Simply right click on the annotated interface from the package explorer and select Generate JUnit from the menu.
Improved SQL support in Java database applications
- Bridging the gap between Java and SQL has been one of the key benefits of pureQuery since the first release. This feature has been improved to allow live validation of SQL against the database, if you have a live connection available. This is a sure shot way to ensure SQL is accurately validated, and you may want to always set this flag if you have a live database connection.
You can set this flag (called “Validate SQL problems against live database”) from Window->Preferences->pureQuery, or from the project properties.
- SQL merge statements can now be auto-generated when pureQuery code is generated from one or more tables and at least one primary key exists on the table(s). Simply check the boxes for SQL merge statements in the pureQuery code generation wizard (by default, they are checked).
Improved developer and DBA handshake
We are providing yet another step towards seamless integration between the developer and DBA roles. When using Optim Development Studio to bind SQL into static SQL packages, you can now generate .bat or .sh files which can be shared with the DBA. The DBA can use that as a starting point to customize the bind calls, or use them as is.
Improved usability for tuning queries in ODS using Optim Query Tuner
You can generate reports that suggest how to tune SQL statements for better performance, when Optim Query Tuner is installed in a shell shared environment with Optim Development Studio. Simply right click on an SQL statement from your pureQuery application or from the SQL Outline, and select Generate Query Tuner report from the pureQuery menu.
Improved support for application development when using the pureQuery API
Applications often need to access SQL from multiple schemas within the same project. This is now possible when building pureQuery annotated style applications. You can specify different schemas (to quality unqualified tables/ views) or paths (to qualify unqualified procedures/ functions) for each annotated interface in a pureQuery application, and these values will be used for SQL development/editing within your interfaces. To enable this, right click on the annotated style interface and provide values using the Connection Settings.
Improved support to use existing beans when using pureQuery API
If you use customized row handlers in your pureQuery applications, you can now get a head start in building these by customizing the ones generated by pureQuery. Using this new feature, you can externalize row handlers from an interface into separate files, and enable re-use. To see this feature in action, right click on the annotated style interface from the Package Explorer and select Create Handler Classes from the pureQuery menu.
In addition to the above Optim Development Studio features, there are numerous enhancements in the Optim pureQuery Runtime Fix Pack, including:
- Usability improvements in the static binder that allow you to specify package level bind options and allows more control over packages to bind from various artifacts
- Improved exception handling to get access to underlying sqlstate and sqlcode easily
- There are also improvements in serviceability and literal substitution features
As always, let us know what features you would like to see and please keep the feedback coming! Feel free to submit questions using the Optim Development Studio and pureQuery Runtime forum on developerWorks.