On 24.03.2009, at 5:29, Stu wrote:
> I suspect I'm having "stack level too deep" type crashes with DM > because of this. it is impossible to say without seeing a stack trace and your code that causes it > What's the best way to approach this situation in > DM? I have already placed the DM model classes in their own module > but that hasn't helped. it looks like the problem is with something else DM 0.9.10 has a known bug that causes stack overflow, but it is impossible to say without stack trace DM 0.10.0 (next branch) is free of this problem, but may or may not be ready to use depending on what gems from dm-more you would need In general, namespacing with modules should be enough for any class name collisions you may have in Ruby code 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 -~----------~----~----~----~------~----~------~--~---
