On Jul 24, 2012, at 9:59 , Ylan Segal wrote: > Can you post how to recreate your problem? Maybe an example app? My quick > test on a 3.1.1 app didn't show this problem.
No. Isolating the cause is the sort of "grubbing around" I was hoping to avoid. The problem doesn't occur most of the time. FWIW, I get the object that's misbehaving from a simple find by ID, which I'm doing in a mix-in on its class. And it's only happening in staging (not in any of my tests, say :-) ). It's the damnedest thing. -- SD Ruby mailing list [email protected] http://groups.google.com/group/sdruby
