This was a regression introduced in 5c858220. We bring
sorting back because people rely on it, eg for constructing consistent cache keys.

Signed-off-by: NJosé Valim <jose.valim@gmail.com>

[#5650 state:resolved]
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Fix for #5579 involved the code change for both has_one and has_many relationships. The path included test only for has_one. This patch adds test for has_many relationship.

[#5706 state:resolved]
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

[#5705 state:resolved]
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Following namespace use case was broken with Ruby 1.9:

  class Author < ActiveRecord::Base
    ...
  end

  module Api
    class Book < ActiveResouce::Base
    end
  end

Let's say XML contains <book><author><name>John</name></author>....

  Api::Book.first.author.class.to_s #=>
    Ruby 1.8.7: "Api::Book::Author" (namespaced, correct),
    Ruby 1.9: "Author" (toplevel, broken)
Signed-off-by: NJosé Valim <jose.valim@gmail.com>

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Signed-off-by: NSantiago Pastorino <santiago@wyeworks.com>

Conflicts:
	actionpack/lib/action_controller/metal/url_for.rb