ObjectDB ObjectDB

Internal Website Search

131-140 of 194 resultsRefresh

Selective merge/cascade of detatched entity

the same EntityManager for all threads, but this will likely introduce locking/synchronize issues

ObjectDB version 2.1 has been released

the download). Added support of disabling optimistic locking exceptions. Added support of url

Updating Entities

._OptimisticLockException: Optimistic lock failed for object application.model.Paygrade#184 (object has version 86 instead

Wrong select results

="." max="128mb" /> <recording enabled="false" sync="false" path="." mode="write" /> <locking version

Should I use ObjectDB and JDO?

object locking was more capable than JDO's. JPA turned out to be the right choice for me. I

Query results are not up to date for entities, not primitives

" />   <locking version-check="true" />   <processing cache="1024mb" max-threads="80" />   <query-cache

Embedded & Activation & Scalation

folder, however I've got a few questions I couldn't find answers for: How will locking take place

OutofMemory error with Object DB 2.0

="write" /> <locking version-check="true" /> <processing cache="64mb" max-threads="10" /> <query

Removed entities can be found by query in the same transaction

optimistic lock exception) but you may want to check if it also solves this issue. support Support

ObjectDB 2.3.2

) and then updated. Fixed retrieval with pessimistic lock to bypass cache and to force refresh.

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