1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
rails--rails/activerecord/test
Sean Griffin 5e0b555b45 current_scope shouldn't pollute sibling STI classes
It looks like the only reason `current_scope` was thread local on
`base_class` instead of `self` is to ensure that when we call a named
scope created with a proc on the parent class, it correctly uses the
default scope of the subclass. The reason this wasn't happening was
because the proc captured `self` as the parent class, and we're not
actually defining a real method. Using `instance_exec` fixes the
problem.

Fixes #18806
2015-02-11 13:46:30 -07:00
..
active_record/connection_adapters rm Column#cast_type 2015-02-03 15:02:18 -07:00
assets
cases current_scope shouldn't pollute sibling STI classes 2015-02-11 13:46:30 -07:00
fixtures Fixes #18492 2015-01-14 21:36:58 +05:30
migrations
models Merge pull request #18512 from vipulnsward/18492-fixtures-with-sti 2015-01-31 18:03:45 -08:00
schema Removed magic comments # encoding: utf-8 , since its default from ruby 2.0 onwards. 2015-02-03 20:51:40 +05:30
support Reset ActiveRecord::SchemaDumper.ignore_tables value after changed in tests 2014-09-03 11:30:36 +09:00
.gitignore
config.example.yml remove the last traces of OpenBase from our codebase. [ci skip] 2014-11-07 10:12:01 +01:00
config.rb