...
JUnit results for OpenJPA supported databases being tested nightly by IBM using Java SE 6 (either IBM SDK or Sun JDK).
- All tests passed
- Number of failing tests
Database | JDBC Driver | I10 M3 (20090901I11 - 20091005) I11/M3 (20091005 | Beta (I14 - 20100125) | I12 Beta2 (2009110220100224) | I13 Beta3 (2009120720100323) |
---|---|---|---|---|---|
Derby 10.2.2.0 | Embedded | 2648 2711 | 2711 2904 |
|
|
Derby 10.5.3.0 | Embedded |
|
| 2788 3004 | 2816 3049 |
DB2 9.5.2 | JCC 3.50.152 | 40 2 | 1 | 3004 | 1 2 |
HSQLDB 1.8.0.10 | Embedded in-memory | 13 | 12 | 13 12 12 | 16 |
MySQL 5.0.67 | JDBC 5.1.6 92 | 1 1 |
|
| 2 |
MS SQL Server 2005 SP3 (9.00.4035) | sqljdbc4 2.0.1803.100 | 74 14 14 | 8 | 14 8 14 | 10 |
MS SQL Server 2008 SP2 (10.0.2531) | sqljdbc4 2.0.1803.100 | 75 14 14 | 5 | 14 5 14 | 8 |
Oracle 10g Express (10.2.0.1.0) | ojdbc14 10.2.0.1.0XE | 116 5 5 | 3 4 | 5 in locking | 4 1 + locking |
Manual Database Coverage
If you regularly test OpenJPA 2.0.x against another DB vendor or level not listed above and would like to share your results, then feel free to add them below. All we ask, is that you provide as much of the details requested below, so others can make their own decision on whether to use one of these combinations in their environment.
Database | JDBC Driver | Java | SVN Rev | Results | Submitter | Notes |
---|---|---|---|---|---|---|
Derby 10.3.3.0 (652961) | Embedded | Sun 1.6.0_15 | r817831 (20090922) | 2 | dwoods | |
Derby 10.4.2.0 (689064) | Embedded | Sun 1.6.0_15 | r817831 (20090922) | 2 | dwoods | |
Derby 10.5.3.0 (802917) | Embedded | Sun 1.6.0_15 | r813659 (20090910) | 1 | dwoods | |
MS SQL Server 2008 (10.00.1600) | jTDS 1.2.5 | Sun 1.5.0_11-b03 | r895453 (20100103) | 4 | mtylenda | did not run locking tests |
PostgreSQL 8.3.5 | 8.4 JDBC3 (build 701) | Sun 1.5.0_11-b03 | r885965 (20091201) | 31 | mtylenda | AccessToUnderlyingConnectionAllowed DBCP property set to true, 12 failures come from locking tests |
H2 1.1.118 | Embedded | Sun 1.5.0_11-b03 | r826468 r905001 (2009101820100131) | 56 48 | mtylenda | in-memory named database, 48 47 failures come from locking tests; with MVCC option turned on there are 23 failures from locking tests, OPENJPA-1367 |
|
|
|
|
|
|
|