ObjectDB ObjectDB
Home » Search

Internal Website Search

51-60 of 200 resultsRefresh
34

PluralAttribute.CollectionType.COLLECTION

Enum Constant javax.persistence.metamodel.PluralAttribute.CollectionType COLLECTION Collection-valued attribute Since: JPA 2.0
34

PluralAttribute.CollectionType.SET

Enum Constant javax.persistence.metamodel.PluralAttribute.CollectionType SET Set-valued attribute Since: JPA 2.0
34

PluralAttribute.CollectionType.MAP

Enum Constant javax.persistence.metamodel.PluralAttribute.CollectionType MAP Map-valued attribute Since: JPA 2.0
34

SharedCacheMode.ALL

Enum Constant javax.persistence.SharedCacheMode ALL All entities and entity-related state and data are cached. Since: JPA 2.0
34

SharedCacheMode.ENABLE_SELECTIVE

Enum Constant javax.persistence.SharedCacheMode ENABLE_SELECTIVE Caching is enabled for all entities for Cacheable(true) is specified. All other entities are not cached. Since: JPA 2.0
34

SharedCacheMode.DISABLE_SELECTIVE

Enum Constant javax.persistence.SharedCacheMode DISABLE_SELECTIVE Caching is enabled for all entities except those for which Cacheable(false) is specified. Entities for which Cacheable(false) is specified are not cached. Since: JPA 2.0
34

ValidationMode.CALLBACK

Enum Constant javax.persistence.ValidationMode CALLBACK The persistence provider must perform the lifecycle event validation. It is an error if there is no Bean Validation provider present in the environment. Since: JPA 2.0
34

ValidationMode.AUTO

Enum Constant javax.persistence.ValidationMode AUTO If a Bean Validation provider is present in the environment, the persistence provider must perform the automatic validation of entities. If no Bean Validation provider is present in the environment, no lifecycle event validation takes place. This is the default behavior. Since: JPA 2.0
34

ValidationMode.NONE

Enum Constant javax.persistence.ValidationMode NONE The persistence provider must not perform lifecycle event validation. Since: JPA 2.0
34

LockModeType.PESSIMISTIC_WRITE

Enum Constant javax.persistence.LockModeType PESSIMISTIC_WRITE Pessimistic write lock. Since: JPA 2.0

Getting Started

ObjectDB is very easy to use. Follow the Getting Started Tutorial and the Quick Tour manual chapter and in minutes you may be able to write and run first Java programs against ObjectDB.

Prior knowledge or experience in database programming (SQL, JDBC, ORM, JPA, etc.) is not required, but some background in using the Java language is essential.

Need Help?

  1. Search ObjectDB website
  2. Read the FAQ
  3. Follow the Tutorials
  4. View or post in the forum
  5. Search or file an issue
  6. Contact support
ObjectDB Database Getting Started Support
DBMS Features Quick Tour with JPA ObjectDB FAQ
Editions and Prices JPA Console Tutorial ObjectDB Manual
Licence Web App Tutorial Forum
Attributions Java EE JPA Tutorial Issue Tracking
Privacy Spring MVC JPA Tutorial Website Search
Terms of Use Download ObjectDB Contact Us

Which JPA is Faster?

 

See a comparison of Hibernate, EclipseLink, OpenJPA, DataNucleus, MySQL, PostgreSQL, Derby, HSQLDB, DB4O by Versant, H2 Database, SQLite and ObjectDB

in the JPA Benchmark.

Copyright © 2003, 2010, 2024  ObjectDB Software, all rights reserved. The JPA API Reference Documentation (JavaDoc) on this website is derived with some adjustments from the open source JPA 2 RI (EclipseLink) and is available under the terms of the Eclipse Public License, v. 1.0 and Eclipse Distribution License, v. 1.0. The JDO API Reference Documentation (JavaDoc) on this website is derived with some adjustments from the JDO 2.2 API and is available under the terms of the Apache License, v. 2.0. Images on this website are available under these licecnes. Documentation on this website explains how to use JPA in the context of the ObjectDB Object Database but mostly relevant also for ORM JPA implementations, such as Hibernate (and HQL), EclipseLink, TopLink, OpenJPA and DataNucleus. ObjectDB is not an ORM JPA implementation but an Object Database (ODBMS) for Java with built in JPA 2 support.