- 18 3月, 2019 12 次提交
-
-
由 Kasper Timm Hansen 提交于
Revert "Pass HTML responses as plain-text in rails-ujs"
-
由 Ryuta Kamizono 提交于
Get rid of `Arel::Nodes::Values`
-
由 Ryuta Kamizono 提交于
-
由 George Claghorn 提交于
Closes #35159.
-
由 Ryuta Kamizono 提交于
Fix invalid suggestion in null origin error message
-
由 Tom Richards 提交于
-
由 Ryuta Kamizono 提交于
That is completely covered by `Arel::Nodes::ValuesList`. Related https://github.com/rails/arel/pull/484.
-
由 razh 提交于
See discussion in #32287
-
由 Ryuta Kamizono 提交于
Here is only place where we use `mb_chars` internally.
-
由 Ryuta Kamizono 提交于
These are introduced after Rails 6.0.0 beta2. [ci skip]
-
由 Ryuta Kamizono 提交于
-
- 17 3月, 2019 10 次提交
-
-
由 Ryuta Kamizono 提交于
* Remove redundant `table_names.empty?` * Early return in `truncate_tables` since it is already deeply nested * Move `truncate_tables` out from between `exec_delete` and `exec_update`
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
-
由 Ryuta Kamizono 提交于
Before: ``` (16.4ms) TRUNCATE TABLE `author_addresses` (20.5ms) TRUNCATE TABLE `authors` (19.4ms) TRUNCATE TABLE `posts` ``` After: ``` Truncate Tables (19.5ms) TRUNCATE TABLE `author_addresses`; TRUNCATE TABLE `authors`; TRUNCATE TABLE `posts` ```
-
由 Yuji Yaginuma 提交于
Add `-e/--environment` option to `rails initializers`
-
由 Ryuta Kamizono 提交于
This is to easier make `truncate_tables` to bulk statements.
-
由 Ryuta Kamizono 提交于
Support Optimizer Hints
-
由 Ryuta Kamizono 提交于
See #33912.
-
- 16 3月, 2019 14 次提交
-
-
由 Ryuta Kamizono 提交于
Raise UnknownAttributeError when unknown column is passed to insert_all and friends
-
由 Josef Šimánek 提交于
-
由 Ryuta Kamizono 提交于
We as Arm Treasure Data are using Optimizer Hints with a monkey patch (https://gist.github.com/kamipo/4c8539f0ce4acf85075cf5a6b0d9712e), especially in order to use `MAX_EXECUTION_TIME` (refer #31129). Example: ```ruby class Job < ApplicationRecord default_scope { optimizer_hints("MAX_EXECUTION_TIME(50000) NO_INDEX_MERGE(jobs)") } end ``` Optimizer Hints is supported not only for MySQL but also for most databases (PostgreSQL on RDS, Oracle, SQL Server, etc), it is really helpful to turn heavy queries for large scale applications.
-
由 yuuji.yaginuma 提交于
This allows specifying the environment as would any other rails commands.
-
由 Ryuta Kamizono 提交于
Update docs for 'parameterize()' [ci skip]
-
由 Xavier Noria 提交于
-
由 Sharang Dashputre 提交于
-
由 Aaron Patterson 提交于
Match evented checker behavior on dir with no exts
-
由 Aaron Patterson 提交于
Make Template::Resolver always cache
-
由 Aaron Patterson 提交于
Rename `ActionView::Base#run`
-
由 Seb Jacobs 提交于
There was a recent change by @tenderlove to Action view which introduced `ActionView::Base#run` [1]. We ran into an issue with our application because one of the core concepts in our domain model is a `Run` which is exposed in most of our views as a helper method, which now conflicts with this new method. Although this is a public method it is not really meant to be part of the public API. In order to discourage public use of this method and to reduce the chances of this method conflicting with helper methods we can prefix this method with an underscore, renaming this method to `_run`. [1] https://github.com/rails/rails/commit/c740ebdaf5
-
由 John Hawthorn 提交于
When FileUpdateChecker is passed a directory and given an empty array of extensions to match on, it will match any extension. Previously, EventedFileUpdateChecker would never match any files when given an empty array. This commit makes it EventedFileUpdateChecker match FileUpdateChecker, and watch all extensions when given an empty array.
-
由 John Hawthorn 提交于
-
由 John Hawthorn 提交于
All actionview caches are already cleared at the start of each request (when Resolver.caching is false) by PerExecutionDigestCacheExpiry, which calls LookupContext::DetailsKey.clear (which clears all caches). Because caches are always cleared per-request in dev, we shouldn't need this extra logic to compare mtimes and conditionally reload templates. This should make templates slightly faster in development (particularly multiple renders of the same template)
-
- 15 3月, 2019 3 次提交
-
-
由 Yuji Yaginuma 提交于
Properly expand the environment's name in all commands
-
由 yuuji.yaginuma 提交于
Since 3777701f, the environment's name is automatically expanded in console and dbconsole commands. In order to match the behavior between the commands, fixes it to have the same behavior of all the commands. This behavior is defined in `EnvironmentArgument`. Since `EnvironmentArgument` also defines the environment option, it is reused. However, since desc was not content that can be used in all comments, fixed desc to be defined for each command.
-
由 Xavier Noria 提交于
-
- 14 3月, 2019 1 次提交
-
-
由 George Claghorn 提交于
-