duncanbeevers

+1

I think this fits best with people's expectations of how scopes should compose.

Issuing a count calculation on a scope that explicitly specifies a select option does not respect that select, resulting in incorrect counts.

Creating a record whose underlying database store is a date-type column does not cast the value on the newly-created record to a Date.

Reading the record back ...

Argh! I've helped make construct_finder_sql that little bit uglier!

I think giving the method a different name is appropriate, and at a minimum the tests should be carried over.

No offense taken.

I quite like the idea of having the scope itself emit its options, and I've realy come around on using class methods as scopes. Could be us...

Perhaps

:scope_method

The provided patch allows for providing a method name as the scope using a symbol as the method name.

def Topic < ActiveRecord::Base
  named_scope :written_b...

When generating complex options hashes for named scopes, it can be difficult to test that the scopes are generated correctly. By providing insight into the ge...

I've been thinking about similar functionality, and thus far I've found it most flexible to simply specify composite scopes as proper methods.

def self.writte...