aboutsummaryrefslogtreecommitdiffstats
path: root/activerecord/lib/active_record/scoping/named.rb
Commit message (Collapse)AuthorAgeFilesLines
...
* Deprecate eager-evaluated scopes.Jon Leighton2012-03-211-2/+16
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | Don't use this: scope :red, where(color: 'red') default_scope where(color: 'red') Use this: scope :red, -> { where(color: 'red') } default_scope { where(color: 'red') } The former has numerous issues. It is a common newbie gotcha to do the following: scope :recent, where(published_at: Time.now - 2.weeks) Or a more subtle variant: scope :recent, -> { where(published_at: Time.now - 2.weeks) } scope :recent_red, recent.where(color: 'red') Eager scopes are also very complex to implement within Active Record, and there are still bugs. For example, the following does not do what you expect: scope :remove_conditions, except(:where) where(...).remove_conditions # => still has conditions
* Avoid obscure &Proc.new thingJon Leighton2012-03-211-2/+2
|
* Remove valid_scope_name? check - use rubyJon Leighton2012-03-211-11/+1
| | | | | | | scope is syntactic sugar for defining a class method. Ruby allows redefining methods but emits a warning when run with -w. So let's not implement our own logic for this. Users should run with -w if they want to be warned about redefined methods.
* no need for castJon Leighton2012-03-211-1/+0
|
* no need for lvarJon Leighton2012-03-211-3/+1
|
* app code in general wants Time.current, not Time.nowXavier Noria2011-12-281-3/+3
|
* call scope within unscoped to prevent duplication of where valuesSergey Nartimov2011-12-171-1/+1
|
* Move DefaultScope and NamedScope under ScopingJon Leighton2011-12-151-0/+202