- 28 7月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 24 7月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
-
- 20 7月, 2016 1 次提交
-
-
由 Ryuta Kamizono 提交于
Fixes #25732.
-
- 15 7月, 2016 1 次提交
-
-
由 Yamaguchi.Tomoki 提交于
-
- 19 5月, 2016 1 次提交
-
-
由 Jeremy Daer 提交于
Ruby 2.4 unifies Fixnum and Bignum into Integer: https://bugs.ruby-lang.org/issues/12005 * Forward compat with new unified Integer class in Ruby 2.4+. * Backward compat with separate Fixnum/Bignum in Ruby 2.2 & 2.3. * Drops needless Fixnum distinction in docs, preferring Integer.
-
- 20 3月, 2016 1 次提交
-
-
由 Erik Michaels-Ober 提交于
-
- 21 2月, 2016 1 次提交
-
-
由 Matthew Draper 提交于
Clarifying this separation and enforcing relation immutability is the culmination of the previous efforts to remove the mutator method delegations.
-
- 11 2月, 2016 1 次提交
-
-
由 Brian Christian 提交于
-
- 10 2月, 2016 1 次提交
-
-
由 Brian Christian 提交于
-
- 14 10月, 2015 2 次提交
-
-
由 Yves Senn 提交于
The focus of this change is to make the API more accessible. References to method and classes should be linked to make it easy to navigate around. This patch makes exzessiv use of `rdoc-ref:` to provide more readable docs. This makes it possible to document `ActiveRecord::Base#save` even though the method is within a separate module `ActiveRecord::Persistence`. The goal here is to bring the API closer to the actual code that you would write. This commit only deals with Active Record. The other gems will be updated accordingly but in different commits. The pass through Active Record is not completely finished yet. A follow up commit will change the spots I haven't yet had the time to update. /cc @fxn
-
由 Yves Senn 提交于
-
- 27 9月, 2015 1 次提交
-
-
由 amitkumarsuroliya 提交于
-
- 09 9月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 23 8月, 2015 1 次提交
-
-
由 Ronak Jangir 提交于
-
- 20 7月, 2015 1 次提交
-
-
由 Mehmet Emin İNAÇ 提交于
-
- 18 7月, 2015 1 次提交
-
-
由 Andrii Ponomarov 提交于
-
- 03 6月, 2015 1 次提交
-
-
由 Roque Pinel 提交于
Improve the guide about `has_many` `collection.clear` to indicate the behavior for each dependent strategy according to `collection.delete_all`. Based on #17179, I changed the `collection.delete` docs to also clarify the default strategy for each `hm` and `hm:t` associations. Fixes #20170.
-
- 07 3月, 2015 1 次提交
-
-
由 Prathamesh Sonpatki 提交于
- CollectionProxy#clear method calls delete_all so the SQL is directly run into the database. - So the updated_at column of the object on which its run is not updated. - Closes #17161
-
- 28 2月, 2015 1 次提交
-
-
由 Akira Matsuda 提交于
-
- 21 2月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 02 1月, 2015 1 次提交
-
-
由 Rafael Mendonça França 提交于
-
- 30 12月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
Fixes #18237
-
- 27 12月, 2014 1 次提交
-
-
由 Sean Griffin 提交于
Construction of relations can be a hotspot, we don't want to create one of these in the constructor. This also allows us to do more expensive things in the predicate builder's constructor, since it's created once per AR::Base subclass
-
- 04 10月, 2014 1 次提交
-
-
由 eileencodes 提交于
For detailed testing of behavior see: https://gist.github.com/eileencodes/5b0a2fe011dcff6203fe This shows destroy_all always destroys records and fires callbacks. It will never use nullify or delete_all delete_all's behavior varies greatly based on `hm` vs `hm:t` and deletion strategy.
-
- 27 8月, 2014 4 次提交
-
-
由 Tom Kadwill 提交于
-
由 Tom Kadwill 提交于
-
由 Tom Kadwill 提交于
-
由 Tom Kadwill 提交于
-
- 07 4月, 2014 1 次提交
-
-
由 eileencodes 提交于
This method no longer returns an array of all records that have been removed. Correct documentation to reflect this change. See issue 14546
-
- 03 4月, 2014 1 次提交
-
-
由 Jefferson Lai 提交于
CollectionProxy should be able to reuse the behavior (methods) of its parent class, but with its own state. This change allows CollectionProxy to use the arel object corresponding to its association's scope.
-
- 22 1月, 2014 4 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Kelsey Schlarman 提交于
Need to define #reset on CollectionProxy.
-
由 Jason Meller 提交于
This commit fixes two regressions introduced in cafe31a0 where newly created finder methods #second, #third, #forth, and #fifth caused a NoMethodError error on reload associations and where we were pulling the wrong element out of cached associations. Examples: some_book.authors.reload.second # Before # => NoMethodError: undefined method 'first' for nil:NilClass # After # => #<Author id: 2, name: "Sally Second", ...> some_book.first.authors.first some_book.first.authors.second # Before # => #<Author id: 1, name: "Freddy First", ...> # => #<Author id: 1, name: "Freddy First", ...> # After # => #<Author id: 1, name: "Freddy First", ...> # => #<Author id: 2, name: "Sally Second", ...> Fixes #13783.
-
由 Kuldeep Aggarwal 提交于
-
- 04 1月, 2014 1 次提交
-
-
由 T.J. Schuck 提交于
-
- 11 12月, 2013 2 次提交
-
-
由 Rafael Mendonça França 提交于
-
由 Rafael Mendonça França 提交于
It is needed for activerecord-depecated_finders This reverts commit dcff027a, reversing changes made to 3a209398.
-
- 12 11月, 2013 1 次提交
-
-
由 Prem Sichanugrist 提交于
According to our guideline, we leave 1 space between `#` and `=>`, so we want `# =>` instead of `#=>`. Thanks to @fxn for the suggestion. [ci skip]
-
- 24 10月, 2013 1 次提交
-
-
由 Peter Jaros 提交于
-
- 13 10月, 2013 1 次提交
-
-
由 Vipul A M 提交于
-