Home » Search

About strong

1-10 of 26 Refresh
Manual
81

Entity Management Settings

", "soft" and " strong". Modified entities are always held by strong references in the persistence
Manual
20

ObjectDB Developer's Guide

(SQL, JDBC, ORM or JPA) is not required in order to follow this guide, but a strong background
Manual
20

Working with JPA Entity Objects

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

Soft Reference Object Cache Recommendation

to have my code called to manipulate the softReferenceData in my JdoBlob2 instances, so there is a strong ... is due to ObjectDB datastore page file cache keeping strong references to the pages that comprise the data ... and you expect to be released? Can you see a path of strong references from a root that holds
Forum
4

evictAll() behavior

- but it is less efficient and has some limitations. For example, strong references to your objects ... (unlike makeTransient / makeTransientAll).  ObjectDB doesn't hold strong references to hollow objects, so if your application doesn't hold  strong references either - they can be garbage collected
Forum
4

Caching/Paging Questions...

of its result objects already created and reside in memory ? Q2: Do I need to manually use strong ... ). You can either use application managed strong references or you can set the configuration, so strong references ... references, which are something in the middle between weak and strong references. The size of the L1
Forum
4

Entity Management Config questions

as a first level cache). The valid values are "weak", "soft" and " strong". Modified entities are always hold by strong references in the persistence context (until commit or flush), regardless of this setting. Question: What exactly is the difference between "weak", "soft", and " strong" references
Issue
2

TYE NullPointerException

a collection after it releases the last strong reference to the containing entity object? Following ... a strong reference to the containing entity - so this unexpected state would be avoided. felixobjectdb
Issue
2

Use temporary files to enable very large transactions

whether it should be referenced by ObjectDB using a strong references or a weak references. A check now ... references as expected. However, new flushed objects are set to have strong references
Issue
2

Unexpected exception (Error 990) com.objectdb.o.InternalException

();         em.persist(new MyEntity());         em.getTransaction().commit();         // Keep a strong ... ().commit();         // Keep a strong reference to the embeddable but free the entity:         List