Notice: this Wiki will be going read only early in 2024 and edits will no longer be possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.
EclipseLink/Development/Incubator/Extensions/MaxDBPlatform
Note: This page describes an extension of EclipseLink that is part of the EclipseLink incubator. Incubator projects are published so the community can use them either to progress towards having them included in the main product, or to use in their own implementations. They have been tested to varying levels and as such, we recommend doing your own testing before including any of this code in a production-level product.
Contents
Bug
- bug 284657 Support for MaxDB / SAPDB
Description
This is a subclass of DatabasePlatform that can be used by customers using the MaxDB database.
Documentation
MaxDB uses URL that may contain the ampersand (&) character, e.g.
jdbc:sapdb://localhost/E32?spaceoption=true&unicode=yes
Please make sure that this character is escaped properly in XML files.
In order to execute the eclipselink tests, the ampersand must also escaped in an URL contained in a test.properties file.
Location
Level of Testing
September 21/2010
- EclipseLink 2.2.0 (trunk) current build (revision: 8220)
- DB: MaxDB, kernel 7.8.01 build 004-123-218-928
- JDBC driver: MaxDB JDBC Driver, Make-Version: 7.8.01 Build 004-123-218-928
| Test Name | Tests | Failures | Errors |
|---|---|---|---|
| Core SRG | 691 | 0 | 5 |
| JPA SRG | 202 | 0 | 7 |
| JPA WDF | 815 | 0 | 0 |
| Core LRG | 7440 | 0 | 45 |
| JPA LRG | ? | ? | ? |
| Server LRG (GlassFish v3) | ? | ? | ? |
Details on Errors/Failures
Core SRG
Test Case: org.eclipse.persistence.testing.tests.SRGTestModel
| Test Name | Bug | Description/Reason |
|---|---|---|
| MultiPlatformTest5 | bug 316774 | coalesce is not recognized as function |
| ScrollableCursorNavigationAPIConformingTest | Cursor Navigation produced incorrect results. cursor.last() does not result in cursor.isLast() returning true. | |
| PessimisticLockTest(mode=1) | bug 325839 | MaxDB can not do select for update with more than one table |
| PessimisticLockEmptyTransactionTest | bug 325839 | Same as PessimisticLockTest(mode=1) |
| QueryTimeoutTest | MaxDB does not recognize timeout settings on statement level |
JPA SRG
Test Case: org.eclipse.persistence.testing.tests.jpa.advanced.EntityManagerJUnitTestSuite
| Test Name | Bug | Description/Reason |
|---|---|---|
| testPESSIMISTIC_READLockWithNoChanges | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
| testPESSIMISTIC_WRITELockWithNoChanges | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
| testPESSIMISTIC_ExtendedScope | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
| testPessimisticLockHintStartsTransaction | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
| testLockWithJoinedInheritanceStrategy | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
| testPESSIMISTIC_FORCE_INCREMENTLock | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
| testGetLockModeType | bug 325839 | Same as PessimisticLockTest(mode=1) in Core SRG |
Older Test Runs
- July, 16, 2010 WDFd Test suite runs with 3 issues (all to be skipped)
- TestSetFunctions.testSum, TestSelectListTypes.testSumBigDecimal - The test calculates sum() of a BigDecimal attribute. The return type should be BigDecimal but Double is returned instead. https://bugs.eclipse.org/bugs/show_bug.cgi?id=320120
- TestGroupByOrderByHaving.testSubQueryGroupBy3 - The test assumes that an error is detected in the query but the execution succeeds on MaxDB. The query in question is "SELECT t0.ID, t0.COOL, t0.NAME, t0.TYPE, t0.CITY_ENUM, t0.CITY_TESLA_INT, t0.CITY_TESLA_BLOB FROM TMP_CITY t0 WHERE EXISTS (SELECT 1 FROM TMP_COP t2, TMP_COP t1 WHERE (t2.ID = t1.PARTNER_ID) GROUP BY t1.ID HAVING (t2.ID = 5))". Actually, it should fail on the database as t2.ID is no grouping column. Seems to a MaxDB issue. The test will be skipped on MaxDB.
- June 22, 2010 SRG Test suite runs with MaxDb except 3 problems
- MultiPlatformTest5 fails because coalesce is not recognized as function see bug 317286
- PessimisticLockTest(EmptyTransactionTest) can not work because MaxDb can not do select for update with more than one table
- QueryTimeoutTest does not work because MaxDb does not recognize timeout settings on statement level
- Sept 3, 2009 - Initial check-in from TopLink Essentials Class - compile-only, no database-level testing. Initial development was done on TopLink Essentials, so there may be some changes needed to even make existing functionality work
Location of tests and examples
No specific tests or examples have been written