Home » Search

About inverse

21-30 of 61Refresh
Forum
3

find() delay

" (inverse) field is retrieved from the database again (as done by "codes-2" and "codes-3"). Please see the documentation on inverse fields and also this forum thread. Thanks for you hints. I read this forum thread and find the active method you mentioned. If I have to maintain the inverse fields
Forum
3

How storage works?

is annotated as inverse (mapped by) the entity object in which the collection is defined (Car) is not stored ... is stored (Wheel). If the collection is not defined as inverse (mapped by) the entity object in which the collection is defined has to be stored. Using direct collections (not inverse / mapped by
Forum
3

mappedBy problem

!!   There was a bug in cascading operations through inverse (mapped by) fields - thank you for your report ... a request to execute a query). You are right about the Explorer. Currently inverse (mapped by) fields ... - storing a relationship based on the inverse side (Employee) is against the standard. Support of inverse
Forum
3

Problem persisting a TreeSet field

for ordinary persistent fields - but mapped by (inverse) fields are more limited. The order of elements in a mapped by (inverse) collection field is set by an automatic query. You can define the field ... an inverse field - remove he mappedBy setting, and update the TreeSet explicitly - ObjectDB doesn't need
Forum
3

Problem with @OrderBy

inverse WHERE inverse = ?1 ORDER BY owner.seqRel, ==> noteSeq <== javax.persistence ... multiple order expressions in inverse (mapped by) fields. Version 2.2.2 includes a fix - please try it. Thank you for your report. 2.2.2 fixed the problem
Forum
3

TimeSeries and ObjectDB

, post #5 regarding Embedded vs. Inverse Collections. Thanks so if I understand correctly - it would be better to use conventional inverse (mapped by) collection. I will get the following benefits: 1 ... limit) right? A more general question: if the database is using indexes efficiently - the inverse
Issue
3

Unexpected Exception during commit

, during commit an attempt to cascade persist through an inverse (mapped by) collection field fails. I ... . On the next line other references that are related to the inverse field are used. Maybe that inverse reference
Result
2

ObjectDB version 2.0.0

of ID / version / inverse (mapped by) fields. Fixed Explorer bug in closing database files. Fixed cascading through inverse (mapped by) fields. Fixed some bugs in automatic schema evolution. Fixed
Result
2

ObjectDB version 2.3.3

first commit (issue #562). Fixed a NullPointerException in accessing inverse (mapped by) collection ... NullPointerException on accessing an inverse collection in an entity that has been garbage collected (issue
Result
2

ObjectDB version 2.4.5

Version 2.4.5 Added support of lazy loading of mapped by (inverse) singular relationships (issue #768). Added support for using ObjectDB with TomEE / OpenEJB. Improved loading of eager mapped by (inverse) relationships (issue #769). Improved performance of database file extending. Fixed a bug in