Skip to content

Conversation

@jabley
Copy link
Contributor

@jabley jabley commented Jan 29, 2013

Fixes #17

This might not be the correct fix (someone with better knowledge of rails than I can judge), but it does have a failing test and a change which fixes the test, plus the change works in our production environment to extract the data and cleanse it for us.

In rails 3.2.8, mass assignment can mean that the ActiveModel class
doesn't support mass assignment. This change ignores any such
protection and assumes it's your own data and you know what you're
doing with it.
Initial exploration seemed to point to a mass-assignment issue; this
change adds a test which attempts to reproduce the configuration that
rails is using when running the application that fails.
@sunitparekh sunitparekh merged commit e11a584 into sunitparekh:master Jan 29, 2013
@jabley jabley deleted the mass-assignment branch January 30, 2013 10:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

whitelisted fields are not persisted in the destination database

2 participants