On Jan 1, 4:45 am, "Dan Kubb (dkubb)" <[email protected]> wrote: > This is something I am working on personally. It's actually far more > difficult in DM than any other ORM that I am aware of, due to our > ability to handle multiple repositories. For example, a many to many > association, at minimum, affects 3 models. What if those three models > are in different repositories, or two are in one, and one is in > another? Many to many can actually span 3 or more models.. so what if > there are 5 models, and 5 repositories?
Dan, I am of the opinion that these complex multi-repo problems should not be attempted in v1.0. Do we really have that strong a need for it? I agree, its a very hard problem. I remember about 10 years I was working with IBM's corba/som based monster which attempted these types of things. They were dealing with database "XA" extensions to handle transactions across heterogeneous data stores. Its a killer problem space and I think it falls to the far side of the principal "Simple things should be simple, complex things should be possible". Unless there is such a strong community need for, it sounds like there is far too much on your plate to achieve this for 1.0. happy new year and thanks for all the datamapping ;) Jon --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "DataMapper" 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/datamapper?hl=en -~----------~----~----~----~------~----~------~--~---
