kotovalexarian-likes-github/rails--rails
1
0
Fork 0
mirror of https://github.com/rails/rails.git synced 2022-11-09 12:12:34 -05:00
Code Releases Activity
rails--rails/activerecord/test/fixtures/computers.yml

11 lines
142 B
YAML
Raw Normal View History

git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@388 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
2005-01-10 19:53:04 -05:00
workstation:
id: 1
Fixed STI classes not defining an attribute method if there is a conflicting private method defined on its ancestors. The problem is that `method_defined_within?(name, klass, superklass)` only works correclty when `klass` and `superklass` are both `Class`es. If both `klass` and `superklass` are both `Class`es, they share the same inheritance chain, so if a method is defined on `klass` but not `superklass`, this method must be introduced at some point between `klass` and `superklass`. This does not work when `superklass` is a `Module`. A `Module`'s inheritance chain contains just itself. So if a method is defined on `klass` but not on `superklass`, the method could still be defined somewhere upstream, e.g. in `Object`. This fix works by avoiding calling `method_defined_within?` with a module while still fufilling the requirement (checking that the method is defined withing `superclass` but not is not a generated attribute method). 4d8ee288 is likely an attempted partial fix for this problem. This unrolls that fix and properly check the `superclass` as intended. Fixes #11569.
2014-02-13 14:49:19 -05:00
system: 'Linux'
Added compatibility with camelCase column names for dynamic finders #533 [Dee.Zsombor] git-svn-id: http://svn-commit.rubyonrails.org/rails/trunk@1263 5ecf4fe2-1ee6-0310-87b1-e25e094e27de
2005-04-30 11:49:28 -04:00
developer: 1
extendedWarranty: 1
Ensure HABTM relationships produce valid class names (Fixes #17119)
2014-10-08 16:58:11 -04:00
laptop:
system: 'MacOS 1'
developer: 1
extendedWarranty: 1
Copy permalink