Skip to main content

Notice: This Wiki is now read only and edits are no longer possible. Please see: https://gitlab.eclipse.org/eclipsefdn/helpdesk/-/wikis/Wiki-shutdown-plan for the plan.

Jump to: navigation, search

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.

Related bugs

  • bug 284657 Support for MaxDB / SAPDB
  • bug 315394 prepare to support MaxDbPlatform
  • bug 316774 coalesce can not be overwritten by a db-platform
  • bug 317286 DB column lenght not in sync between @Column and @JoinColumn
  • bug 317597 @Lob annotation is not recognized by forwardmapper

Description

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

Documentation

even in the test.properties file xml special characters must be escaped, because the properties are converted at some point in time e.g. the url can look like:

jdbc:sapdb://localhost/E32?spaceoption=true&unicode=yes

Location

svn+ssh://dev.eclipse.org/svnroot/rt/org.eclipse.persistence/incubator/extensions/trunk/org.eclipse.persistence.platform.database.maxdb

Level of Testing

  • 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
  • June 22, 2010 SRG Test suite runs with MaxDb except 3 problems
  1.  MultiPlatformTest5 fails because coalesce is not recognized as function see bug 317286
  2.  PessimisticLockTest(EmptyTransactionTest) can not work because MaxDb can not do select for update with more than one table
  3.  QueryTimeoutTest does not work because MaxDb does not recognize timeout settings on statement level

Location of tests and examples

No specific tests or examples have been written

Back to the top