| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
Pointing at Rails master generally requires pointing at Arel master
|
|\
| |
| | |
Remove single element array preprocess
|
| |
| |
| |
| |
| | |
Since 213796f, array predicate handler supports making binds, so the
preprocess is no longer needed.
|
|\ \
| | |
| | | |
Clarify add_column limit documentation
|
| | |
| | |
| | |
| | |
| | | |
The limit option is ignored by PostgreSQL and may be ignored by 3rd
party backends. Make this clear in the docs. Fixes #29922.
|
|\ \ \
| |/ /
|/| | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Solves #29923
This regression was caused due to a wrong regex to filter out
paths, introduced in commit 796a1cf0e
The regex was /^\w+\// which did not accept paths with a leading
slash and hence all absolute paths were filtered out.
This change introduces a change in regex which allows for a leading
slash and acts on the matched term accordingly.
While cascading through the case block, the paths are checked for
line number specification, existence of a directory at that path
and if none of those match, then it is considered to be a path to the
file. The regex matchers specified are filtered out via the call
to `Array#compact` since they do not match any of these conditions.
|
| |/
|/|
| |
| |
| |
| |
| |
| |
| | |
Note that the two relations must still have the same `includes` values
(which is the only time `references` actually does anything). It makes
sense for us to allow this, as `references` is called implicitly when
passing a hash to `where`.
Fixes #29411
|
|\ \
| | |
| | | |
Update Gemfile.lock to reflect arel 9.0.0.alpha
|
| | |
| | |
| | |
| | | |
Follow up to 089ca52.
|
|\ \ \
| |/ /
|/| | |
Suppress deprecated warning in Action Cable
|
| | | |
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Without this change, bundler will resolve a gemfile which is pointing at
Rails master and not arel master. The error message that someone will
get from doing this will be incredibly unhelpful, as it'll be the result
of ActiveRecord being in a half-loaded that halted at `require
"arel/collectors/composite"`, which was subsequently rescued in
`"rails/all"`
|
|\ \ \
| | | |
| | | | |
Remove useless `JoinInformation`
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Since 213796f removed `binds`, `JoinInformation` only contain `joins`.
So it is enough to return `joins` simply.
|
|\ \ \ \
| | | | |
| | | | | |
Remove unused `queries_predicates`
|
| | | | |
| | | | |
| | | | |
| | | | | |
Since 213796f, `queries_predicates` is no longer used.
|
|\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
y-yagi/extract_assert_output_and_available_pty_to_module
Extract `assert_output` and `available_pty?` into `ConsoleHelpers` module
|
| | |_|/
| |/| |
| | | |
| | | |
| | | | |
We define almost the same method with multiple tests. Therefore, it extract
into module.
|
| | | |
| | | |
| | | |
| | | | |
`bind_values` was removed from Arel
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
The output of `.databases` in SQLite will truncate to a certain size.
This causes the test to fail when run locally from a mac, or anything
which has a tempdir with more than a few characters. This pragma has
the same output, but presented as a normal query, meaning no truncation
will occur.
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
koic/fix_test_add_column_with_timestamp_type_oracle
Fix `test_add_column_with_timestamp_type` when using Oracle
|
| |/ / / |
|
|\ \ \ \
| |_|/ /
|/| | | |
Stop creating ApplicationRecord on model generation
|
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | |
| | | | |
When generating models, we created ApplicationRecord in the default
location if no file existed there. That was annoying for people who
moved it to somewhere else in the autoload path. At this point, the
vast majority of apps should have either run the upgrade script or
generated a model since upgrading. For those that haven't the error
message after generating a new model should be helpful:
NameError: uninitialized constant ApplicationRecord
To ease friction in that case, this also adds a generator for
ApplicationRecord.
|
|\ \ \ \
| |_|/ /
|/| | | |
[ci skip] Add documentation for after_create_commit and after_update_commit callbacks
|
|/ / /
| | |
| | |
| | | |
callbacks
|
|\ \ \
| | | |
| | | | |
Make actionpack frozen string friendly
|
| |/ / |
|
|\ \ \
| | | |
| | | | |
Fix `warning: ambiguous first argument`
|
|/ / /
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
This fixes the following warning:
```
railties/test/application/rake/dbs_test.rb:265: warning: ambiguous first argument; put parentheses or a space even after `/' operator
```
|
|\ \ \
| | | |
| | | | |
[API DOCUMENTATION] [MINOR] Correct description of ActionController::Parameters#delete
|
| | | | |
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | | |
remove depreciated assertion to eliminate warning
|
| | |_|/
| |/| |
| | | |
| | | | |
Signed-off-by: Yuki Nishijima <yk.nishijima@gmail.com>
|
|\ \ \ \
| |/ / /
|/| | |
| | | |
| | | | |
deivid-rodriguez/follow_up_to_multiple_location_engine_mounting
Fix regression introduced by fixing mounting the same engine in multiple locations
|
| | | | |
|
|\ \ \ \
| | | | |
| | | | |
| | | | | |
Update rack-test dependency constraint
|
| | | | | |
|
|\ \ \ \ \
| |_|_|_|/
|/| | | |
| | | | |
| | | | | |
xtina-starr/suppress-warning-from-actionview-controller-helper
Suppress warning from actionview controller helper.
|
|/ / / /
| | | |
| | | |
| | | |
| | | |
| | | | |
Explicitly pass a destructed array to the delegate method.
Signed-off-by: Yuki Nishijima <yk.nishijima@gmail.com>
|
|\ \ \ \
| | | | |
| | | | | |
Use frozen string literal in actionview/
|
| | | | | |
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Fix warnings in railties tests
|
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This warning has been fixed in sass-rails. This change picks up the fix.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix `COUNT(DISTINCT ...)` with `ORDER BY` and `LIMIT`
|
| | | | | | | |
|
| | | | | | | |
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Since #26972, `ORDER BY` is kept if `LIMIT` is presented for
performance. But in most SQL servers (e.g. PostgreSQL, SQL Server, etc),
`ORDER BY` expressions must appear in select list for `SELECT DISTINCT`.
We should not replace existing select list in that case.
|