From 4314d2bbb20013eefef1e52b2f57316f42c3b734 Mon Sep 17 00:00:00 2001 From: Neeraj Singh Date: Fri, 8 Mar 2013 08:47:38 -0500 Subject: fixing typo in the merging scopes section --- guides/source/active_record_querying.md | 7 +++---- 1 file changed, 3 insertions(+), 4 deletions(-) (limited to 'guides') diff --git a/guides/source/active_record_querying.md b/guides/source/active_record_querying.md index da1b4fcbf9..f8823fd43a 100644 --- a/guides/source/active_record_querying.md +++ b/guides/source/active_record_querying.md @@ -1203,7 +1203,7 @@ Just like `where` clauses scopes are merged using `AND` conditions. ```ruby class User < ActiveRecord::Base scope :active, -> { where state: 'active' } - scope :inactive, -> { where state: 'active' } + scope :inactive, -> { where state: 'inactive' } end ```ruby @@ -1216,8 +1216,7 @@ will have all conditions joined with `AND` . ```ruby User.active.where(state: 'finished') -# => SELECT "users".* FROM "users" WHERE "users"."state" = 'active' AND -"users"."state" = 'finished' +# => SELECT "users".* FROM "users" WHERE "users"."state" = 'active' AND "users"."state" = 'finished' ``` If we do want the `last where clause` to win then `Relation#merge` can @@ -1235,7 +1234,7 @@ One important caveat is that `default_scope` will be overridden by class User < ActiveRecord::Base default_scope { where state: 'pending' } scope :active, -> { where state: 'active' } - scope :inactive, -> { where state: 'active' } + scope :inactive, -> { where state: 'inactive' } end User.all -- cgit v1.2.3