Update to activerecord 5#533
Conversation
|
@dperson Thanks for jumping into this! One thing that concerns me about the upgrade is config.active_record.belongs_to_required_by_default = false |
|
@mockdeep it has been running well for me, but I'll be glad to change the configuration to maintain the historical behavior. |
49d43d2 to
f77b0f7
Compare
|
@dperson actually, it looks like the configuration defaults to Sorry for the back and forth! |
f77b0f7 to
b60dc28
Compare
|
@mockdeep no problem. I deleted the commit that added the file, and pushed it back to the branch. I'm just glad that there are fixes / updates coming once again. Thank you! |
Me too. Thanks! |
I'm a little surprised this was possible, but #533 introduced a version of ActiveRecord that did not match the constraints of `delayed_job_active_record`. I thought bundler was more strict, but it somehow allowed this one to slip through. This fixes the issue.
I'm a little surprised this was possible, but #533 introduced a version of ActiveRecord that did not match the constraints of `delayed_job_active_record`. I thought bundler was more strict, but it somehow allowed this one to slip through. This fixes the issue.
Followed the instructions at https://www.fastruby.io/blog/rails/upgrades/upgrade-rails-from-4-2-to-5-0.html to migrate to the newer version. Then fixed the
pec/support/active_record.rbcalls to work with the new API.