Permalink
Browse files

Merge pull request #11501 from nishantmodak/patch-3

Upgrade guide. Renaming Indexes on tables. [ci skip]
  • Loading branch information...
2 parents 20281b7 + 3659215 commit 7cb2e82bd66c6df6d644facbf03d616e1aaa78fa @senny senny committed Jul 19, 2013
Showing with 2 additions and 0 deletions.
  1. +2 −0 guides/source/upgrading_ruby_on_rails.md
@@ -151,6 +151,8 @@ Rails 4.0 no longer supports loading plugins from `vendor/plugins`. You must rep
* The `delete` method in collection associations can now receive `Fixnum` or `String` arguments as record ids, besides records, pretty much like the `destroy` method does. Previously it raised `ActiveRecord::AssociationTypeMismatch` for such arguments. From Rails 4.0 on `delete` automatically tries to find the records matching the given ids before deleting them.
+* In Rails 4.0 when a column or a table is renamed the related indexes are also renamed. If you have migrations which rename the indexes, they are no longer needed.
+
* Rails 4.0 has changed how orders get stacked in `ActiveRecord::Relation`. In previous versions of Rails, the new order was applied after the previously defined order. But this is no longer true. Check [Active Record Query guide](active_record_querying.html#ordering) for more information.
* Rails 4.0 has changed `serialized_attributes` and `attr_readonly` to class methods only. You shouldn't use instance methods since it's now deprecated. You should change them to use class methods, e.g. `self.serialized_attributes` to `self.class.serialized_attributes`.

0 comments on commit 7cb2e82

Please sign in to comment.