About L2

11-20 of 26Refresh
Forum
5

OptimisticLockException

any object before I modify it??   You can disable the L2 cache (or empty it with evict) and empty ... is globally locked at the database when retrieved from L2 cache ? b) If process B attempts to modify ... refresh objects in the L2 cache?     so far the following works for me: 1) standard config file
Forum
4

IN expression in a Criteria Query

it is throwing: com.objectdb.o.UserException: Unexpected query token ':l2' Does anybody have any idea ... . Here is complete stack trace: com.objectdb.o.UserException: Unexpected query token ':l2' com.objectdb.o ... =":" code="7" postion="103:104">                    
Forum
4

Is 2 level cache in use?

if the L2 cache is enabled directly but you can check its content, by using emf.getCache().contains ... . The L2 cache doesn't always improve performance. It depends on the application. Sometimes enabling the L2 cache may slow the application because of the overhead in keeping it up to date and the memory
Forum
3

can't get HashMap out of the database

);     GuestHolder hld = new GuestHolder();     Guest tst = new Guest("testname");     Guest l2 = new Guest("level 2");     tst.addGuest(l2);     Guest l3 = new Guest("level 3");     l2.addGuest(l3);     hld
Forum
2

Caching/Paging Questions...

size of ObjectDB L2 cache or EntityManager context ? Q4: Would paging result sets ... cache is automatic. There is no limit on the maximum size of the L2 cache. Using setFirstResult
Forum
2

find() delay

a transaction of em. Maybe different EntityManager instances are used and the L2 cache is enabled. L2
Result
2

ObjectDB version 2.2.2

Version 2.2.2 Changed log format to include date and time. Changed class loader management. Fixed handling multiple order expressions in inverse (mapped by) fields. Fixed the behavior of CacheStoreMode setting in L2 shared cache. Fixed TreeSet and TreeMap element comparison bugs. Fixed an Explorer
Result
2

ObjectDB version 2.2.7

Version 2.2.7 Added support of report generation using BIRT. Fixed a bug in query optimization of DISTINCT. Fixed a bug in keeping removed entity object in the L2 cache. Fixed orphan removal of owner entity object in bidirectional relationship. Fixed an "Attempt to persist a reference to a non
Forum
2

@Convert is not supported?

that it is a singletone...   Suppose I dont have this feature, (and L1 or L2 cache is not a guarantee
Forum
2

Delete object from collection versus delete from JPQL

queries After using these queries you may use refresh, or discard cached objects in the EntityManager and in the L2 cache.  greymatter