Release Notes: This release provides working DB/2 LUW 10.1 support. It is working well except for an exception on one test. Basic support for Oracle, SQL Server, and Sybase ASE will be provided in the future. Stored procedures were tuned.
Release Notes: Beta 18 adds tested support for Oracle 11gR2 with the same capabilities which have already been released for PostgreSQL 9.1, MySQL 5.5, and DB/2 LUW 10.1. It also resurrects the CFBam 2.0 model, though there are problems with the XML parser for that model which cannot be resolved without significant work.
Release Notes: This release incorporates enhanced and upgraded support for PostgreSQL 9.1 and MySQL 5.5, providing more robust security restrictions and enforcement than Beta 16 did. It also includes support for DB/2 LUW 10.1, though there are runtime exceptions occurring in two test cases consistently which cannot be replicated under Eclipse, so consider this a qualified beta for DB/2.
Release Notes: This release has completely regression tested MySQL 5.5 support as verified under Ubuntu 13.04 with OpenJDK 7 and stock 64-bit MySQL 5.5 out of the Ubuntu can. This code is actually slightly more advanced than the PostgreSQL code, in that it implements read security checks for all of the stored read procedures.
Release Notes: This release refreshes the MySQL 5.5 support to the point release supported by Ubuntu 13.04. It should be backwards compatible with the 12.04 LTS release as well, but this has not been tested. The MySQL data definitions are complete, with support for the audit columns on tables and the history tables as well. The installation of CFDbTest 2.0 for MySQL 5.5 on Ubuntu 13.04 installs with zero errors, though the history and audit information is not maintained by the stored procedures yet. Apologies for the formerly broken MySQL 5.5 implementation.
Release Notes: The PostgreSQL feature set is now complete. The data manipulation methods for PostgreSQL and its corresponding stored procedures now restrict data access based on the ClusterId and TenantId specified and stored in the Authorization object, unless a session is logged in as "system". There will be bugfixes for PostgreSQL in the future if needed, but no further new development features are planned nor expected for that set of DbIOs. Future releases will flesh out the feature sets of the other databases to match that of PostgreSQL instead.