I'm looking at using the Sharding stuff that NHibernate Contrib provides but noticed a bit of functionality that seems to missing. However it seems so fundamental to me that I wonder if there is some obvious reason that it's not there...
I've been able to implement sharding for a single object but when I added a many-to-one relationship things start going a bit "wrong". Specifically I insert one "parent" object and three "children" with the "children" each being located in a seperate Shard. All goes fine until a attempt to load the "children" when 2 of the 3 get an object not found exception on the "parent". As I understand it this all refered to as a "cross-shard object graph" and appears to be unsupported but I don't understand why? If it's just time then fine I'll probably look to contribute and get this functionality added in but is there some deep rooted reason this is a bad idea? -- You received this message because you are subscribed to the Google Groups "NHibernate Contrib - Development Group" 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/nhcdevs?hl=en.
