Skip to content
Browse files

Merge pull request #12030 from garysweaver/master

adding more finder deprecation info in upgrade documentation [ci skip]
  • Loading branch information...
2 parents af3a69a + a394f91 commit 60b9d4fe877c9ff5718b72609142caa2619c7fd1 @senny senny committed
Showing with 6 additions and 0 deletions.
  1. +6 −0 guides/source/upgrading_ruby_on_rails.md
View
6 guides/source/upgrading_ruby_on_rails.md
@@ -184,6 +184,12 @@ this gem such as `whitelist_attributes` or `mass_assignment_sanitizer` options.
* `find_or_initialize_by_...` becomes `find_or_initialize_by(...)`.
* `find_or_create_by_...` becomes `find_or_create_by(...)`.
+* Note that `where(...)` returns a relation, not an array like the old finders. If you require an `Array`, use `where(...).to_a`.
+
+* These equivalent methods may not execute the same SQL as the previous implementation.
+
+* To re-enable the old finders, you can use the [activerecord-deprecated_finders gem](https://github.com/rails/activerecord-deprecated_finders).
+
### Active Resource
Rails 4.0 extracted Active Resource to its own gem. If you still need the feature you can add the [Active Resource gem](https://github.com/rails/activeresource) in your Gemfile.

0 comments on commit 60b9d4f

Please sign in to comment.
Something went wrong with that request. Please try again.