About lock

161-170 of 179Refresh
Forum
1

Updating Entities

get an odd error message... Caused by: com.objectdb.o._OptimisticLockException: Optimistic lock failed
Issue
1

Use temporary files to enable very large transactions

" />                 <locking version-check="true" />                
Forum
1

Vs. EHCache

. Unfortunately we don't have such information. But if you don't need transactions, lock management, durability
Forum
1

Weird behaviour with enhanced classes and embedded entities

() to the proxied list (I am pretty sure I do the locking/synchronizing the right way
Forum
1

WORM (Write once read many) support

would be locked. Would this functionality you requested be enough for runing objectDB.  regards. emil_peric
Forum
1

Wrong select results

="." mode="write" />   <locking version-check="true" />  
Result
1

ObjectDB version 2.2.8

(issues #365, #366, #368). Fixed a pessimistic locking deadlock (issue #342).
Result
1

ObjectDB version 2.3.2

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

ObjectDB version 2.4.0

. Fixed a bug in optimistic locking on find by using LockModeType.WRITE. Fixed exception
Result
1

ObjectDB version 2.2.1

Added support for using ObjectDB with JBoss AS 6.0 / 6.1. Fixed several bugs in handling eager fetch. Fixed a pessimistic locking bug. Fixed a bug in using primary key fields in queries. Fixed a bug in queries on deleted objects before commit / flush.