Gotcha. The only problem with that is that there is no guarantee that
getToHouse() exists... the flattened relationship could span
DbRelationships that don't have corresponding ObjRelationships.
So maybe the answer is there isn't a good answer :)
On 10/3/05, Andrus Adamchik <andru..bjectstyle.org> wrote:
> or rather:
>
> public City getToCity() {
> return getToHouse().getToCity();
> }
>
> If we follow your example...
>
> Andrus
>
> On Oct 3, 2005, at 5:41 PM, Andrus Adamchik wrote:
>
> >
> > On Oct 3, 2005, at 5:32 PM, Cris Daniluk wrote:
> >
> >
> >>> Hmm... I haven't looked at the case of flattened relationships
> >>> overlapping with regular ObjRelationship. Maybe we should generally
> >>> treat them as cover methods without any DB magic? Otherwise you'd
> >>> have your object graph easily messed up (I had such bad experience
> >>> with EOF).
> >>>
> >>>
> >>
> >> Not following what you mean when you say cover methods..
> >>
> >
> >
> > Here is an example:
> >
> > Collection getCities() {
> > return getHouse().getCities();
> > }
> >
> >
> > Andrus
> >
> >
>
>
This archive was generated by hypermail 2.0.0 : Mon Oct 03 2005 - 17:48:29 EDT