- 18 11月, 2012 3 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
-
- 17 11月, 2012 6 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
-
由 Alexey Muranov 提交于
The `ActiveRecord::Fixtures::find_table_name` method was removed from "master" almost a year ago, but it was never deprecated. Here it comes back, more dead than alive.
-
由 Carlos Antonio da Silva 提交于
-
由 George Brocklehurst 提交于
See issue #7950.
-
- 16 11月, 2012 4 次提交
-
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
由 Aaron Patterson 提交于
-
- 14 11月, 2012 1 次提交
-
-
由 Carlos Antonio da Silva 提交于
Nothing should be raised anyway
😄 Thanks @spastorino❤ https://github.com/rails/rails/pull/8202/files#r2112067
-
- 13 11月, 2012 3 次提交
-
-
由 Nikita Afanasenko 提交于
-
由 Nikita Afanasenko 提交于
-
由 Aaron Patterson 提交于
-
- 12 11月, 2012 4 次提交
- 11 11月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
Two threads may be in method_missing at the same time. If so, they might both try to define the same delegator method. Such a situation probably wouldn't result in a particularly spectacular bug as one method would probably just be overridden by an identical method, but it could cause warnings to pop up. (It could be worse if method definition is non-atomic in a particular implementation.) (We will also need this mutex shortly anyway, see #8127.)
-
- 10 11月, 2012 3 次提交
-
-
由 AvnerCohen 提交于
-
由 Bogdan Gusiev 提交于
-
由 Nikita Afanasenko 提交于
We should not need any `serialized_attributes` checks outside `ActiveRecord::AttributeMethods::Serialization` module.
-
- 09 11月, 2012 11 次提交
-
-
由 Andrew White 提交于
Most apps upgrading from 3.x will have options for mass assigment in their application.rb and environments/*.rb config files. Rather than just raising a NoMethodError when copying the config, this commit adds a warning message until either the protected_attributes gem is installed or the relevant config options are removed.
-
由 Carlos Antonio da Silva 提交于
These were removed with ActiveRecord::Model in https://github.com/rails/rails/commit/9e4c41c903e8e58721f2c41776a8c60ddba7a0a9#L15L156
-
由 Jon Leighton 提交于
-
由 Jon Leighton 提交于
Rather than just changing it and hoping for the best. Requested by @jeremy: https://github.com/rails/rails/commit/ba1544d71628abff2777c9c514142d7e9a159111#commitcomment-2106059
-
由 Jon Leighton 提交于
So that the scope may be a NullRelation and return a result without executing a query. Fixes #7928
-
由 Jon Leighton 提交于
Fixes #8102. I couldn't find a nicer way to deal with this than delegate the call to #scope, which will be a NullRelation when we want it to be.
-
由 Jon Leighton 提交于
This allows us to avoid hacks like the "return 0 if owner.new_record?" in #count (which this commit removes). Also, the relevant foreign key may actually be present even on a new owner record, in which case we *don't* want a null relation. This logic is encapsulated in the #null_scope? method. We also need to make sure that the CollectionProxy is not 'infected' with the NullRelation module, or else the methods from there will override the definitions in CollectionProxy, leading to incorrect results. Hence the nullify: false option to CollectionAssociation#scope. (This feels a bit nasty but I can't think of a better way.)
-
由 Jon Leighton 提交于
For example, the following should not run any query on the database: Post.new.comments.where(body: 'omg').to_a # => [] Fixes #5215.
-
由 Vinny Diehl 提交于
Organized the gemspec files a bit. * Made quotes more consistent (single quotes dominated, so I used that). * Moved license line down a line, separating it logically, and removed the extra whitespace before its = operator. * Minor whitespace fixes.
-
由 AvnerCohen 提交于
-
-
- 08 11月, 2012 3 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
-
由 Carlos Antonio da Silva 提交于
This is already handled by #find, it's a duplicate check, since find_with_ids is not called from anywhere else.
-
- 07 11月, 2012 1 次提交
-
-
由 Aaron Patterson 提交于
-