- 08 11月, 2016 2 次提交
-
-
由 Rafael França 提交于
Upgrade JRuby to satisfy gemfile
-
由 Kir Shatrov 提交于
-
- 07 11月, 2016 4 次提交
-
-
由 Kasper Timm Hansen 提交于
Fix 'Getting Started with Rails' [ci skip]
-
由 Eileen M. Uchitelle 提交于
Add missing spaces [ci skip]
-
由 bogdanvlviv 提交于
-
由 bogdanvlviv 提交于
`bin/rails generate controller Comments` creates files app/assets/javascripts/comments.coffee app/assets/stylesheets/comments.scss not app/assets/javascripts/comment.coffee app/assets/stylesheets/comment.scss
-
- 06 11月, 2016 5 次提交
-
-
由 Matthew Draper 提交于
Clear query cache during checkin, instead of an execution callback
-
由 Rafael França 提交于
Avoid `unscope(:order)` when `limit_value` is presented for `count`
-
由 Akira Matsuda 提交于
-
由 Ryuta Kamizono 提交于
If `limit_value` is presented, records fetching order is very important for performance. Should not unscope the order in the case.
-
由 Rafael França 提交于
remove unused require
-
- 05 11月, 2016 10 次提交
-
-
由 Jon Moss 提交于
Use local variable instead of instance variable [ci skip]
-
由 Daniel Amireh 提交于
Update render yield docs to use `search` local variable instead of `@q` instance variable
-
由 Akira Matsuda 提交于
2.3: sprintf('%0.1f', 5.55) #=> "5.5" 2.4: sprintf('%0.1f', 5.55) #=> "5.6" see: https://github.com/ruby/ruby/commit/6ed8c79ddb11ccfb580bb0a22b22cc1362250255 and https://github.com/ruby/ruby/commit/295f60b94d5ff6551fab7c55e18d1ffa6a4cf7e3
-
由 Akira Matsuda 提交于
this test case fails with ruby 2.4, so we want to see what's actually happening
-
由 Akira Matsuda 提交于
-
由 yuuji.yaginuma 提交于
YAML and ERB were removed at 971d5107
-
由 Aaron Patterson 提交于
Use different name for main and thread connection variable.
-
由 Charles Oliver Nutter 提交于
Under JRuby, the updates of the one shared variable interleaved, causing threads to pick up each others' connections. I'm amazed this worked on MRI.
-
由 Guillermo Iguaran 提交于
Update sqlite3
-
由 Gianfranco Montoya 提交于
-
- 04 11月, 2016 4 次提交
-
-
由 Arthur Nogueira Neves 提交于
change `MemCacheStore#increment` and `MemCacheStore#decrement` to public API [ci skip]
-
由 Sean Griffin 提交于
If the call to `.define_attribute_methods` actually ends up loading the schema (*very* hard to do, as it requires the object being created without `allocate` having been called, but it can be done by manually calling `initialize` from inside `marshal_load` if you're crazy), the value of `_default_attributes` will change from that call.
-
由 Arthur Nogueira Neves 提交于
Move `test_quoting_classes` into `test/cases/quoting_test.rb`
-
由 Arthur Nogueira Neves 提交于
fix datatime error
-
- 03 11月, 2016 1 次提交
-
-
由 Daniel E. Garcia Shulman 提交于
* Fixes TypeError when cache counter value equals nil * Test case for counter cache on unloaded has_many association
-
- 02 11月, 2016 14 次提交
-
-
由 Akira Matsuda 提交于
-
由 Guillermo Iguaran 提交于
remove warning from railtie
-
由 yuuji.yaginuma 提交于
This removes the following warnings. ```ruby rails/railties/lib/rails/railtie.rb:186: warning: instance variable @rake_tasks not initialized rails/railties/lib/rails/railtie.rb:186: warning: instance variable @rake_tasks not initialized rails/railties/lib/rails/railtie.rb:186: warning: instance variable @load_console not initialized rails/railties/lib/rails/railtie.rb:186: warning: instance variable @rake_tasks not initialized ```
-
由 Sen-Zhang 提交于
-
由 Arthur Neves 提交于
-
由 Sean Griffin 提交于
Don't put db:migrate and db:setup in binfiles if activerecord is excluded
-
由 Bouke van der Bijl 提交于
-
由 Sean Griffin 提交于
Remove unnecessary `target.uniq.size` in `CollectionAssociation#size`
-
由 Sean Griffin 提交于
Remove unused internal `:dependent` option in `CollectionAssociation#delete`
-
由 Sean Griffin 提交于
With the changes in #25337, double save bugs are pretty much impossible, so we can just lift this restriction with pretty much no change. There were a handful of cases where we were relying on specific quirks in tests that had to be updated. The change to has_one associations was due to a particularly interesting test where an autosaved has_one association was replaced with a new child, where the child failed to save but the test wanted to check that the parent id persisted to `nil`. I think this is almost certainly the wrong behavior, and I may change that behavior later. But ultimately the root cause was because we never remove the parent in memory when nullifying the child. This makes #23197 no longer needed, but it is what we'll do to fix some issues on 5.0 Close #23197
-
由 Sean Griffin 提交于
Deprecate the behavior of AR::Dirty inside of after_(create|update|save) callbacks
-
由 Sean Griffin 提交于
We pretty frequently get bug reports that "dirty is broken inside of after callbacks". Intuitively they are correct. You'd expect `Model.after_save { puts changed? }; model.save` to do the same thing as `model.save; puts model.changed?`, but it does not. However, changing this goes much farther than just making the behavior more intuitive. There are a _ton_ of places inside of AR that can be drastically simplified with this change. Specifically, autosave associations, timestamps, touch, counter cache, and just about anything else in AR that works with callbacks have code to try to avoid "double save" bugs which we will be able to flat out remove with this change. We introduce two new sets of methods, both with names that are meant to be more explicit than dirty. The first set maintains the old behavior, and their names are meant to center that they are about changes that occurred during the save that just happened. They are equivalent to `previous_changes` when called outside of after callbacks, or once the deprecation cycle moves. The second set is the new behavior. Their names imply that they are talking about changes from the database representation. The fact that this is what we really care about became clear when looking at `BelongsTo.touch_record` when tests were failing. I'm unsure that this set of methods should be in the public API. Outside of after callbacks, they are equivalent to the existing methods on dirty. Dirty itself is not deprecated, nor are the methods inside of it. They will only emit the warning when called inside of after callbacks. The scope of this breakage is pretty large, but the migration path is simple. Given how much this can improve our codebase, and considering that it makes our API more intuitive, I think it's worth doing.
-
由 Arthur Neves 提交于
-
由 Rafael Fidelis 提交于
fixing @generators var initialization pre initializing variables values Changing from var init to symbol to instance var get/set
-