> > > Ah. I can see how the app uses more and more memory then. > > I assume the only way the relationship is broken is to gc the top level > object.
Alternatively, you can use ValueHolder.invalidate() on top-level (reverse) property. However, I'm not 100% sure that'll work. BTW, I tried to map a second DbEntity to the same table, but as the > name of the table is used as a key to the DbEntity that didn't work. This > would have to be in a seperate DataMap then? This is about multiple ObjEntities with sole DbEntity. This is possible
