On Aug 3, 1:29 pm, Jason Meckley <[email protected]> wrote: > What you describe may be a better candidate for a document database
I have also considered a document database for this and have been looking at both MongoDb and RavenDb prior to my colleague's NHibernate suggestion. I agree it does seem to make the most sense but it's a tough sell managerial staff (and devs, myself included, for that matter) that have been thinking in relational database terms for so long (though I might be able to sell it on not needing expensive SQL Server/Oracle licensing!) Also, it does still seem to be in its infancy, at least as far as monitoring, maintenance and profiling goes. On Aug 3, 12:52 am, Diego Mijelshon <[email protected]> wrote: > No, NH will not do that. Looking at it from another angle, would the following class (with a suitable one-to-one mapping between PocoA and PocoB; and a suitable one-to-one mapping between PocoA and PocoC) generate a single-level SELECT statement and populate correctly from a single returned row? public class PocoA { public virtual long ID { get; set; } public virtual PocoB Foo { get; set; } public virtual PocoC Bar { get; set; } } If so, would the same SELECT and population occur if PocoA did not know about PocoB and only PocoB's mapping defined the one-to-one to PocoA (i.e. if PocoB was in a different assembly)? If so, could NHibernate infer a one-to-one relationship between PocoB and PocoC, given that both have a defined one-to-one mapping to the same field on PocoA? -- 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.
