| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
These tests are for testing the `rake` method.
|
|
|
|
| |
`Journey::Router::RoutingError` is no longer used since db06d128262b49c8b02e153cf95eb46f4eff364b.
|
|\
| |
| |
| |
| | |
rmacklin/synchronize-actioncable-compiled-bundle-and-source
Synchronize ActionCable JS source code with compiled bundle
|
|/
|
|
|
|
|
|
| |
30a0c7e04093add0b14be6da17c7496e7dd40e10 commited changes to the
compiled bundle but not to the corresponding source files. This meant
that running `yarn build` was producing untracked changes to the
compiled bundle. The fix is to commit the changes to the source files
so that they are in sync.
|
|\
| |
| | |
Re-add changes_applied doc
|
| |
| |
| |
| | |
[ci skip]
|
|\ \
| | |
| | | |
Fix typo and clarify documentation
|
|/ /
| |
| |
| |
| |
| | |
This commit fixes a small typo in documentation of the
"UNLOGGED" table option for PostgreSQL databases, and
clarifies the documentation slightly.
|
|/
|
| |
[ci skip]
|
|\
| |
| | |
Replace `cache_key` with `cache_key_with_version` on caching_with_rails in Caching with Rails guide [ci skip]
|
|/
|
|
| |
[ci skip]
|
|
|
|
|
|
|
|
|
| |
* Arel: Implemented DB-aware NULL-safe comparison
* Fixed where clause inversion for NULL-safe comparison
* Renaming "null_safe_eq" to "is_not_distinct_from", "null_safe_not_eq" to "is_distinct_from"
[Dmytro Shteflyuk + Rafael Mendonça França]
|
|\
| |
| | |
Fix a method call in bin/setup file
|
|/
|
|
| |
Follow up to a725539de677adbea0ced19d65647e975dbd3f84
|
|\
| |
| | |
Add test for normalizing non-unicode string
|
| |
| |
| |
| | |
Closes #34062
|
|\ \
| |/
|/| |
Allow patching polling interval logarithmic multiplier
|
|/ |
|
|\
| |
| | |
fix typo on association_basics.md [ci skip]
|
|/ |
|
|\
| |
| | |
Allow rescue from parse errors
|
| |
| |
| |
| | |
[Gannon McGibbon + Josh Cheek]
|
|\ \
| |/
|/| |
Describe how has_many's :dependent option affects #delete
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
I was puzzled about why `collection=` was destroying the removed
records on an association with `dependent: :destroy`, even after
consulting the documentation for that option. I had to dive into the
Active Record source to understand what was going on: eventually
`collection=` calls `collection.delete` on the ousted records, and it
also uses the `:dependent` option to decide how to remove records.
It would have helped me to have mention of this in the documentation for
`:dependent`, not just under `collection.delete` (which I found much
later).
Briefly mention the broader impacts of `:dependent` in the Association
Basics guide.
[ci skip]
|
|\ \
| |/
|/| |
Remove asset paths from autoload_paths
|
| |
| |
| |
| |
| | |
Remove `app/assets` and `app/javascript` from `eager_load_paths`
and `autoload_paths`.
|
|\ \
| | |
| | |
| | | |
Fix: Arel now emits a single pair of parens for UNION and UNION ALL
|
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
mysql has a great implementation to suppress multiple parens for union
sql statements.
This moves that functionality to the generic implementation
This also introduces that functionality for UNION ALL
|
|\ \ \
| | | |
| | | | |
Reset Capybara sessions if failed system test screenshot raising an exception
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Reset Capybara sessions if `take_failed_screenshot` raise exception
in system test `after_teardown`.
|
|\ \ \ \
| |_|/ /
|/| | | |
Adjust bind length of SQLite to default (999)
|
| | | |
| | | |
| | | |
| | | |
| | | | |
Change `#bind_params_length` in SQLite adapter to return the default
maximum amount (999). See https://www.sqlite.org/limits.html
|
|\ \ \ \
| | | | |
| | | | |
| | | | |
| | | | | |
bogdanvlviv/ensure-that-connected_to-establish_connection
Ensure that `ActiveRecord::Base#connected_to` with `:database` establishes connection
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
connection
Related to #34052
|
|\ \ \ \ \
| | | | | |
| | | | | | |
Add support for UNLOGGED Postgresql tables
|
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
This commit adds support for the
`ActiveRecord::ConnectionAdapters::PostgreSQLAdapter.create_unlogged_tables`
setting, which turns `CREATE TABLE` SQL statements into
`CREATE UNLOGGED TABLE` statements.
This can improve PostgreSQL performance but at the
cost of data durability, and thus it is highly recommended
that you *DO NOT* enable this in a production environment.
|
|\ \ \ \ \ \
| | | | | | |
| | | | | | | |
Fix ignored options in the `#added?` method
|
| | | | | | |
| | | | | | |
| | | | | | |
| | | | | | | |
Fixes #34416
|
|\ \ \ \ \ \ \
| | | | | | | |
| | | | | | | | |
Add an alias for the --webpack option
|
|/ / / / / / / |
|
|\ \ \ \ \ \ \
| |_|/ / / / /
|/| | | | | | |
Ignore warnings such as `Psych.safe_load is deprecated`
|
|/ / / / / /
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | |
| | | | | | |
Addressing warnings are important but it should be out of this test scope.
https://travis-ci.org/rails/rails/jobs/454145524#L4122-L4131
```
.F
Failure:
ApplicationTests::BinSetupTest#test_bin_setup_output [test/application/bin_setup_test.rb:49]:
--- expected
+++ actual
@@ -1,4 +1,5 @@
"== Installing dependencies ==
+warning: Passing permitted_classes with the 2nd argument of Psych.safe_load is deprecated. Use keyword argument like Psych.safe_load(yaml, permitted_classes: ...) instead.
The Gemfile's dependencies are satisfied
== Preparing database ==
rails test test/application/bin_setup_test.rb:38
```
|
|\ \ \ \ \ \
| |_|_|/ / /
|/| | | | | |
Make `PERMITTED_TYPES` private
|
|/ / / / /
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The constant `PERMITTED_TYPES` is only used by the private method
`serialize_argument` and it already has the `# :nodoc:` annotation as
the other constants in the class.
Complements e899e22
|
|\ \ \ \ \
| |_|/ / /
|/| | | |
| | | | |
| | | | | |
eugeneius/rm_ensure_from_with_transaction_returning_status
Remove ensure from with_transaction_returning_status
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
The test added in 12b0b26df7560ab5199ba830586864085441508f passes even
without this code since 9b8c7796a9c2048208aa843ad3dc477dffa8bdee, as the
call to `id` in `remember_transaction_record_state` now triggers a
`sync_with_transaction_state` which discards the leftover state from the
previous transaction.
This issue had already been fixed for `save!`, `destroy` and `touch` in
caae79a385ce112245262a17414bcd96bea013c2, but continued to affect `save`
because the call to `rollback_active_record_state!` in that method would
increment the transaction level before `add_to_transaction` could clear
it, preventing the fix from working correctly.
As `rollback_active_record_state!` was removed entirely in
48007d5390db47fc1223f57c8e7ab3ebb7c3a3d7, this code is no longer needed.
|
|\ \ \ \ \
| |/ / / /
|/| | | |
| | | | |
| | | | | |
albertoalmagro/include-big-decimal-as-supported-type
Document missing supported types [ci skip]
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
This commit adds missing types to the supported types list, which
was extended in #30941
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Follow up a741208f80dd33420a56486bd9ed2b0b9862234a.
Since a741208, `Decimal#serialize` which is superclass of `Money` type
is no longer no-op, so it consistently serialize/deserialize a value as
a decimal even if schema default.
|
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | |
| | | | | |
Related 34cc301f03aea2e579d6687a9ea9782afc1089a0.
`QueryAttribute#value_for_database` calls only `type.serialize`, and
`Decimal#serialize` is a no-op unlike other attribute types.
Whether or not `serialize` will invoke `cast` is undefined in our test
cases, but it actually does not work properly unless it does so for now.
|