From: Fabio Maulo
Sent: Saturday, August 15, 2009 11:39 PM
To: nhusers@googlegroups.com
Subject: [nhusers] Re: Lazy load of one-to-one association
let your app choose which is the real relationship and configure it as
many-to-one for persistence scope (that is one of the reasons to use a
persist
witter: http://twitter.com/jeffz_cn
--
From: "hival"
Sent: Saturday, August 15, 2009 11:46 PM
To: "nhusers"
Subject: [nhusers] Re: Lazy load of one-to-one association
>
> Hmm...
> Here is my mapping and SQL (NH2.
er.com/jeffz_cn
--
From: "hival"
Sent: Saturday, August 15, 2009 11:46 PM
To: "nhusers"
Subject: [nhusers] Re: Lazy load of one-to-one association
>
> Hmm...
> Here is my mapping and SQL (NH2.1.0)
>
> asse
Hmm...
Here is my mapping and SQL (NH2.1.0)
Parent
> Twitter: http://twitter.com/jeffz_cn
>
> --
> From: "hival"
> Sent: Saturday, August 15, 2009 11:09 PM
> To: "nhusers"
> Subject: [nhusers] Re: Lazy load of one-to-one association
>
> >
>
Tried but nothing changed.
Blog: http://www.cnblogs.com/JeffreyZhao/
Twitter: http://twitter.com/jeffz_cn
--
From: "hival"
Sent: Saturday, August 15, 2009 11:09 PM
To: "nhusers"
Subject: [nhusers] Re: Lazy load of on
Try to specify constrained="true" in the User's side of the association.I'm not sure whether it is correct but it works. It
seems that NH doesn't look at the other side of the one-to-one assoc.
to find out whether the assoc. is optional or not.
--~--~-~--~~~---~--~--
