Hello Michael, do you have any clue about this problem? This DataMapper behavior can break a system in scenarios similar to the one I reproduced in the TestCase. I judge this as a serious problem in DataMapper. Please, just let me know if the DataMapper team will handle this issue and how. I'm willing to help as much as possible.
Best regards, Matevž Rostaher On 23 mar., 15:25, Matevz Rostaher <[email protected]> wrote: > Michael, > > no it doesn't cause infinite recursion. If you run the test i provided > in my original post, you'll see that a1.assoc1.first answers nil > instead of b. I tried this also with the latest revision from git and > the result is the same. > If I first navigate to b with a1.assoc1.first and after that load b > using the primary key b = ObjectB.get(1) and compare, than everything > is ok. So, the order of operations is very important here. > > Best regards, > Matevz > > On Mar 16, 11:47 am, Michael Klishin <[email protected]> > wrote: > > > On 16.03.2009, at 12:08, Matevz Rostaher wrote: > > > > The problem is best described with the test at the bottom of the > > > message > > > Matevz, > > > I guess it causes infinite recursion and stack overflow. It is a known > > bug in 1:n associations in 0.9.10. > > > Could you try to reproduce with 0.10 (from git)? Thank you. > > > MK --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
