default_scope with named_scope or scoped merge broken on 2.3

I'm noticing this broken behavior too. Haven't had a chance to look into the reasons why yet.

It's expected behavior, believe it or not, look at the tests. Default_scope does not behave the same as named_scope. This should be fixed in my patch over here: http://rails.lighthouseapp.com/p...

@Manfred, Pratik: any chance we can rollback #2193? Seems it causes more trouble then fixes things, count with named_scope(:select => ...) seems to be broken as well.

Well, the change was a fix for a number of regressions I saw in building instances through an has_many :through association I think. So reverting this would break that.

Manfred's commit has actually nothing to do with this bug -- see #1960

whoops.. the wrong number of ticket.. see #2346

This ticket is totally wrong, #2346 is the correct one. Will wait for cleanup :)