- 07 8月, 2016 1 次提交
-
-
由 Xavier Noria 提交于
The current code base is not uniform. After some discussion, we have chosen to go with double quotes by default.
-
- 13 5月, 2016 1 次提交
-
-
由 Sean Griffin 提交于
The error message that we give today makes this error difficult to debug if you receive it. I have no clue why we're printing the object ID of the class (the commit doesn't give context), but I've left it as it was deliberate.
-
- 29 4月, 2016 1 次提交
-
-
由 Tom Kadwill 提交于
-
- 02 3月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 17 12月, 2015 1 次提交
-
-
由 Abdelkader Boudih 提交于
-
- 23 9月, 2015 1 次提交
-
-
由 Sean Griffin 提交于
When I originally reviewed the #20317, I believe these changes were present, but it appears that it was later updated so that they were removed. Since Travis hadn't re-run the build, this slipped through.
-
- 27 8月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 13 8月, 2015 1 次提交
-
-
由 Yves Senn 提交于
As described in the "Follow Coding Conventions" section in our contribution guide (http://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#follow-the-coding-conventions) we favor `assert_not` over `refute`. While we don't usually make stylistic changes on it's own I opted to do it in this case. The reason being that test cases are usually copied as a starting point for new tests. This results in a spread of `refute` in files that have been using it already.
-
- 17 7月, 2015 1 次提交
-
-
由 Prem Sichanugrist 提交于
We deprecate the support for passing an argument to force reload in 6eae366d. That led to several deprecation warning when running Active Record test suite. This commit silence the warnings by properly calling `#reload` on the association proxy or on the association object instead. However, there are several places that `ActiveSupport::Deprecation.silence` are used as those tests actually tests the force reload functionality and will be removed once `master` is targeted next minor release (5.1).
-
- 16 7月, 2015 1 次提交
-
-
由 Prem Sichanugrist 提交于
This is to simplify the association API, as you can call `reload` on the association proxy or the parent object to get the same result. For collection association, you can call `#reload` on association proxy to force a reload: @user.posts.reload # Instead of @user.posts(true) For singular association, you can call `#reload` on the parent object to clear its association cache then call the association method: @user.reload.profile # Instead of @user.profile(true) Passing a truthy argument to force association to reload will be removed in Rails 5.1.
-
- 22 6月, 2015 1 次提交
-
-
由 Diego Carrion 提交于
thrown ActiveRecord::AssociationTypeMismatch when assigning a wrong value for a namespaced association fixes #20541
-
- 17 6月, 2015 1 次提交
-
-
由 Diego Carrion 提交于
raise ActiveModel::MissingAttributeError when trying to access a relationship without the foreign key attribute fixes regression reported on #20253 ActiveRecord::Base#[] was not used cause of 8b954200
-
- 14 6月, 2015 1 次提交
-
-
由 James Dabbs 提交于
Unitialized polymorphic `belongs_to` associations raise an error while attempting to reload, as they attempt to make an uncached reload, but don't have a klass to fetch uncachedly. In this case, `loaded?` should be `false` anyway.
-
- 21 4月, 2015 1 次提交
-
-
由 Andrew White 提交于
In 1f006c an option was added called :class to allow passing anonymous classes to association definitions. Since using :class instead of :class_name is a fairly common typo even amongst experienced developers this can result in hard to debug errors arising in raise_on_type_mismatch? To fix this we're renaming the option from :class to :anonymous_class as that is a more correct description of what the option is for. Since this was an internal, undocumented option there is no need for a deprecation. Fixes #19659
-
- 09 4月, 2015 2 次提交
-
-
由 Tristan Gamilis 提交于
Assert that counter_cache behaviour is not used on belongs_to or has_many associations if the option is not given explicitly.
-
由 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 提交于
-