Release Notes - Tirasa/OpenJPA-Azure GitHub Wiki

Information about features, issues and limitations related to project releases.

0.4 (2012-12-21)

The 0.4 release introduces cache support, multithreaded connection and code optimization.

See the detailed list of issues included in this release.

Limitations of this release

  1. #36 Cannot handle the same table either in the root database and one or more federations.
  2. Cross database JOINs are not supported.
  3. #55 JPQL AVG not supported.
  4. #66 ID auto generation strategy 'AUTO' is supported only.

0.3 (2012-11-30)

The 0.3 release introduces wrapping by OpenJPA Slice, support for JPQL / SQL native JOINs (no cross database) and full transaction support.

Besides the known [basic example](Sample Web Application), Apache Syncope integration project has been improved as started in a separated project, aiming to make Apache Syncope able to get the most out of Windows Azure.

See the detailed list of issues included in this release.

Limitations of this release

  1. #36 Cannot handle the same table either in the root database and one or more federations.
  2. Cross database JOINs are not supported.
  3. OpenJPA QuerySQLCache, QueryCache, DataCache, QueryCompilationCache are not supported.
  4. #55 JPQL AVG not supported.
  5. #66 ID auto generation strategy 'AUTO' is supported only.

0.2 (2012-10-19)

This github project and Maven groupId and artifactId were renamed to be more adherent to Windows Azure's naming; these facts might result in some dangling links or not working build instructions: just update to latest available version and everything should be working. If you experience any problem, please let us know.

The 0.2 release introduces support for all JPQL 2.0 statements and initial support for transactions and native SQL statements.

Besides the known [basic example](Sample Web Application), a more complex integration was started in a separated project, aiming to make Apache Syncope able to get the most out of Windows Azure.

See the detailed list of issues included in this release.

Limitations of this release

  1. #36 Cannot handle the same table either in the root database and one or more federations.
  2. #42 JPQL Empty Collection comparison is not implemented because it would imply full JOIN support.
  3. #43 JPQL Collection membership is not implemented because it would imply full JOIN support.
  4. #55 JPQL AVG not implemented.
  5. #51 EntityManager.find() can be incoherent in case of replication.

0.1.1 (2012-09-24)

In addition to 0.1, some POM refactoring has taken place and now the only artifact available is a lightweight JAR library that can be embedded in other projects, like as the provided [sample web application](Sample Web Application).

0.1 (2012-09-21)

This is the first stable release after initial prototype, mostly featuring code reorganization and clean up.

See the detailed list of issues included in this release.

Limitations of this release

  1. Tables with foreign-key constraints cannot be federated
  2. Native queries on federated tables cannot be executed
  3. JOIN operations involving federated tables are not supported yet
  4. Criteria API are not supported on federations