Hi Pete, Try dropping the 'constrained' attribute from the <one-to-many>'s in User > if I remove 'contrained' attribute on User side, NHibernate would force fetch=join when loading users, just to discover whether each related entity actually exists (so to build a lazy-ready proxy) or not (set related attribute to null). This allows to preserve a NHibernate invariance, as well explained by Ayende<http://ayende.com/blog/3960/nhibernate-mapping-one-to-one> . In my case, when fetching a User I would get a (often useless) join on 6 tables more. I would like to avoid this behaviour.
Thanks for your answer, Marcello. -- You received this message because you are subscribed to the Google Groups "nhusers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/nhusers?hl=en. For more options, visit https://groups.google.com/groups/opt_out.
