…Use form of instantiation that allows protected attributes to be set.
…onize on fields beside the primary key. #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
…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
…ach_with_index and Hash. Hash[column_names.zip(attributes)] would be much clearer, but would leave nil values for missing attributes which doesn't match the existing behavior.
…e of options[:ignore]
…ausing trouble, but to be a bit paranoid (reverts 63d6fae)
…the same indexes as the array_of_attributes, and so was sometime mismatched. Also return to the column_names[j] == primary_key style of testing, as the column itself is not always present
…aster, more rigid structure
…he primary_key nulls we might put in next
…tory - remove.
…_for_column_names_and_attributes. This means both with properly support sequences. Rather than pass a ton of variables (sequence_name, columns, column_names, &c.), move the method out of the connection. Also, use Column#primary to check primary key status.
…ns_or_callbacks. This is DRY-er, more consistent between the supports_import? cases and enables us to inline #quote_column_names
… particularly well-factored, and for parity with "not supports_import?"
…y chaining #map (is simpler, should be more performant, AFAIK)