We'll respond shortly.
David and Jonathan are having trouble with testing namespaced controllers using RSpec. They have two controllers, Admin::MyController and SuperUser::MyController, and the RSpec tests appear to be finding the wrong controller.
Their short-term solution is to put a manual require in the spec that was getting confused.
UPDATE – The issue turns out to be a naming conflict. The app has a model named SuperUser, and the existence of this model can cause class loading to be confused for SuperUser::* controllers. In Socialitis, our standard is to use plural names for controller namespace names, to prevent this sort of confusion.
Steve has learned that, in general, it’s a good idea to avoid using offsets when manipulating large quantities of data in MySQL. Luckily, some of MySQL’s quirks help with this:
You can take advantage of this behavior to paginate through a large dataset where the order doesn’t really matter. The following statements perform better than your typical LIMIT/OFFSET clause:
SELECT * FROM big_table WHERE id > 1 LIMIT 1000 SELECT * FROM big_table WHERE id > 1000 LIMIT 1000 SELECT * FROM big_table WHERE id > 2000 LIMIT 1000
acts_as_solr uses this technique for reindexing.
Here’s a link to a related blog post: