About reference

1-10 of 200Refresh
JPA Doc
336

JPA Reference (JavaDoc) [2018-08-18]

This reference contains the API documentation (similar to JavaDoc) of the Java Persistence API (JPA) 2.0. The content is derived from the original JPA documentation (in the EclipseLink JPA 2 RI ... into the following sections: The purpose of these documentation pages is to serve as a reference. In
JPA Doc
336

JPA Reference (JavaDoc)

This reference contains the API documentation (similar to JavaDoc) of the Java Persistence API (JPA) 2.0. The content is derived from the original JPA documentation (in the EclipseLink JPA 2 RI ... into the following sections: The purpose of these documentation pages is to serve as a reference. In
JDO Doc
333

JDO Reference (JavaDoc) [2018-08-18]

This reference contains the API documentation (similar to JavaDoc) of JDO 2.2. The content is derived from the original JDO documentation with some additions and notes. The most basic JDO types are: All the other JDO types are organized into the following sections:
JDO Doc
333

JDO Reference (JavaDoc)

This reference contains the API documentation (similar to JavaDoc) of JDO 2.2. The content is derived from the original JDO documentation with some additions and notes. The most basic JDO types are: All the other JDO types are organized into the following sections:
Forum
37

Soft Reference Object Cache Recommendation

[] and instruct ObjectDB to use soft reference for its Level One (L1) object data cache.  I disable the L2 ... [] and uses a soft reference to make that array eligible for GC when the JVM does a full GC. private ... reference to the byte[] when data needs to be written back to ObjectDB datastore, and a soft reference
Forum
35

Update Entity references if we change the type of an entity

. As example (like in the attached example): We have an EntityA that have a reference to an EntityB ... , because it's possible that many other entities have just a ID based reference with a simple 'int' field to this element. And we thought that also the real references are based on the ID. This step
Forum
34

Handling deleted references

" instances? This would simplify my use case since all I have to do is to check if the reference is null ... other value) should be done in the same transaction, to avoid a reference from User to a deleted Profile ... where we cannot check for further references (e.g. if the same Profile instance is used twice in 2 different
Forum
34

Broken @ManyToOne reference

and persisted: a Parent and a Child, the Child instance references the Parent instance in the prn ... is retrieved. Now it has null in the prn field. The output shall look like: Parent reference written: testobjectdb.Parent@e425743 Parent reference read back: null Regards, Vladimir The model in the test
Issue
34

Lazy loading of mapped by (inverse) singular references

. For ordinary reference fields the type of the references is stored within the entity objects, so it is always available. For mapped by (inverse) reference fields no information is stored in the entity ... object with inverse fields tracking which inverse fields have been loaded and references
Issue
34

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

a transaction (including the entity manager) the ODB file writer still holds a reference to entities. Performing similar calls repeatedly hence increases the number of references to entities not longer needed in ... still holds references to entities although it is not needed. We did following: All entities