cayenne-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From John Huss <>
Subject Re: Auto-creation of reverse relationships
Date Mon, 12 Mar 2012 21:24:40 GMT
On Tue, Feb 28, 2012 at 10:34 PM, John Huss <> wrote:

> My entity classes use explicit fields to store data instead of a Map, so
> when it tries to access the "runtimeRelationshipX" fields it blows up
> because these don't exist in the generated java classes.  I've dealt with
> it so far by just modeling all the relationships so that the fields are
> there to hold the data.  But now I'm using more introspection and having
> these unnecessary relationships is requiring workaround that I would prefer
> not to have.
> I did try turning this off today and thus far everything seems ok, but
> there is a lot more to test to be sure.

So, just to follow up on this...  I did run into some problems - one was
when adding some prefetches to a query it would look for the reverse
relationship and blow up.  There was another occurrence elsewhere too, but
I don't recall where.  So I turned back on the creation of the reverse
DbRelationships only and that seems to work well.  These "unneeded"
DbRelationships don't hurt anything and still keep my entity classes free
of accessors for relationships that I don't want.

So my question now is, it is ok if I submit a patch to make it optional to
create the reverse ObjRelationships?  I would probably use a property to
configure it, but maybe there is a better way.


  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message