| Commit message (Collapse) | Author | Age | Files | Lines |
|\
| |
| |
| |
| | |
yahonda/supports_foreign_tables_in_abstract_adapter
Define `supports_foreign_tables?` in AbstractAdapter
|
| | |
|
|\ \
| |/
|/| |
Remove out-of-date references to jQuery [ci skip]
|
| |
| |
| |
| | |
Fixes #31703
|
| |
| |
| |
| | |
This was changed with 5d7b70f and 428939b.
|
| |
| |
| |
| |
| |
| |
| | |
Because we use `credentials` in an example of configuration files, but
`credentials` can not be used unless it is 1.8.0 or later.
Ref: 9d65ac3
|
| | |
|
|\ \
| | |
| | | |
Relax minitest versions
|
| |/
| |
| |
| |
| |
| |
| | |
We locked Minitest to 5.11.1 in #31799
because 5.11.2 included a breaking change.
The change was fixed in 5.11.3, so we no
longer need to lock in the version.
|
|/ |
|
|\
| |
| | |
Fix infinite loop when unloading autoloaded modules
|
| | |
|
| |
| |
| |
| | |
error occured during the load.
|
|\ \
| | |
| | | |
Fix example migrations in Associations guide
|
| | | |
|
|\ \ \
| |/ /
|/| | |
Use respond_to test helpers
|
| | | |
|
| | | |
|
| | | |
|
| | | |
|
|/ / |
|
| |
| |
| |
| |
| |
| | |
Since #29504, mysql2 adapter lost ability to insert zero value on
primary key due to enforce `NO_AUTO_VALUE_ON_ZERO` disabled.
That is for using `DEFAULT` on auto increment column, but we can use
`NULL` instead in that case.
|
|\ \
| | |
| | | |
Lock Minitest 5.11.1
|
|/ /
| |
| |
| |
| | |
To workaround `undefined method `error?' for` reported
at https://travis-ci.org/rails/rails/jobs/333456146
|
|\ \
| | |
| | | |
Update note on MySQL index order support [ci skip]
|
|/ /
| |
| |
| |
| | |
MySQL supports descending indexes from 8.0.1 onwards:
https://dev.mysql.com/doc/relnotes/mysql/8.0/en/news-8-0-1.html
|
|\ \
| | |
| | | |
Clarify autoload_paths and eager_load in guides per current usage.
|
| | | |
|
| | |
| | |
| | |
| | | |
Since #31422, `insert_fixtures` is deprecated.
|
| | |
| | |
| | |
| | | |
It was unused since 9e4c41c903e8e58721f2c41776a8c60ddba7a0a9.
|
|\ \ \
| | | |
| | | | |
Fix typo in API document FormHelper#fields
|
|/ / /
| | |
| | |
| | |
| | | |
- Fix typo
- Adjust output example to other example's format
|
| | |
| | |
| | |
| | | |
It is useless since 90c8be76a7d00475be5ff4db2eeedde5cc936c2d.
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
driving table
This is a regression caused by 6beb4de.
In PostgreSQL, ORDER BY expressions must appear in SELECT list when
using DISTINCT.
When using `count(:all)` with eager loading, Active Record enforces
DISTINCT to count the driving table records only. 6beb4de was caused the
regression because `count(:all)` with DISTINCT path no longer removes
ORDER BY.
We need to ignore ORDER BY when DISTINCT is enforced, otherwise not
always generated valid SQL for PostgreSQL.
Fixes #31783.
|
| | | |
|
|\ \ \
| | | |
| | | |
| | | |
| | | | |
yoreek/clear_transaction_state_when_ar_object_is_duped
Clear the transaction state when AR object is duped
|
|/ / / |
|
| | | |
|
|\ \ \
| | | |
| | | | |
Avoid passing unnecessary arguments to relation
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
Most of the time the table and predicate_builder
passed to Relation.new are exactly the
arel_table and predicate builder of the
given klass. This uses klass.arel_table
and klass.predicate_builder as the defaults,
so we don't have to pass them in most cases.
This does change the signaure of both Relation and
AssocationRelation. Are we ok with that?
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
Only enable verbose_query_logs in Rails server
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Should fix #31688 unless someone can point me to a better way to achieve
this goal. Essentially David's point was that verbose query logging when
enabled in Rails console tends to make things very noisy.
That's especially true if we display absolute paths to callsites which
sadly is still the case when we detect a caller that isn't part of the
Rails application — think gems.
Discussed this with both @matthewd and @rafaelfranca and went back and
forth between enabling if defined?(Rails::Server) or this implementation
and this one makes more sense for now.
Long term I think it'll make sense to let people override this default
disabling in Rails Console because they might want to use the feature
but for now it feels like the correct default behavior.
|
|\ \ \ \ \
| |_|/ / /
|/| | | | |
Remove code duplication for `ActionController::Metal.action`
|
| | | | | |
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
It doesn't have to do anything, but it shouldn't fail.
Fixes #31766.
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Postgresql bulk_change_table should flatten procs array
|
| | | | | | |
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Build a multi-statement query when inserting fixtures
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
- mysql will add a 2 bytes margin to the statement, so given a `max_allowed_packet` set to 1024 bytes, a 1024 bytes fixtures will no be inserted (mysql will throw an error)
- Preventing this by decreasing the max_allowed_packet by 2 bytes when doing the comparison with the actual statement size
|