Yup, I agree that we should make scopes work the same as chaining Arel methods, being combined in the same field instead of overriding the condition. And the same should happen for default_scope, it should combine using scopes or where methods, so that to override any condition you should be very specific about it.

Oleg, I’ve never seem this before, but if you think it’s a Rails issue I’d ask you to open an issue giving as much information as possible, with more code examples showing your issue there. Thanks!

Yeah, my example wasn’t too good. But the issue is still there, just it manifests itself a little bit differently. Here are the details: https://github.com/rails/rails/issues/8511

maybe I do not understand the point, when I write two scopes of type
  scope :created_after, -> date { where(“created_at > ? “, date )}
  scope :created_before, -> data { where(“created_at ‘2013-01-17’ ) AND (created_at < '2013-02-03' )

Gio

For ex:

class User
  scope :active, where(…)
class Admin < User

Admin.active.to_sql will have extra condition of type:
select * from users where type in ('Admin', 'User')..