About strong

21-30 of 30Refresh
Issue
1

Navigation through lazy loading from Detached Objects

an update to confirm my very strong interest in this feature. We simply can't use our EclipseLink
Issue
1

ObjectDB 2 JDO Manual

working with a product so much harder 2) suggests a strong possibility that you are considering removing
Forum
1

OutofMemory error with Object DB 2.0

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

Persistent domain in Scala or Java...

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

Storing Images and Object Pooling

to soft or strong. However, notice that objects are cached as objects per EntityManager
Forum
1

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

" />    
Issue
1

ODB-FileWriter holds unecessary entity reference after transaction and entity manager are closed

information for the MSF/MST/PGC instances with strong references from GC roots. We have scenarios in
Result
0

ObjectDB 1.0 Manual

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

[ODB1] Chapter 5 - JDO Connections

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

[ODB1] Chapter 6 - Persistent Objects

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