- 19 3月, 2019 11 次提交
-
-
由 Eileen M. Uchitelle 提交于
Fix a ContentNegotiation test description
-
由 Xavier Noria 提交于
-
由 Andrew White 提交于
Fix Time#advance to work with dates before 1001-03-07
-
由 Sharang Dashputre 提交于
-
由 Eileen M. Uchitelle 提交于
Merge pull request #35663 from eileencodes/fix-database-configuration-when-not-actually-a-three-tier Fix database configuration when adding another config level
-
由 Kasper Timm Hansen 提交于
This also prevents insert_all from leaking its attributes checks.
-
由 Kasper Timm Hansen 提交于
`values_list` is quite long and does far too many things. This also eagerly extract the keys in initialize instead of having to worry about calling them multiple times.
-
由 eileencodes 提交于
This is kind of hard to explain but if you have a database config with another level like this: ``` development: primary: database: "my db" variables: statement_timeout: 1000 ``` the database configurations code would chooke on the `variables` level because it didn't know what to do with it. We'd see the following error: ``` lib/active_record/database_configurations.rb:72:in `block in find_db_config': undefined method `env_name' for [nil]:Array (NoMethodError) ``` The problem here is that Rails does correctly identify this as not a real configuration but returns `[nil]` along with the others. We need to make sure to flatten the array and remove all the `nil`'s before returning the `configurations` objects. Fixes #35646
-
由 Ryuta Kamizono 提交于
Internal usage for the method as public has removed at #29623.
-
由 प्रथमेश Sonpatki 提交于
[Alex Kitchens, Prathamesh Sonpatki]
-
由 Andrew White 提交于
In #10634 the behavior of Time#advance was changed to maintain a proleptic gregorian calendar for dates before calendar reform. However it didn't full address dates a long time before calendar reform and they gradually drift away from the proleptic calendar the further you go back in time. Fix this by always converting the date to gregorian before calling advance which sets the reform date to -infinity.
-
- 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 7 次提交
-
-
由 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 提交于
-