ObjectDB Database Search

(which serves as a first level cache). The valid values are "weak" , "soft " and " strong ". Modified entities are always held by strong references in the persistence context (until commit or flush

it and it is automatically removed from the persistence context. ObjectDB can be configured to use strong

this guide, but a strong background and understanding of the Java language is essential

, so there is a strong reference to the byte[] when data needs to be written back to ObjectDB datastore ... datastore page file cache keeping strong references to the pages that comprise the data of the byte ... ? Can you see a path of strong references from a root that holds that  byte[] from being garbage

with no enhancement as an extension to JDO - but it is less efficient and has some limitations. For example, strong ... ).  ObjectDB doesn't hold strong references to hollow objects, so if your application doesn't hold  strong references either - they can be garbage collected. support Support evictAll - i

are "weak", "soft" and " strong ". Modified entities are always held by strong ... . Question : What exactly is the difference between "weak", "soft", and " strong " references? dmoshal ... /understanding-weak-references For more information, please see: https://www.google.com/search?q=java+ strong +weak+soft+reference&gws_rd=ssl support Support

of its result objects already created and reside in memory ? Q2: Do I need to manually use strong ... (but the difference is not huge). You can either use application managed strong references or you can set the configuration , so strong references will be used automatically until the persistence context is cleared

, if you create EntityManagerFacotry instances but do not close all of them, or still have strong references ... using strong references and somehow still reference EntityManager instances. To check

a query (and has no real value in the database). Anyway, you will have strong static typing

changing the default reference cache configuration from weak to soft or strong . However, notice

Pathak The question is who holds the  com.objectdb.o.ENT instances with strong references

with an helper ENT object.  entityManager.clear() should release strong references to ENT objects

, so everything is already transient, just that ObjectDB sets a permanent strong reference from B

_es BTC EmbeddedSystems This regression was caused by a change in 2.6.4_04 from strong to weak

to see were are the strong references that hold them in memory. support Support

.  Are there strong JPA-like libraries for Scala, or should I be considering Scala-specific

(SQL, JDBC or JDO) is not required in order to follow this guide, but a strong background

instance, in any context, to return its associate Transaction object. The strong

store transactions (which is the default in ObjectDB), there is a strong relationship between

? With enhanced classes ObjectDB is not expected to hold strong references (which prevents garbage ... and paths of strong references from roots to objects? support Support @Entity class MyStepBlockCollection ... with strong references, so hopefully the heap dump could help in understanding the issue. support Support

inconsistency. Is it possible that your application uses a collection after it releases the last strong ... is included now in build 2.3.2_01. Lazy collections will always hold a strong reference to the containing

;  // Keep a strong reference to the embeddable but free the entity:      ... .getTransaction().commit();         // Keep a strong reference

documentation. 1) makes working with a product so much harder 2) suggests a strong possibility

. support Support Just an update to confirm my very strong interest in this feature. We simply can't

reflection mode ObjectDB has to keep some strong references to objects, which are weak references when entity classes are enhanced. support Support

with strong references from GC roots. support Support We have scenarios in which we open up to lots

BTC EmbeddedSystems It is unclear from these images if there are paths of strong references from