Release Notes: The PostgreSQL 9.1 implementation has been updated to make use of stored procedures, prepared SQL statements, and every other performance-tuning trick known by the author. Subsequent betas will be released as additional databases are brought to the same level of integration as this release for PostgreSQL. MySQL 5.5 support is as complete as it will ever be, and basic DB/2 LUW 10.1 support is also provided.
Release Notes: A workaround for the DB/2 LUW Blob support issue has been implemented. DB/2 LUW now stores BLOBs as Base64-encoded CLOBs of the same maximum length as the Blobs in other databases. As a result, DB/2 LUW cannot store full-size Blobs. On the plus side, all database operations for DB/2 LUW are now expressed as server-side stored procedures, boosting performance.
Release Notes: There are three known bugs with the code produced by the release candidate. DB/2 LUW will periodically throw SQLCODE 204 exceptions. Sybase ASE will allow you to delete data when you don't have an entry in the security tables allowing you to do so. SQL Server will also allow you to delete data when you don't have permission to do so.
Release Notes: The MssCF support files have been moved from the $schemaname$ project to the $schemaname$msscf project. That way, the core library package $schemaname$ has no more than it absolutely must, and there is no dependency on MssCF implied for using the project code.
Release Notes: PostgreSQL JDBC now uses dynamic database schema naming. You can now dynamically set the database schema name with a PostgreSQL JDBC client, allowing you to run a custom client for a given schema model against an extended/superset database instance that references the schema model for your application. Because the target database is a superset, your client should only have to specify the target schema name in its configuration file, and the rest should just happen automatically.
Release Notes: You can now reference and import schemas to your model by using the new SchemaRef elements of a SchemaDef. Examples of how to use this new construct are present in all the models provided by the distribution packaging. You need to import CFIso and CFSecurity at a minimum. CFInternet is highly recommended, as well. Most applications that are modified to reference CFIso and CFSecurity should see substantial reduction in code size compared to copy-pasting the old complete CFSme model.