Paul, > Is there a fix on the horizon?
We take performance regressions fairly seriously. If you're seeing a problem I can look at it this week, and hopefully get a fix before the 1.0.1 release in the next week or so. > Any quick and dirty hack I can use to get around this in the interim? Nothing that immediately comes to mind, but I'll let you know. > My relationships are all relating the > models to each other using their primary keys, I would think it would > be easy to make this work with the identity map since they would exist > already by PK. First thing though, can you create a ticket to track this issue: http://datamapper.lighthouseapp.com/projects/20609-datamapper/tickets/new The next thing I would ask is a small stand-alone script that demonstrates the problem, with perhaps some comments on your expected behaviour. This makes sure that I can see what you're seeing. Without it, I might end up spending alot of time looking for nonexistent problems in other parts of the system. Another benefit is that I can use the script to create a spec to ensure the regression never happens again. Also sometimes when I'm doing a code spike to figure out how to approach a fix I'll use the stand-alone scripts to get feedback on whether or not I'm on the right track.. then I revert the spike, write a real failing spec, and fix the problem properly. -- Thanks, Dan -- 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.
