…al Ruby modules and includes will work fine here.
Use connection pool instead of actual connection on load (helps with Rails 3.1 on Heroku)
…onnect to the database until necessary
Relax pg version dependency a bit.
…nd Rails 3.1 specifies pg 0.11 so there is no way for bundler to install pg for a new download.
Fix import of very large datasets containing multibyte chars on Ruby 1.9
Ruby 1.9.2 / RubyGems 1.8.5 compatibility fix (pass String instead of Pathname to require)
…t works with 3.1. [fixes #24]
…y/site_ruby/1.9.1/rubygems.rb) expects the path as a String, not a Pathname. Convert Pathnames to Strings prior to calling 'require'
Use String's bytesize instead of size, because we're talking about byte length, not string length. This resolves a problem on Ruby 1.9 with multi-byte characters.
…the Date.parse capabilities to no longer support MM/DD/YYYY functionality so we only test against YYYY/MM/DD. [fixes zdennis#19]
…Use form of instantiation that allows protected attributes to be set.
…onize on fields beside the primary key. zdennis#16
…from ar-extensions. Currently only works with MySQL since that is the only database that supports on duplicate key update functionality. https://github.com/zdennis/activerecord-import/issues#issue/6
…nsions code base. https://github.com/zdennis/activerecord-import/issues#issue/6
…it impossible to see anything useful.
…r_columns_and_attributes and cleaned up how it dealt with columns. * added back in the support for type-casting based on the database column * removed unused method in ActiveRecord::Import::AbstractAdapter https://github.com/zdennis/activerecord-import/issues#issue/5