We are re-writing the DDL parsing logic for FireStorm 2.0 and are looking for sample SQL/DDL files. Have you had problems importing SQL scripts using FireStorm 1.1? If so, we'd love to have sample SQL scripts from you so we can make sure that FireStorm 2.0 handles them correctly.
Please send any samples to support@codefutures.com - we will keep them confidential.
FireStorm has been reviewed by the folks over at Jars.com and has scored 955 points out of a possible 1000, resulting in a "Jars Top 5%" rating.
FireStorm/DAO 2.0 is rapidly becoming a stable platform and we are looking for beta users to provide feedback on all the great new features. In return we are offering attractive discounts for qualifying beta customers who provide meaningful feedback.
If you are interested in road-testing FireStorm/DAO 2.0 send an introductory email to beta@codefutures.com
FireStorm 2.0 provides an option that allows you to choose whether you want to map numeric columns to primitives or objects. For example, if you have a SQL INTEGER colum you can choose to map this to an int or an Integer type in Java.
FireStorm 2.0 is progressing well in the labs and now supports DAO code generation from custom SQL statements. This means that you can use ANY possible SQL statement that your database supports and no longer be limited to one-to-one mappings between Tables and Java objects.
For example you can now generate DAO code for statements like:
SELECT D.PRODUCT_CODE, COUNT(*)
FROM DOWNLOAD D, CUSTOMER C
WHERE D.EMAIL = C.EMAIL
AND C.REGION = :region
GROUP BY D.PRODUCT_CODE
The FireStorm roadmap is available at:
We have just posted FireStorm 1.1.4 to the web site. This version contains the following enhancements:
FireStorm 1.1.3 is now available to download from:
http://www.codefutures.com/products/firestorm/download/
This release includes a code generation bug fix for J2EE as well as improved support for nullable columns.
FireStorm 1.1.3 now generates extra methods on DTO (Data Transfer Objects) so that primitives can be tested for null values.
FireStorm 1.1.3 now generates extra methods on DTO (Data Transfer Objects) so that primitives can be tested for null values.
For example, if your database contains a column called "quantity" that allows nulls, you will now get these methods on the DTO:
void setAmount(int amount);
int getAmount();
boolean isAmountNull();
void setAmountNull(boolean isNull);
A new FAQ entry has been posted which explains how you can call multiple DAOs as part of a single transaction in both J2SE and J2EE DAO tiers.
Welcome to the Code Futures corporate Weblog. This weblog will be used to announce product launches, availability of bug fixes, special offers, and so on.