I'm still not convinced that a workaround like this is the right way
to solve these 'bulk load' / ETL scenarios.   Why not use your
database's import tools or some really lightweight SQL wrappers?


While the  'insert' method is more universal, I agree that it's often smarter to use the vendor tools. For example,
MySQL's LOAD command processes data imports many orders of magnitude faster than traditional inserts.

Joshua Sierles


_______________________________________________
Rails-core mailing list
Rails-core@lists.rubyonrails.org
http://lists.rubyonrails.org/mailman/listinfo/rails-core

Reply via email to