Adam Wróbel

I've started a discussion on core with suggestion to change scope syntax. I think the syntax change is certainly a better way of resolving this issue than a hac...

I know you specify multiple columns for order, but when I referred to multi and single values I meant values that get merged and values that get overwritten. My...

An alternative would be to overwrite on merge, but append on order(). That would be similar to where(:column => value). Multiple where() calls create OR but dur...

I suggest moving order from MULTI_VALUE_METHODS to SINGLE_VALUE_METHODS and overwriting the order array with each merged scope or new call to order(). There's n...

This problem can also surface when using named scopes.

class Widget < ActiveRecord::Base
  default_scope lambda { where(['created_at >= ?', 10.minute.ago]) }
 ...

Thanks for finding this issue.

You're right that those latter calls calculate previously defined lambdas and append their results to the final query. A test wit...

It's currently waiting to be reviewed by Aaron and hopefully merged into edge for a release in 3.1. And yes - that code allows one to call default_scope multipl...

There is an open ticket to enable proc handling for default scope. It contains a patch that enables lambda default scopes instead of raising an exception on rec...

This is unrelated to the lambda support. Uniqueness validator just ignores the default_scope regardless of whether it's lambda or arel finder.

activerecord/lib...

I was reminded to use respond_to?(:call) instead of kind_of?(Proc) on github. Here's a corrected patch.