« June 2005 | Main | September 2005 »

July 26, 2005

Bug fix: Prefix Table With Schema Name

FireStorm/DAO 3.0 build 59 is now available for direct download from:

http://www.codefutures.com/products/firestorm/download/

This build fixes a number of bugs related to the code generation option "prefix table with schema name". This option was working correctly for J2SE code generation but not for J2EE code generation. Also there were inconsistencies in how this option was saved to the project file.

The first time that you generate code from your project using this new build, it is recommended that you double check the setting of this option to make sure it is set to the value you desire (on or off) and that you save your project file afterwards.

The name of the option in the "provider options" section of the project file has been standardised to "prefix-schema-name" whereas previously both "prefix-schema-name" and "use-schema-name" were in use.


July 15, 2005

FireStorm/DAO 3.0 Release Candidate 1

The development team is finally feature-complete and ready to launch Release 3.0.

The Release Candidate 1 is now available for download.

The new feature list is:

• Hibernate code generation

FireStorm/DAO produces Hibernate Java persistent classes and a Hibernate mapping file (*.hbm.xml) for each database table.

• REF CURSOR support for Oracle Stored Procedures

FireStorm/DAO reverse-engineers stored procedures for Oracle, SQL Server, and Sybase. Oracle support has been enhanced and FireStorm/DAO now reverse-engineers REF CURSOR parameter information, including REF CURSOR columns, when importing Oracle Stored Procedures.

• Using Dynamic SQL with Custom SQL DAOs

It is now possible to execute Custom Data Access Objects with dynamic SQL. Effectively this means that the same DTO and DAO mapping can now be used with multiple SQL statements. A typical use-case for using Dynamic SQL statements with a Custom DAO is where a multi-table SELECT is implemented as a Custom DAO but there is a need for multiple "finder" methods.

• setMaxRows Support

JDBC DAOs for Tables and Views now have a setMaxRows() method. This method should be called prior to calling any finder methods to limit the number of rows returned (the DAO finder implementations simply makes a call to JDBC setMaxRows method before executing their SQL query).

• Setting Default Values for DTO Fields

Users can set default values for DTO fields when defining Table and View DAOs through the FireStorm/DAO user interface. Typical uses of this feature would include allocating UUID values to primary key fields and defaulting date fields to today's date.

• User Interface and Usability Improvements

There are many usability improvements, for example, when re-installing or upgrading FireStorm/DAO, existing firestorm- conf.xml files are no longer overwritten.


Between RC1 and GA, we're going to test, test, document, and test. We've improved the user interface so much that we're going to have to re-shoot all the video demos as well.


July 07, 2005

FireStorm/DAO 3.0 EA build 48

An updated 3.0 RC1 is now available to download from:

http://www.codefutures.com/products/firestorm/download

Build 48 features significant improvements in Hibernate ORM support as well as further improvements to the Studio user interface (FireStorm/DAO now remembers the 10 most recent projects in the File menu and the JDBC Driver and JDBC Data Source configuration dialogs have been overhauled).

You can view the release notes here.

July 05, 2005

FireStorm/DAO 3.0 EA build 44

A new FireStorm/DAO build has been released. As always, the release notes are available here:

http://www.codefutures.com/products/firestorm/download/README.html