>From your mail:"this returns a Post entity with a join on Publication BUT
not on Region"

2009/4/30 graphicsxp <[email protected]>

>
> Do you mean on the theSource property of my Post class ?
>
> If so, here's what it looks like at the moment :
>
>  <many-to-one class="Metrica.Source,Metrica" name="thePublication"
> cascade="all-delete-orphan" column="PublicationID" />
>
> does 'all' not include merge already ?
>
>
> On 30 avr, 17:52, Fabio Maulo <[email protected]> wrote:
> > cascade="merge"
> >
> > 2009/4/30 graphicsxp <[email protected]>
> >
> >
> >
> >
> >
> > > Hi,
> >
> > > I carry on with my series of posts about fetching strategy issues ....
> >
> > > class Post
> > > {
> > >  Publication thePublication
> > > }
> >
> > > class Publication
> > > {
> > >  Region theRegion
> > > }
> >
> > > class Region
> > > {
> > > }
> >
> > > if I set the fetch policy of the many-to-one property in Publication
> > > mapping :
> > > <many-to-one fetch="join" class="Metrica.Region, Metrica"
> > > name="theRegion" column="RegionID" />
> >
> > > When I get a Post, NH does the join on Publication and Region.
> >
> > > However when I call mySession.Merge(myPost), this returns a Post
> > > entity with a join on Publication BUT not on Region, therefore the
> > > property theRegion is not loaded...
> >
> > > Is this expected behaviour ? I would have thought that Merge would do
> > > exactly what the mapping file says....
> >
> > --
> > Fabio Maulo
> >
>


-- 
Fabio Maulo

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"nhusers" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to 
[email protected]
For more options, visit this group at 
http://groups.google.com/group/nhusers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to