SELECT “patterns”.* FROM “patterns” INNER JOIN “patterns_patterns” ON “patterns”.“id” = “patterns_patterns”.“child_id” WHERE “patterns_patterns”.“parent_id” = ? ORDER BY sort, title [[“parent_id”, 1]]
I tend to avoid default_scope for exactly this reason, the results are
not always obvious. I prefer to use named scopes or specify the order
explicitly. Then you have better control of what is going on. Many
believe default scopes are evil. I believe you can override it using
reorder.
Hi Colin, thank you for your answer.
I just realized that my problem is bigger than that. I removed the default_scope and my query now is “orderbyless”.
SELECT “patterns”.* FROM “patterns” INNER JOIN “patterns_patterns” ON “patterns”.“id” = “patterns_patterns”.“child_id” WHERE “patterns_patterns”.“parent_id” = ? [[“parent_id”, 7]]
Hi Colin, thank you for your answer.
I just realized that my problem is bigger than that. I removed the default_scope and my query now is “orderbyless”.
SELECT “patterns”.* FROM “patterns” INNER JOIN “patterns_patterns” ON “patterns”.“id” = “patterns_patterns”.“child_id” WHERE “patterns_patterns”.“parent_id” = ? [[“parent_id”, 7]]
Why the order is been ignored?
class Pattern < ActiveRecord::Base
has_and_belongs_to_many :children,
:class_name => 'Pattern',
:join_table => 'patterns_patterns',
:association_foreign_key => 'child_id',
:foreign_key => 'parent_id',
:order => 'patterns_patterns.updated_at'
end
The order option was removed a while back - things that change the query should be done in a scope lambda instead: