- 09 4月, 2015 1 次提交
-
-
由 Arthur Neves 提交于
[fixes #18606] Make belongs_to use touch over touch_later when running the callbacks. Add more tests and small method rename Thanks Jeremy for the feedback.
-
- 22 2月, 2015 1 次提交
-
-
由 Josef Šimánek 提交于
Deprecate `required` option in favor of `optional` for belongs_to.
-
- 27 1月, 2015 1 次提交
-
-
由 Sean Griffin 提交于
-
- 14 11月, 2014 1 次提交
-
-
由 Arun Agrawal 提交于
`Computer` class needs to be require See #17217 for more details
-
- 08 11月, 2014 1 次提交
-
-
由 alfa-jpn 提交于
fixes #17495
-
- 29 9月, 2014 1 次提交
-
-
由 Ben Woosley 提交于
Isolate access to @associations_cache and @aggregations cache to the Associations and Aggregations modules, respectively. This includes replacing the `association_cache` accessor with a more limited `association_cached?` accessor and making `clear_association_cache` and `clear_aggregation_cache` private.
-
- 09 7月, 2014 1 次提交
-
-
由 Zuhao Wan 提交于
-
- 06 7月, 2014 1 次提交
-
-
由 Godfrey Chan 提交于
This reverts commit e84799d9, e31104c1 and e6ca8e2c
-
- 28 6月, 2014 3 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
-
- 26 6月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
Reliant on https://github.com/rails/rails/pull/15747 but pulled to a separate PR to reduce noise. `has_many :through` associations have the undocumented behavior of automatically detecting counter caches. However, the way in which it does so is inconsistent with counter caches everywhere else, and doesn't actually work consistently. As with normal `has_many` associations, the user should specify the counter cache on the `belongs_to`, if they'd like it updated.
-
- 21 5月, 2014 2 次提交
-
-
由 Lauro Caetano 提交于
The foreign_key could be `String` and just doing `owners_map[owner_key]` could return `nil`. To prevent this bug, we should `to_s` both keys if their types are different. Fixes #14734.
-
由 Brock Trappitt 提交于
-
- 14 4月, 2014 2 次提交
-
-
由 Lauro Caetano 提交于
Follow up to af549a1a
-
由 Jean Boussier 提交于
-
- 05 4月, 2014 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 26 3月, 2014 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 18 3月, 2014 1 次提交
-
-
由 Arthur Neves 提交于
Backport test from #14410
-
- 15 3月, 2014 1 次提交
-
-
由 Washington Luiz 提交于
Prior to Rails 4.0.4 when touching a object which doesn't have timestamp attributes (updated_at / updated_on) rails would still touch all associations. After 73ba2c14 it updates associations but rollsback because `touch` would return nil since there's no timestamp attribute
-
- 20 2月, 2014 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
This is to ensure that they are not accidentally called by the app code. They are renamed to _create_record and _update_record respectively. Closes #11645
-
- 31 1月, 2014 1 次提交
-
-
由 Lauro Caetano 提交于
Dangerous association names conflicts include instance or class methods already defined by `ActiveRecord::Base`.
-
- 22 1月, 2014 1 次提交
-
-
由 Rafael Mendonça França 提交于
Since Rails 4.0, we add an ORDER BY in the `first` method to ensure consistent results among different database engines. But for singular associations this behavior is not needed since we will have one record to return. As this ORDER BY option can lead some performance issues we are removing it for singular associations accessors. Fixes #12623.
-
- 23 12月, 2013 1 次提交
-
-
由 Paul Nikitochkin 提交于
Fixes: #13445
-
- 18 12月, 2013 1 次提交
-
-
由 Jeremy Kemper 提交于
-
- 29 11月, 2013 1 次提交
-
-
由 Kuldeep Aggarwal 提交于
removed unnecessary test case and improved test case for belongs_to having invalid options
-
- 26 10月, 2013 1 次提交
-
-
由 Ivan Antropov 提交于
-
- 29 7月, 2013 1 次提交
-
-
由 Akira Matsuda 提交于
-
- 05 7月, 2013 2 次提交
-
-
由 Paul Nikitochkin 提交于
if belongs to model with touch option on touch Closes #11288
-
由 Paul Nikitochkin 提交于
simplified logic to calculate number of queries by using assert_queries
-
- 03 6月, 2013 1 次提交
-
-
由 Vipul A M 提交于
-
- 07 5月, 2013 1 次提交
-
-
由 Ben Tucker 提交于
counter cache At present, calling destroy multiple times on the same record results in the belongs_to counter cache being decremented multiple times. With this change the record is checked for whether it is already destroyed prior to decrementing the counter cache.
-
- 08 3月, 2013 1 次提交
-
-
由 Anupam Choudhury 提交于
-
- 07 3月, 2013 1 次提交
-
-
由 Anupam Choudhury 提交于
-
- 04 1月, 2013 2 次提交
-
-
由 Jason Stirk 提交于
This commit fixes a bug introduced in 96a13fc7 which breaks behaviour of integer fields. In 3.2.8, setting the value of an integer field to a non-integer (eg. Array, Hash, etc.) would default to 1 (true) : # 3.2.8 p = Post.new p.category_id = [ 1, 2 ] p.category_id # => 1 p.category_id = { 3 => 4 } p.category_id # => 1 In 3.2.9 and above, this will raise a NoMethodError : # 3.2.9 p = Post.new p.category_id = [ 1, 2 ] NoMethodError: undefined method `to_i' for [1, 2]:Array Whilst at first blush this appear to be sensible, it combines in bad ways with scoping. For example, it is common to use scopes to control access to data : @collection = Posts.where(:category_id => [ 1, 2 ]) @new_post = @collection.new In 3.2.8, this would work as expected, creating a new Post object (albeit with @new_post.category_id = 1). However, in 3.2.9 this will cause the NoMethodError to be raised as above. It is difficult to avoid triggering this error without descoping before calling .new, breaking any apps running on 3.2.8 that rely on this behaviour. This patch deviates from 3.2.8 in that it does not retain the somewhat spurious behaviour of setting the attribute to 1. Instead, it explicitly sets these invalid values to nil : p = Post.new p.category_id = [ 1, 2 ] p.category_id # => nil This also fixes the situation where a scope using an array will "pollute" any newly instantiated records. @new_post = @collection.new @new_post.category_id # => nil Finally, 3.2.8 exhibited a behaviour where setting an object to an integer field caused it to be coerced to "1". This has not been retained, as it is spurious and surprising in the same way that setting Arrays and Heshes was : c = Category.find(6) p = Post.new # 3.2.8 p.category_id = c p.category_id # => 1 # This patch p.category_id = c p.category_id # => nil This commit includes explicit test cases that expose the original issue with calling new on a scope that uses an Array. As this is a common situation, an explicit test case is the best way to prevent regressions in the future. It also updates and separates existing tests to be explicit about the situation that is being tested (eg. AR objects vs. other objects vs. non-integers)
-
-
- 02 1月, 2013 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 29 11月, 2012 2 次提交
-
-
由 Carlos Antonio da Silva 提交于
-
由 Jason Rush 提交于
Allows you to do BaseClass.new(:type => "SubClass") as well as parent.children.build(:type => "SubClass") or parent.build_child to initialize an STI subclass. Ensures that the class name is a valid class and that it is in the ancestors of the super class that the association is expecting.
-
- 11 8月, 2012 1 次提交
-
-
由 Jon Leighton 提交于
Method compilation provides better performance and I think the code comes out cleaner as well. A knock on effect is that methods that get redefined produce warnings. I think this is a good thing. I had to deal with a bunch of warnings coming from our tests, though.
-