On 24 February 2012 02:01, John Hinnegan <[email protected]> wrote: >Our test environments do not have millions of records, so we're unlikely to >catch an > error until we push to production and see our systems grind to a halt.
Then they're not very good test systems. They should be as close a possible to production to highlight exactly this kind of thing. > vs having to always worry that our new guy will write perfectly valid > code and we'll just forget that you can't use that code on that model. Code reviews? Training? I'm sorry to say I don't think my post directly answers your issue (have you tried aliasing/overloading AR::Base.find?), but that's because I think your solution is dealing with the symptoms rather than the core of your problem. -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" 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/rubyonrails-talk?hl=en.
