| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This alternative case expressions read better for my taste, and look more uniform
in a file where other similar case expressions are used (without dynamic clauses).
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix spelling in API documentation
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
[ci skip]
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | | |
Add --skip-coffee generating option
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Usage
`rails new awesome-project --skip-coffee`
|
|\ \ \ \ \ \ \
| |_|_|_|/ / /
|/| | | | | | |
Add `:nodoc` to `table_structure`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Follow up to #27008.
`table_structure` is an internal method so it is better to hide it in
the doc. And alias `table_structure` to `column_definitions` to remove
the duplicated `columns` method in the sqlite3 adapter.
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
The current implementation of AC::Parameters#permit builds permitted hashes and
then calls permit! on them.
This filtering is recursive, so we call permit! on terminal branches, but then
ascendants call permit! on themselves when the recursion goes up the stack,
which recurses all the way down again because permit! is recursive itself.
Repeat this for every parent node and you get some scary O-something going on
that I don't even want to compute.
Instead, since the whole point of the permit recursion is to build permitted
hashes along the way and at that point you know you've just come up with a
valid filtered version, you can already switch the toggle on the spot.
I have seen 2x speedups in casual benchmarks with small structures. As the
previous description shows, the difference in performance is going to be a
function of the nesting.
Note that that the involved methods are private and used only by permit.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
alexanderkustov/alexanderkustov/update-docs-ActionView
better docs for ActionView::ViewPaths#prepend_view_path [ci skip]
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
✂️ extra line
|
| | | | | | | |
|
| |_|/ / / /
|/| | | | | |
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Refactor column initialization into `new_column_from_field`
|
|/ / / / /
| | | | |
| | | | |
| | | | | |
that accepts results of SHOW FIELDS
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Configure query caching (per thread) on the connection pool
|
| | | | | | |
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
connected? doesn't mean what we need here.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Update guides/source/active_record_querying.md
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Add info about updating locking column value
Follow #26050 and #26871
[ci skip]
|
|\ \ \ \ \ \
| |_|_|_|_|/
|/| | | | | |
add `ActionController::Parameters#merge!`
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This method has the same behavior as `Hash#merge!`, returns current
`ActionController::Parameters`.
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
versions of mysql2
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Add ActiveRecord::Base.connection_pool.stat
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Need to explain the key is only there in certain cases.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
[ci skip] Add `render_collection.action_view` entry to AS instrumenta…
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| |/ / / / / /
|/| | | | | | |
Upgrade JRuby to satisfy gemfile
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix 'Getting Started with Rails' [ci skip]
|
| | |/ / / /
| |/| | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
`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
|
|\ \ \ \ \ \
| |/ / / / /
|/| | | | | |
Add missing spaces [ci skip]
|
|/ / / / / |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Clear query cache during checkin, instead of an execution callback
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
It doesn't make sense for the query cache to persist while a connection
moves through the pool and is assigned to a new thread.
[Samuel Cochran & Matthew Draper]
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
kamipo/avoid_unscope_order_when_limit_value_present
Avoid `unscope(:order)` when `limit_value` is presented for `count`
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
If `limit_value` is presented, records fetching order is very important
for performance. Should not unscope the order in the case.
|
|/ / / / / / |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
remove unused require
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
YAML and ERB were removed at 971d510
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use local variable instead of instance variable [ci skip]
|
|/ / / / / / /
| | | | | | |
| | | | | | | |
Update render yield docs to use `search` local variable instead of `@q` instance variable
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
this test case fails with ruby 2.4, so we want to see what's actually happening
|
| | | | | | | |
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Use different name for main and thread connection variable.
|
| |/ / / / / /
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
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.
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Update sqlite3
|