Hi, That sounds similar to the technique I was considering. Did you find much of a performance improvment here? What I am concerned with is whether the buffering exists throughout the whole ActiveRecord > ConnectionAdapter > DB Driver stack, in which case just solving the object creation in ActiveRecord::Base won't help much.
For example - look at http://dev.rubyonrails.org/browser/trunk/activerecord/lib/active_record/connection_adapters/mysql_adapter.rb#L370 to see that the MySQL connection adapter seems to convert the entire result set to an array of hashes before returning from the select method. This is never going to work for large result sets. I've looked at the MySQL/Ruby bindings and it doesn't seem to do this buffering, I'm not even sure why ActiveRecord chooses to do it at the connection adapter level. Could one of the Core Developer who knows about this chime in? Thanks --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Core" 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-core -~----------~----~----~----~------~----~------~--~---
