About reference

11-20 of 200Refresh
Forum
20

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
19

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
19

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
19

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
Manual
19

Detached Entity Objects

object. Cascading Detach Marking a reference field with CascadeType.DETACH (or CascadeType ... that references an instance of Address, which is another entity class. Due to the CascadeType.DETACH ... when applicable (e.g. to entity objects that the Address object references, if any). Bulk Detach
Forum
19

Mysterious "Attempt to persist a reference to a non managed instance" error

.RollbackException Failed to commit transaction: Attempt to persist a reference to a non managed failing ... .UserException: Attempt to persist a reference to a non managed failing.Ostrich instance at com.objectdb.o ... a reference to a non managed failing.Ostrich instance at com.objectdb.o.MSG.d(MSG.java:61) at com
Issue
19

spuriously objectdb objects have null references

from time to time we have in a multi threaded environment objects where all the references are null (i.e. references actions, childNodes), even after a subsequent refresh. we are using a separate ... ){ } } } ...   the reference definitions are (for the null references above): ... @OneToMany(fetch
Forum
19

Question: remove and recreate an object, do the references survive ?

it has been before, do the references from other objects survive this (assuming that no Doctor is done in between that would remove the orphane references) ?   References should survive and become valid ... . Build 2.7.5_06 adds an option to disable broken reference cleaning. Run the Doctor with this > java
Issue
19

NULL reference, how to remove

):     More information is needed about this NULL reference. Can we have access to the database? What happens when you try to access the containing entity object? How many such null references ... ? Is there new information regarding this null reference? If they are ordinary null values in the ArrayList
Forum
19

Repair broken references in entities

. Are all broken references in other entities on this removed/persisted entity repaired again? best regards ... , and then references to the old entity should point to the new one (eliminating broken references). btc_es