Skip to main content

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.

Jump to: navigation, search

EclipseLink/Development/Incubator/Extensions/HANAPlatform

< EclipseLink‎ | Development‎ | Incubator‎ | Extensions
Revision as of 07:03, 11 December 2012 by Sabine.heider.sap.com (Talk | contribs) (12. September 2012)

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.

Bugs

  • bug 380226 (Database Platform for SAP HANA Database) - Initial bug for taking HANAPlatform to the incubator (resolved)
  • bug 383862 (Preparing Database Platform for SAP HANA Database for Promotion into trunk) - Bug for collecting/tracking test issues

Description

This is a subclass of DatabasePlatform that can be used by customers using the SAP HANA database.

Documentation

TBD

Limitations of the Platform

  • Reserved SQL keywords cannot be used as table, column or sequence names. Use a different name, or enclose the name in double quotes. For example: @Column(name="\"LANGUAGE\"")
  • Pessimistic locking adds 'FOR UPDATE' to the SELECT statement, and cannot be used with queries that use DISTINCT.
  • Pessimistic locking cannot be used with queries that select from multiple tables - see bug 384129
  • The LockNoWait option of Pessimistic Locking cannot be used; it is ignored when specified (i.e. only 'FOR UPDATE' is added to the SELECT statement).
  • Bulk update and delete operations that require multiple tables to be accessed cannot be used (e.g. bulk operation on an entity that is part of an inheritance hierarchy, UpdateAll and DeleteAll queries).
  • '= NULL' and '<> NULL' cannot be used for null comparisons in the WHERE clause. Use 'IS (NOT) NULL' instead.
  • Scrollable cursors are not supported - see bug 384116.
  • Query timeouts are not supported - see bug 384135.

Location

TBD

Level of Testing

11. December 2012

  • EclipseLink master (commit b0202ac783b3920b362d77c75245e7d34b765bc1) + HANA Platform (commit 89106f515530b763a76179832b8e1fbcbc17f58e) + patches from the following bugs: bug 396259
  • DB: SAP HANA 1.00.31.362930
  • JDBC Driver: SAP In-Memory Database JDBC Driver 1.00.31 Build 0362930-1510
Test Name Tests Failures/Errors
Core SRG 693 0
Core LRG 8001 3
JPA SRG 244 0
JPA LRG 2902 14
JPA WDF 852 1
Server LRG (GlassFish v3)  ?  ?

Details on Errors/Failures

Core LRG
Test Name Bug Description/Reason
org.eclipse.persistence.testing.tests.feature.CacheStatementBatchWritingTest.CacheStatementBatchWritingTest n/a Statements were not cached correctly
org.eclipse.persistence.testing.tests.queries.QueryFrameworkTestSuite$5.JoinSubclassesQueryTest n/a Invalid argument resultSetType, use TYPE_FORWARD_ONLY
org.eclipse.persistence.testing.tests.queries.QueryFrameworkTestSuite$5.JoinSubclassesQueryTest n/a Invalid argument resultSetType, use TYPE_FORWARD_ONLY
JPA LRG
Test Name Bug Description/Reason
org.eclipse.persistence.testing.tests.jpa.advanced.JPAAdvancedTestModel.JPAAdvancedTestModel n/a sql syntax error
org.eclipse.persistence.testing.tests.jpa.criteria.AdvancedCriteriaQueryTestSuite.testCursors n/a Invalid argument resultSetType, use TYPE_FORWARD_ONLY.
org.eclipse.persistence.testing.tests.jpa.criteria.AdvancedQueryTestSuite.testCursors n/a Invalid argument resultSetType, use TYPE_FORWARD_ONLY.
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testAssociationOverrideToEmbeddedManyToMany n/a invalid column name: invalid column name: JUSTTOTEST
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testAssociationOverrideToEmbeddedManyToMany n/a invalid column name: invalid column name: JUSTTOTEST
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testDDLUniqueKeysAsJoinColumns n/a invalid column name: B_CODE
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testDDLUniqueKeysAsJoinColumns n/a invalid column name: B_CODE
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testDeleteObjectWithEmbeddedManyToMany n/a invalid column name: JUSTTOTEST
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testDeleteObjectWithEmbeddedManyToMany n/a invalid column name: JUSTTOTEST
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testManyToManyWithMultipleJoinColumns n/a invalid column name: B_CODE
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testManyToManyWithMultipleJoinColumns n/a invalid column name: B_CODE
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testPrimaryKeyJoinColumns n/a invalid column name: NAME
org.eclipse.persistence.testing.tests.jpa.ddlgeneration.DDLGenerationExtendTablesJUnitTestSuite.testPrimaryKeyJoinColumns n/a invalid column name: NAME
org.eclipse.persistence.testing.tests.jpa.jpql.AdvancedQueryTestSuite.testCursors n/a Invalid argument resultSetType, use TYPE_FORWARD_ONLY
JPA WDF
Test Name Bug Description/Reason
org.eclipse.persistence.testing.tests.wdf.jpa1.generator.TestSequence.testAllocSize n/a wrong allocation expected:<4> but was:<2>

Location of tests and examples

No specific tests or examples have been written

Back to the top