activerecord 7.0.8 → 7.1.1
Sign up to get free protection for your applications and to get access to all the features.
- checksums.yaml +4 -4
- data/CHANGELOG.md +1412 -1507
- data/MIT-LICENSE +1 -1
- data/README.rdoc +15 -16
- data/lib/active_record/aggregations.rb +16 -13
- data/lib/active_record/association_relation.rb +1 -1
- data/lib/active_record/associations/association.rb +18 -3
- data/lib/active_record/associations/association_scope.rb +16 -9
- data/lib/active_record/associations/belongs_to_association.rb +14 -6
- data/lib/active_record/associations/builder/association.rb +3 -3
- data/lib/active_record/associations/builder/belongs_to.rb +21 -8
- data/lib/active_record/associations/builder/has_and_belongs_to_many.rb +1 -5
- data/lib/active_record/associations/builder/singular_association.rb +4 -0
- data/lib/active_record/associations/collection_association.rb +15 -9
- data/lib/active_record/associations/collection_proxy.rb +15 -10
- data/lib/active_record/associations/foreign_association.rb +10 -3
- data/lib/active_record/associations/has_many_association.rb +20 -13
- data/lib/active_record/associations/has_many_through_association.rb +10 -6
- data/lib/active_record/associations/has_one_association.rb +10 -3
- data/lib/active_record/associations/join_dependency.rb +10 -8
- data/lib/active_record/associations/preloader/association.rb +27 -6
- data/lib/active_record/associations/preloader.rb +13 -10
- data/lib/active_record/associations/singular_association.rb +1 -1
- data/lib/active_record/associations/through_association.rb +22 -11
- data/lib/active_record/associations.rb +295 -199
- data/lib/active_record/attribute_assignment.rb +0 -2
- data/lib/active_record/attribute_methods/before_type_cast.rb +17 -0
- data/lib/active_record/attribute_methods/dirty.rb +40 -26
- data/lib/active_record/attribute_methods/primary_key.rb +76 -24
- data/lib/active_record/attribute_methods/query.rb +28 -16
- data/lib/active_record/attribute_methods/read.rb +18 -5
- data/lib/active_record/attribute_methods/serialization.rb +150 -31
- data/lib/active_record/attribute_methods/write.rb +3 -3
- data/lib/active_record/attribute_methods.rb +105 -21
- data/lib/active_record/attributes.rb +3 -3
- data/lib/active_record/autosave_association.rb +55 -9
- data/lib/active_record/base.rb +7 -2
- data/lib/active_record/callbacks.rb +10 -24
- data/lib/active_record/coders/column_serializer.rb +61 -0
- data/lib/active_record/coders/json.rb +1 -1
- data/lib/active_record/coders/yaml_column.rb +70 -42
- data/lib/active_record/connection_adapters/abstract/connection_handler.rb +163 -88
- data/lib/active_record/connection_adapters/abstract/connection_pool/queue.rb +2 -0
- data/lib/active_record/connection_adapters/abstract/connection_pool/reaper.rb +3 -1
- data/lib/active_record/connection_adapters/abstract/connection_pool.rb +63 -43
- data/lib/active_record/connection_adapters/abstract/database_limits.rb +5 -0
- data/lib/active_record/connection_adapters/abstract/database_statements.rb +128 -32
- data/lib/active_record/connection_adapters/abstract/query_cache.rb +60 -22
- data/lib/active_record/connection_adapters/abstract/quoting.rb +41 -6
- data/lib/active_record/connection_adapters/abstract/savepoints.rb +4 -3
- data/lib/active_record/connection_adapters/abstract/schema_creation.rb +18 -4
- data/lib/active_record/connection_adapters/abstract/schema_definitions.rb +137 -11
- data/lib/active_record/connection_adapters/abstract/schema_statements.rb +289 -124
- data/lib/active_record/connection_adapters/abstract/transaction.rb +287 -58
- data/lib/active_record/connection_adapters/abstract_adapter.rb +502 -91
- data/lib/active_record/connection_adapters/abstract_mysql_adapter.rb +207 -108
- data/lib/active_record/connection_adapters/column.rb +9 -0
- data/lib/active_record/connection_adapters/mysql/column.rb +1 -0
- data/lib/active_record/connection_adapters/mysql/database_statements.rb +22 -143
- data/lib/active_record/connection_adapters/mysql/quoting.rb +16 -12
- data/lib/active_record/connection_adapters/mysql/schema_creation.rb +9 -0
- data/lib/active_record/connection_adapters/mysql/schema_definitions.rb +6 -0
- data/lib/active_record/connection_adapters/mysql/schema_dumper.rb +1 -1
- data/lib/active_record/connection_adapters/mysql/schema_statements.rb +18 -13
- data/lib/active_record/connection_adapters/mysql2/database_statements.rb +148 -0
- data/lib/active_record/connection_adapters/mysql2_adapter.rb +98 -53
- data/lib/active_record/connection_adapters/pool_config.rb +14 -5
- data/lib/active_record/connection_adapters/pool_manager.rb +19 -9
- data/lib/active_record/connection_adapters/postgresql/column.rb +14 -3
- data/lib/active_record/connection_adapters/postgresql/database_statements.rb +71 -40
- data/lib/active_record/connection_adapters/postgresql/oid/range.rb +11 -2
- data/lib/active_record/connection_adapters/postgresql/oid/timestamp_with_time_zone.rb +1 -1
- data/lib/active_record/connection_adapters/postgresql/quoting.rb +10 -6
- data/lib/active_record/connection_adapters/postgresql/referential_integrity.rb +3 -9
- data/lib/active_record/connection_adapters/postgresql/schema_creation.rb +76 -6
- data/lib/active_record/connection_adapters/postgresql/schema_definitions.rb +131 -2
- data/lib/active_record/connection_adapters/postgresql/schema_dumper.rb +53 -0
- data/lib/active_record/connection_adapters/postgresql/schema_statements.rb +349 -55
- data/lib/active_record/connection_adapters/postgresql_adapter.rb +338 -176
- data/lib/active_record/connection_adapters/schema_cache.rb +287 -59
- data/lib/active_record/connection_adapters/sqlite3/column.rb +49 -0
- data/lib/active_record/connection_adapters/sqlite3/database_statements.rb +45 -39
- data/lib/active_record/connection_adapters/sqlite3/quoting.rb +4 -3
- data/lib/active_record/connection_adapters/sqlite3/schema_definitions.rb +1 -0
- data/lib/active_record/connection_adapters/sqlite3/schema_statements.rb +26 -7
- data/lib/active_record/connection_adapters/sqlite3_adapter.rb +209 -79
- data/lib/active_record/connection_adapters/statement_pool.rb +7 -0
- data/lib/active_record/connection_adapters/trilogy/database_statements.rb +98 -0
- data/lib/active_record/connection_adapters/trilogy_adapter.rb +254 -0
- data/lib/active_record/connection_adapters.rb +3 -1
- data/lib/active_record/connection_handling.rb +71 -94
- data/lib/active_record/core.rb +136 -148
- data/lib/active_record/counter_cache.rb +46 -25
- data/lib/active_record/database_configurations/database_config.rb +9 -3
- data/lib/active_record/database_configurations/hash_config.rb +22 -12
- data/lib/active_record/database_configurations/url_config.rb +17 -11
- data/lib/active_record/database_configurations.rb +86 -33
- data/lib/active_record/delegated_type.rb +8 -3
- data/lib/active_record/deprecator.rb +7 -0
- data/lib/active_record/destroy_association_async_job.rb +2 -0
- data/lib/active_record/encryption/auto_filtered_parameters.rb +66 -0
- data/lib/active_record/encryption/cipher/aes256_gcm.rb +4 -1
- data/lib/active_record/encryption/config.rb +25 -1
- data/lib/active_record/encryption/configurable.rb +12 -19
- data/lib/active_record/encryption/context.rb +10 -3
- data/lib/active_record/encryption/contexts.rb +5 -1
- data/lib/active_record/encryption/derived_secret_key_provider.rb +8 -2
- data/lib/active_record/encryption/encryptable_record.rb +36 -18
- data/lib/active_record/encryption/encrypted_attribute_type.rb +17 -6
- data/lib/active_record/encryption/extended_deterministic_queries.rb +66 -54
- data/lib/active_record/encryption/extended_deterministic_uniqueness_validator.rb +3 -3
- data/lib/active_record/encryption/key_generator.rb +12 -1
- data/lib/active_record/encryption/message_serializer.rb +2 -0
- data/lib/active_record/encryption/properties.rb +3 -3
- data/lib/active_record/encryption/scheme.rb +19 -22
- data/lib/active_record/encryption.rb +1 -0
- data/lib/active_record/enum.rb +113 -26
- data/lib/active_record/errors.rb +108 -15
- data/lib/active_record/explain.rb +23 -3
- data/lib/active_record/fixture_set/model_metadata.rb +14 -4
- data/lib/active_record/fixture_set/render_context.rb +2 -0
- data/lib/active_record/fixture_set/table_row.rb +29 -8
- data/lib/active_record/fixtures.rb +119 -71
- data/lib/active_record/future_result.rb +30 -5
- data/lib/active_record/gem_version.rb +3 -3
- data/lib/active_record/inheritance.rb +30 -16
- data/lib/active_record/insert_all.rb +55 -8
- data/lib/active_record/integration.rb +8 -8
- data/lib/active_record/internal_metadata.rb +120 -30
- data/lib/active_record/locking/pessimistic.rb +5 -2
- data/lib/active_record/log_subscriber.rb +29 -12
- data/lib/active_record/marshalling.rb +56 -0
- data/lib/active_record/message_pack.rb +124 -0
- data/lib/active_record/middleware/database_selector/resolver.rb +4 -0
- data/lib/active_record/middleware/database_selector.rb +5 -7
- data/lib/active_record/middleware/shard_selector.rb +3 -1
- data/lib/active_record/migration/command_recorder.rb +104 -5
- data/lib/active_record/migration/compatibility.rb +131 -5
- data/lib/active_record/migration/default_strategy.rb +23 -0
- data/lib/active_record/migration/execution_strategy.rb +19 -0
- data/lib/active_record/migration.rb +213 -109
- data/lib/active_record/model_schema.rb +60 -40
- data/lib/active_record/nested_attributes.rb +21 -3
- data/lib/active_record/normalization.rb +159 -0
- data/lib/active_record/persistence.rb +184 -34
- data/lib/active_record/promise.rb +84 -0
- data/lib/active_record/query_cache.rb +3 -21
- data/lib/active_record/query_logs.rb +77 -52
- data/lib/active_record/query_logs_formatter.rb +41 -0
- data/lib/active_record/querying.rb +15 -2
- data/lib/active_record/railtie.rb +109 -47
- data/lib/active_record/railties/controller_runtime.rb +10 -5
- data/lib/active_record/railties/databases.rake +139 -145
- data/lib/active_record/railties/job_runtime.rb +23 -0
- data/lib/active_record/readonly_attributes.rb +32 -5
- data/lib/active_record/reflection.rb +162 -44
- data/lib/active_record/relation/batches/batch_enumerator.rb +5 -3
- data/lib/active_record/relation/batches.rb +190 -61
- data/lib/active_record/relation/calculations.rb +160 -63
- data/lib/active_record/relation/delegation.rb +22 -8
- data/lib/active_record/relation/finder_methods.rb +77 -16
- data/lib/active_record/relation/merger.rb +2 -0
- data/lib/active_record/relation/predicate_builder/association_query_value.rb +11 -2
- data/lib/active_record/relation/predicate_builder/polymorphic_array_value.rb +4 -6
- data/lib/active_record/relation/predicate_builder/relation_handler.rb +5 -1
- data/lib/active_record/relation/predicate_builder.rb +26 -14
- data/lib/active_record/relation/query_attribute.rb +2 -1
- data/lib/active_record/relation/query_methods.rb +352 -63
- data/lib/active_record/relation/spawn_methods.rb +18 -1
- data/lib/active_record/relation.rb +76 -35
- data/lib/active_record/result.rb +19 -5
- data/lib/active_record/runtime_registry.rb +10 -1
- data/lib/active_record/sanitization.rb +51 -11
- data/lib/active_record/schema.rb +2 -3
- data/lib/active_record/schema_dumper.rb +46 -7
- data/lib/active_record/schema_migration.rb +68 -33
- data/lib/active_record/scoping/default.rb +15 -5
- data/lib/active_record/scoping/named.rb +2 -2
- data/lib/active_record/scoping.rb +2 -1
- data/lib/active_record/secure_password.rb +60 -0
- data/lib/active_record/secure_token.rb +21 -3
- data/lib/active_record/signed_id.rb +7 -5
- data/lib/active_record/store.rb +8 -8
- data/lib/active_record/suppressor.rb +3 -1
- data/lib/active_record/table_metadata.rb +10 -1
- data/lib/active_record/tasks/database_tasks.rb +127 -105
- data/lib/active_record/tasks/mysql_database_tasks.rb +15 -6
- data/lib/active_record/tasks/postgresql_database_tasks.rb +16 -13
- data/lib/active_record/tasks/sqlite_database_tasks.rb +15 -7
- data/lib/active_record/test_fixtures.rb +113 -96
- data/lib/active_record/timestamp.rb +27 -15
- data/lib/active_record/token_for.rb +113 -0
- data/lib/active_record/touch_later.rb +11 -6
- data/lib/active_record/transactions.rb +36 -10
- data/lib/active_record/type/adapter_specific_registry.rb +1 -8
- data/lib/active_record/type/internal/timezone.rb +7 -2
- data/lib/active_record/type/time.rb +4 -0
- data/lib/active_record/validations/absence.rb +1 -1
- data/lib/active_record/validations/numericality.rb +5 -4
- data/lib/active_record/validations/presence.rb +5 -28
- data/lib/active_record/validations/uniqueness.rb +47 -2
- data/lib/active_record/validations.rb +8 -4
- data/lib/active_record/version.rb +1 -1
- data/lib/active_record.rb +121 -16
- data/lib/arel/errors.rb +10 -0
- data/lib/arel/factory_methods.rb +4 -0
- data/lib/arel/nodes/binary.rb +6 -1
- data/lib/arel/nodes/bound_sql_literal.rb +61 -0
- data/lib/arel/nodes/cte.rb +36 -0
- data/lib/arel/nodes/fragments.rb +35 -0
- data/lib/arel/nodes/homogeneous_in.rb +0 -8
- data/lib/arel/nodes/leading_join.rb +8 -0
- data/lib/arel/nodes/node.rb +111 -2
- data/lib/arel/nodes/sql_literal.rb +6 -0
- data/lib/arel/nodes/table_alias.rb +4 -0
- data/lib/arel/nodes.rb +4 -0
- data/lib/arel/predications.rb +2 -0
- data/lib/arel/table.rb +9 -5
- data/lib/arel/visitors/mysql.rb +8 -1
- data/lib/arel/visitors/to_sql.rb +81 -17
- data/lib/arel/visitors/visitor.rb +2 -2
- data/lib/arel.rb +16 -2
- data/lib/rails/generators/active_record/application_record/USAGE +8 -0
- data/lib/rails/generators/active_record/migration.rb +3 -1
- data/lib/rails/generators/active_record/model/USAGE +113 -0
- data/lib/rails/generators/active_record/model/model_generator.rb +15 -6
- metadata +46 -11
- data/lib/active_record/connection_adapters/legacy_pool_manager.rb +0 -35
- data/lib/active_record/null_relation.rb +0 -63
data/CHANGELOG.md
CHANGED
@@ -1,2376 +1,2281 @@
|
|
1
|
-
## Rails 7.
|
1
|
+
## Rails 7.1.1 (October 11, 2023) ##
|
2
2
|
|
3
|
-
* Fix
|
4
|
-
using 7.0+ Migrations and SQLite.
|
5
|
-
|
6
|
-
*Hartley McGuire*
|
7
|
-
|
8
|
-
* Fix unscope is not working in specific case
|
9
|
-
|
10
|
-
Before:
|
11
|
-
```ruby
|
12
|
-
Post.where(id: 1...3).unscope(where: :id).to_sql # "SELECT `posts`.* FROM `posts` WHERE `posts`.`id` >= 1 AND `posts`.`id` < 3"
|
13
|
-
|
14
|
-
```
|
15
|
-
|
16
|
-
After:
|
17
|
-
```ruby
|
18
|
-
Post.where(id: 1...3).unscope(where: :id).to_sql # "SELECT `posts`.* FROM `posts`"
|
19
|
-
```
|
20
|
-
|
21
|
-
Fixes #48094.
|
22
|
-
|
23
|
-
*Kazuya Hatanaka*
|
24
|
-
|
25
|
-
* Fix associations to a STI model including a `class_name` parameter
|
26
|
-
|
27
|
-
```ruby
|
28
|
-
class Product < ApplicationRecord
|
29
|
-
has_many :requests, as: :requestable, class_name: "ProductRequest", dependent: :destroy
|
30
|
-
end
|
31
|
-
|
32
|
-
# STI tables
|
33
|
-
class Request < ApplicationRecord
|
34
|
-
belongs_to :requestable, polymorphic: true
|
35
|
-
|
36
|
-
validate :request_type, presence: true
|
37
|
-
end
|
38
|
-
|
39
|
-
class ProductRequest < Request
|
40
|
-
belongs_to :user
|
41
|
-
end
|
42
|
-
```
|
43
|
-
|
44
|
-
Accessing such association would lead to:
|
45
|
-
|
46
|
-
```
|
47
|
-
table_metadata.rb:22:in `has_column?': undefined method `key?' for nil:NilClass (NoMethodError)
|
48
|
-
```
|
49
|
-
|
50
|
-
*Romain Filinto*
|
3
|
+
* Fix auto populating IDENTITY columns for PostgreSQL.
|
51
4
|
|
52
|
-
*
|
53
|
-
|
54
|
-
*Hartley McGuire*
|
5
|
+
*fatkodima*
|
55
6
|
|
56
|
-
* Fix
|
7
|
+
* Fix "ArgumentError: wrong number of arguments (given 3, expected 2)" when
|
8
|
+
down migrating `rename_table` in older migrations.
|
57
9
|
|
58
|
-
*
|
10
|
+
*fatkodima*
|
59
11
|
|
60
|
-
|
12
|
+
* Do not require the Action Text, Active Storage and Action Mailbox tables
|
13
|
+
to be present when running when running test on CI.
|
61
14
|
|
62
|
-
*
|
15
|
+
*Rafael Mendonça França*
|
63
16
|
|
64
17
|
|
65
|
-
## Rails 7.0
|
18
|
+
## Rails 7.1.0 (October 05, 2023) ##
|
66
19
|
|
67
20
|
* No changes.
|
68
21
|
|
69
22
|
|
70
|
-
## Rails 7.0.
|
71
|
-
|
72
|
-
* Restores functionality to the missing method when using enums and fixes.
|
73
|
-
|
74
|
-
*paulreece*
|
75
|
-
|
76
|
-
* Fix `StatementCache::Substitute` with serialized type.
|
23
|
+
## Rails 7.1.0.rc2 (October 01, 2023) ##
|
77
24
|
|
78
|
-
|
25
|
+
* Remove -shm and -wal SQLite files when `rails db:drop` is run.
|
79
26
|
|
80
|
-
*
|
27
|
+
*Niklas Häusele*
|
81
28
|
|
82
|
-
|
83
|
-
|
84
|
-
* Correctly dump check constraints for MySQL 8.0.16+.
|
85
|
-
|
86
|
-
*Steve Hill*
|
87
|
-
|
88
|
-
* Fix `ActiveRecord::QueryMethods#in_order_of` to include `nil`s, to match the
|
89
|
-
behavior of `Enumerable#in_order_of`.
|
29
|
+
* Revert the change to raise an `ArgumentError` when `#accepts_nested_attributes_for` is declared more than once for
|
30
|
+
an association in the same class.
|
90
31
|
|
91
|
-
|
92
|
-
|
32
|
+
The reverted behavior broke the case where the `#accepts_nested_attributes_for` was defined in a concern and
|
33
|
+
where overridden in the class that included the concern.
|
93
34
|
|
94
|
-
*
|
35
|
+
*Rafael Mendonça França*
|
95
36
|
|
96
|
-
* Revert "Fix autosave associations with validations added on `:base` of the associated objects."
|
97
37
|
|
98
|
-
|
99
|
-
but broke many assumptions which key these errors were stored.
|
38
|
+
## Rails 7.1.0.rc1 (September 27, 2023) ##
|
100
39
|
|
101
|
-
|
40
|
+
* Better naming for unique constraints support.
|
102
41
|
|
103
|
-
|
42
|
+
Naming unique keys leads to misunderstanding it's a short-hand of unique indexes.
|
43
|
+
Just naming it unique constraints is not misleading.
|
104
44
|
|
105
|
-
|
106
|
-
Now, any UPDATE or DELETE to a record is considered a change, and will result in `#previously_new_record?`
|
107
|
-
returning false.
|
45
|
+
In Rails 7.1.0.beta1 or before:
|
108
46
|
|
109
|
-
|
47
|
+
```ruby
|
48
|
+
add_unique_key :sections, [:position], deferrable: :deferred, name: "unique_section_position"
|
49
|
+
remove_unique_key :sections, name: "unique_section_position"
|
50
|
+
```
|
110
51
|
|
111
|
-
|
52
|
+
Now:
|
112
53
|
|
113
|
-
|
54
|
+
```ruby
|
55
|
+
add_unique_constraint :sections, [:position], deferrable: :deferred, name: "unique_section_position"
|
56
|
+
remove_unique_constraint :sections, name: "unique_section_position"
|
57
|
+
```
|
114
58
|
|
115
|
-
*
|
59
|
+
*Ryuta Kamizono*
|
116
60
|
|
117
|
-
|
118
|
-
the query cache, but this had the adverse effect to clearing the primary key when
|
119
|
-
the query argument contained an `ActiveRecord::Base` instance.
|
61
|
+
* Fix duplicate quoting for check constraint expressions in schema dump when using MySQL
|
120
62
|
|
121
|
-
|
63
|
+
A check constraint with an expression, that already contains quotes, lead to an invalid schema
|
64
|
+
dump with the mysql2 adapter.
|
122
65
|
|
123
|
-
|
66
|
+
Fixes #42424.
|
124
67
|
|
68
|
+
*Felix Tscheulin*
|
125
69
|
|
126
|
-
|
70
|
+
* Performance tune the SQLite3 adapter connection configuration
|
127
71
|
|
128
|
-
|
72
|
+
For Rails applications, the Write-Ahead-Log in normal syncing mode with a capped journal size, a healthy shared memory buffer and a shared cache will perform, on average, 2× better.
|
129
73
|
|
130
|
-
*
|
74
|
+
*Stephen Margheim*
|
131
75
|
|
132
|
-
*
|
76
|
+
* Allow SQLite3 `busy_handler` to be configured with simple max number of `retries`
|
133
77
|
|
134
|
-
|
78
|
+
Retrying busy connections without delay is a preferred practice for performance-sensitive applications. Add support for a `database.yml` `retries` integer, which is used in a simple `busy_handler` function to retry busy connections without exponential backoff up to the max number of `retries`.
|
135
79
|
|
136
|
-
*
|
80
|
+
*Stephen Margheim*
|
137
81
|
|
138
|
-
|
82
|
+
* The SQLite3 adapter now supports `supports_insert_returning?`
|
139
83
|
|
140
|
-
|
84
|
+
Implementing the full `supports_insert_returning?` contract means the SQLite3 adapter supports auto-populated columns (#48241) as well as custom primary keys.
|
141
85
|
|
142
|
-
*
|
86
|
+
*Stephen Margheim*
|
143
87
|
|
144
|
-
*
|
88
|
+
* Ensure the SQLite3 adapter handles default functions with the `||` concatenation operator
|
145
89
|
|
146
|
-
|
147
|
-
|
148
|
-
Treasure.where(price_estimates: PriceEstimate.all)
|
149
|
-
#=> SELECT (...) WHERE "treasures"."id" IN (SELECT "price_estimates"."estimate_of_id" FROM "price_estimates")
|
150
|
-
```
|
90
|
+
Previously, this default function would produce the static string `"'Ruby ' || 'on ' || 'Rails'"`.
|
91
|
+
Now, the adapter will appropriately receive and use `"Ruby on Rails"`.
|
151
92
|
|
152
|
-
Later:
|
153
93
|
```ruby
|
154
|
-
|
155
|
-
#=> SELECT (...) WHERE "treasures"."id" IN (SELECT "price_estimates"."estimate_of_id" FROM "price_estimates" WHERE "price_estimates"."estimate_of_type" = 'Treasure')
|
94
|
+
change_column_default "test_models", "ruby_on_rails", -> { "('Ruby ' || 'on ' || 'Rails')" }
|
156
95
|
```
|
157
96
|
|
158
|
-
*
|
159
|
-
|
160
|
-
* Fix decrementing counter caches on optimistically locked record deletion
|
161
|
-
|
162
|
-
*fatkodima*
|
163
|
-
|
164
|
-
* Ensure binary-destined values have binary encoding during type cast.
|
165
|
-
|
166
|
-
*Matthew Draper*
|
167
|
-
|
168
|
-
* Preserve existing column default functions when altering table in SQLite.
|
169
|
-
|
170
|
-
*fatkodima*
|
171
|
-
|
172
|
-
* Remove table alias added when using `where.missing` or `where.associated`.
|
173
|
-
|
174
|
-
*fatkodima*
|
175
|
-
|
176
|
-
* Fix `Enumerable#in_order_of` to only flatten first level to preserve nesting.
|
177
|
-
|
178
|
-
*Miha Rekar*
|
97
|
+
*Stephen Margheim*
|
179
98
|
|
99
|
+
* Dump PostgreSQL schemas as part of the schema dump.
|
180
100
|
|
181
|
-
|
101
|
+
*Lachlan Sylvester*
|
182
102
|
|
183
|
-
* No changes.
|
184
|
-
|
185
|
-
## Rails 7.0.5 (May 24, 2023) ##
|
186
|
-
|
187
|
-
* Type cast `#attribute_changed?` `:from` and `:to` options.
|
188
103
|
|
189
|
-
|
104
|
+
## Rails 7.1.0.beta1 (September 13, 2023) ##
|
190
105
|
|
191
|
-
*
|
106
|
+
* Encryption now supports `support_unencrypted_data` being set per-attribute.
|
192
107
|
|
193
|
-
|
108
|
+
You can now opt out of `support_unencrypted_data` on a specific encrypted attribute.
|
109
|
+
This only has an effect if `ActiveRecord::Encryption.config.support_unencrypted_data == true`.
|
194
110
|
|
195
|
-
|
111
|
+
```ruby
|
112
|
+
class User < ActiveRecord::Base
|
113
|
+
encrypts :name, deterministic: true, support_unencrypted_data: false
|
114
|
+
encrypts :email, deterministic: true
|
115
|
+
end
|
116
|
+
```
|
196
117
|
|
197
118
|
*Alex Ghiculescu*
|
198
119
|
|
199
|
-
*
|
200
|
-
|
201
|
-
*Hartley McGuire*
|
120
|
+
* Add instrumentation for Active Record transactions
|
202
121
|
|
203
|
-
|
122
|
+
Allows subscribing to transaction events for tracking/instrumentation. The event payload contains the connection and the outcome (commit, rollback, restart, incomplete), as well as timing details.
|
204
123
|
|
205
|
-
|
124
|
+
```ruby
|
125
|
+
ActiveSupport::Notifications.subscribe("transaction.active_record") do |event|
|
126
|
+
puts "Transaction event occurred!"
|
127
|
+
connection = event.payload[:connection]
|
128
|
+
puts "Connection: #{connection.inspect}"
|
129
|
+
end
|
130
|
+
```
|
206
131
|
|
207
|
-
*
|
132
|
+
*Daniel Colson*, *Ian Candy*
|
208
133
|
|
209
|
-
|
134
|
+
* Support composite foreign keys via migration helpers.
|
210
135
|
|
211
|
-
|
136
|
+
```ruby
|
137
|
+
# Assuming "carts" table has "(shop_id, user_id)" as a primary key.
|
212
138
|
|
213
|
-
|
139
|
+
add_foreign_key(:orders, :carts, primary_key: [:shop_id, :user_id])
|
214
140
|
|
215
|
-
|
141
|
+
remove_foreign_key(:orders, :carts, primary_key: [:shop_id, :user_id])
|
142
|
+
foreign_key_exists?(:orders, :carts, primary_key: [:shop_id, :user_id])
|
143
|
+
```
|
216
144
|
|
217
145
|
*fatkodima*
|
218
146
|
|
219
|
-
*
|
147
|
+
* Adds support for `if_not_exists` when adding a check constraint.
|
220
148
|
|
221
|
-
|
222
|
-
|
223
|
-
|
149
|
+
```ruby
|
150
|
+
add_check_constraint :posts, "post_type IN ('blog', 'comment', 'share')", if_not_exists: true
|
151
|
+
```
|
224
152
|
|
225
|
-
*
|
153
|
+
*Cody Cutrer*
|
226
154
|
|
227
|
-
*
|
155
|
+
* Raise an `ArgumentError` when `#accepts_nested_attributes_for` is declared more than once for an association in
|
156
|
+
the same class. Previously, the last declaration would silently override the previous one. Overriding in a subclass
|
157
|
+
is still allowed.
|
228
158
|
|
229
159
|
*Joshua Young*
|
230
160
|
|
231
|
-
*
|
232
|
-
|
233
|
-
*fatkodima*
|
234
|
-
|
235
|
-
* Fix Enumerable#in_order_of to preserve duplicates.
|
161
|
+
* Deprecate `rewhere` argument on `#merge`.
|
236
162
|
|
237
|
-
|
163
|
+
The `rewhere` argument on `#merge`is deprecated without replacement and
|
164
|
+
will be removed in Rails 7.2.
|
238
165
|
|
239
|
-
*
|
166
|
+
*Adam Hess*
|
240
167
|
|
241
|
-
|
168
|
+
* Fix unscope is not working in specific case
|
242
169
|
|
243
|
-
|
170
|
+
Before:
|
171
|
+
```ruby
|
172
|
+
Post.where(id: 1...3).unscope(where: :id).to_sql # "SELECT `posts`.* FROM `posts` WHERE `posts`.`id` >= 1 AND `posts`.`id` < 3"
|
244
173
|
|
245
|
-
|
174
|
+
```
|
246
175
|
|
247
|
-
|
176
|
+
After:
|
177
|
+
```ruby
|
178
|
+
Post.where(id: 1...3).unscope(where: :id).to_sql # "SELECT `posts`.* FROM `posts`"
|
179
|
+
```
|
248
180
|
|
249
|
-
|
181
|
+
Fixes #48094.
|
250
182
|
|
251
|
-
*
|
183
|
+
*Kazuya Hatanaka*
|
252
184
|
|
253
|
-
|
185
|
+
* Change `has_secure_token` default to `on: :initialize`
|
254
186
|
|
255
|
-
|
187
|
+
Change the new default value from `on: :create` to `on: :initialize`
|
256
188
|
|
257
|
-
|
189
|
+
Can be controlled by the `config.active_record.generate_secure_token_on`
|
190
|
+
configuration:
|
258
191
|
|
259
|
-
|
192
|
+
```ruby
|
193
|
+
config.active_record.generate_secure_token_on = :create
|
194
|
+
```
|
260
195
|
|
261
|
-
*
|
196
|
+
*Sean Doyle*
|
262
197
|
|
263
|
-
* Fix
|
198
|
+
* Fix `change_column` not setting `precision: 6` on `datetime` columns when
|
199
|
+
using 7.0+ Migrations and SQLite.
|
264
200
|
|
265
|
-
|
266
|
-
default precision as regular datetime columns, resulting in the following
|
267
|
-
being erroneously equivalent:
|
201
|
+
*Hartley McGuire*
|
268
202
|
|
269
|
-
|
270
|
-
t.virtual :name, type: datetime, precision: nil, as: "expression"
|
203
|
+
* Support composite identifiers in `to_key`
|
271
204
|
|
272
|
-
|
273
|
-
datetime column default precisions match.
|
205
|
+
`to_key` avoids wrapping `#id` value into an `Array` if `#id` already an array
|
274
206
|
|
275
|
-
*
|
207
|
+
*Nikita Vasilevsky*
|
276
208
|
|
277
|
-
*
|
209
|
+
* Add validation option for `enum`
|
278
210
|
|
279
|
-
|
211
|
+
```ruby
|
212
|
+
class Contract < ApplicationRecord
|
213
|
+
enum :status, %w[in_progress completed], validate: true
|
214
|
+
end
|
215
|
+
Contract.new(status: "unknown").valid? # => false
|
216
|
+
Contract.new(status: nil).valid? # => false
|
217
|
+
Contract.new(status: "completed").valid? # => true
|
280
218
|
|
219
|
+
class Contract < ApplicationRecord
|
220
|
+
enum :status, %w[in_progress completed], validate: { allow_nil: true }
|
221
|
+
end
|
222
|
+
Contract.new(status: "unknown").valid? # => false
|
223
|
+
Contract.new(status: nil).valid? # => true
|
224
|
+
Contract.new(status: "completed").valid? # => true
|
225
|
+
```
|
281
226
|
|
282
|
-
|
227
|
+
*Edem Topuzov*, *Ryuta Kamizono*
|
283
228
|
|
284
|
-
*
|
229
|
+
* Allow batching methods to use already loaded relation if available
|
285
230
|
|
231
|
+
Calling batch methods on already loaded relations will use the records previously loaded instead of retrieving
|
232
|
+
them from the database again.
|
286
233
|
|
287
|
-
|
234
|
+
*Adam Hess*
|
288
235
|
|
289
|
-
*
|
236
|
+
* Deprecate `read_attribute(:id)` returning the primary key if the primary key is not `:id`.
|
290
237
|
|
238
|
+
Starting in Rails 7.2, `read_attribute(:id)` will return the value of the id column, regardless of the model's
|
239
|
+
primary key. To retrieve the value of the primary key, use `#id` instead. `read_attribute(:id)` for composite
|
240
|
+
primary key models will now return the value of the id column.
|
291
241
|
|
292
|
-
|
242
|
+
*Adrianna Chang*
|
293
243
|
|
294
|
-
*
|
244
|
+
* Fix `change_table` setting datetime precision for 6.1 Migrations
|
295
245
|
|
296
|
-
|
297
|
-
attempting sanitization. That sanitization could be bypassed with
|
298
|
-
carefully crafted input.
|
246
|
+
*Hartley McGuire*
|
299
247
|
|
300
|
-
|
301
|
-
occurrences of "/*" or "*/" with "/ *" or "* /". It also performs a
|
302
|
-
first pass to remove one surrounding comment to avoid compatibility
|
303
|
-
issues for users relying on the existing removal.
|
248
|
+
* Fix change_column setting datetime precision for 6.1 Migrations
|
304
249
|
|
305
|
-
|
306
|
-
be provided user input.
|
250
|
+
*Hartley McGuire*
|
307
251
|
|
308
|
-
|
252
|
+
* Add `ActiveRecord::Base#id_value` alias to access the raw value of a record's id column.
|
309
253
|
|
310
|
-
|
254
|
+
This alias is only provided for models that declare an `:id` column.
|
311
255
|
|
312
|
-
|
313
|
-
PostgreSQL will treat the column type as numeric. Comparing
|
314
|
-
integer values against numeric values can result in a slow
|
315
|
-
sequential scan.
|
256
|
+
*Adrianna Chang*
|
316
257
|
|
317
|
-
|
318
|
-
ActiveRecord::Base.raise_int_wider_than_64bit which defaults to true.
|
258
|
+
* Fix previous change tracking for `ActiveRecord::Store` when using a column with JSON structured database type
|
319
259
|
|
320
|
-
|
260
|
+
Before, the methods to access the changes made during the last save `#saved_change_to_key?`, `#saved_change_to_key`, and `#key_before_last_save` did not work if the store was defined as a `store_accessor` on a column with a JSON structured database type
|
321
261
|
|
262
|
+
*Robert DiMartino*
|
322
263
|
|
323
|
-
|
264
|
+
* Fully support `NULLS [NOT] DISTINCT` for PostgreSQL 15+ indexes.
|
324
265
|
|
325
|
-
|
266
|
+
Previous work was done to allow the index to be created in a migration, but it was not
|
267
|
+
supported in schema.rb. Additionally, the matching for `NULLS [NOT] DISTINCT` was not
|
268
|
+
in the correct order, which could have resulted in inconsistent schema detection.
|
326
269
|
|
327
|
-
|
270
|
+
*Gregory Jones*
|
328
271
|
|
329
|
-
*
|
272
|
+
* Allow escaping of literal colon characters in `sanitize_sql_*` methods when named bind variables are used
|
330
273
|
|
331
|
-
|
332
|
-
which is wasteful and cause problem with YAML safe_load.
|
274
|
+
*Justin Bull*
|
333
275
|
|
334
|
-
|
276
|
+
* Fix `#previously_new_record?` to return true for destroyed records.
|
335
277
|
|
336
|
-
|
278
|
+
Before, if a record was created and then destroyed, `#previously_new_record?` would return true.
|
279
|
+
Now, any UPDATE or DELETE to a record is considered a change, and will result in `#previously_new_record?`
|
280
|
+
returning false.
|
337
281
|
|
338
|
-
|
282
|
+
*Adrianna Chang*
|
339
283
|
|
340
|
-
|
284
|
+
* Specify callback in `has_secure_token`
|
341
285
|
|
342
286
|
```ruby
|
343
|
-
|
344
|
-
|
345
|
-
|
346
|
-
*Alex Ghiculescu*
|
347
|
-
|
348
|
-
* Fix supporting timezone awareness for `tsrange` and `tstzrange` array columns.
|
287
|
+
class User < ApplicationRecord
|
288
|
+
has_secure_token on: :initialize
|
289
|
+
end
|
349
290
|
|
350
|
-
|
351
|
-
# In database migrations
|
352
|
-
add_column :shops, :open_hours, :tsrange, array: true
|
353
|
-
# In app config
|
354
|
-
ActiveRecord::Base.time_zone_aware_types += [:tsrange]
|
355
|
-
# In the code times are properly converted to app time zone
|
356
|
-
Shop.create!(open_hours: [Time.current..8.hour.from_now])
|
291
|
+
User.new.token # => "abc123...."
|
357
292
|
```
|
358
293
|
|
359
|
-
*
|
294
|
+
*Sean Doyle*
|
360
295
|
|
361
|
-
*
|
296
|
+
* Fix incrementation of in memory counter caches when associations overlap
|
362
297
|
|
363
|
-
|
364
|
-
|
365
|
-
still reported a stale cache_version.
|
298
|
+
When two associations had a similarly named counter cache column, Active Record
|
299
|
+
could sometime increment the wrong one.
|
366
300
|
|
367
|
-
|
301
|
+
*Jacopo Beschi*, *Jean Boussier*
|
368
302
|
|
369
|
-
|
370
|
-
developers = Developer.all
|
371
|
-
developers.cache_version
|
303
|
+
* Don't show secrets for Active Record's `Cipher::Aes256Gcm#inspect`.
|
372
304
|
|
373
|
-
|
305
|
+
Before:
|
374
306
|
|
375
|
-
|
376
|
-
|
377
|
-
|
307
|
+
```ruby
|
308
|
+
ActiveRecord::Encryption::Cipher::Aes256Gcm.new(secret).inspect
|
309
|
+
"#<ActiveRecord::Encryption::Cipher::Aes256Gcm:0x0000000104888038 ... @secret=\"\\xAF\\bFh]LV}q\\nl\\xB2U\\xB3 ... >"
|
378
310
|
```
|
379
311
|
|
380
|
-
|
312
|
+
After:
|
381
313
|
|
382
|
-
|
314
|
+
```ruby
|
315
|
+
ActiveRecord::Encryption::Cipher::Aes256Gcm(secret).inspect
|
316
|
+
"#<ActiveRecord::Encryption::Cipher::Aes256Gcm:0x0000000104888038>"
|
317
|
+
```
|
383
318
|
|
384
|
-
*
|
319
|
+
*Petrik de Heus*
|
385
320
|
|
386
|
-
|
387
|
-
a query but never use it.
|
321
|
+
* Bring back the historical behavior of committing transaction on non-local return.
|
388
322
|
|
389
323
|
```ruby
|
390
|
-
|
391
|
-
|
324
|
+
Model.transaction do
|
325
|
+
model.save
|
326
|
+
return
|
327
|
+
other_model.save # not executed
|
328
|
+
end
|
392
329
|
```
|
393
330
|
|
394
|
-
|
395
|
-
|
331
|
+
Historically only raised errors would trigger a rollback, but in Ruby `2.3`, the `timeout` library
|
332
|
+
started using `throw` to interrupt execution which had the adverse effect of committing open transactions.
|
396
333
|
|
397
|
-
|
398
|
-
|
399
|
-
* Fix eager loading for models without primary keys.
|
334
|
+
To solve this, in Active Record 6.1 the behavior was changed to instead rollback the transaction as it was safer
|
335
|
+
than to potentially commit an incomplete transaction.
|
400
336
|
|
401
|
-
|
337
|
+
Using `return`, `break` or `throw` inside a `transaction` block was essentially deprecated from Rails 6.1 onwards.
|
402
338
|
|
403
|
-
|
339
|
+
However with the release of `timeout 0.4.0`, `Timeout.timeout` now raises an error again, and Active Record is able
|
340
|
+
to return to its original, less surprising, behavior.
|
404
341
|
|
405
|
-
|
406
|
-
way to dump a schema to both SQL and Ruby formats. You can now do this with
|
407
|
-
an environment variable. For example:
|
342
|
+
This historical behavior can now be opt-ed in via:
|
408
343
|
|
409
344
|
```
|
410
|
-
|
345
|
+
Rails.application.config.active_record.commit_transaction_on_non_local_return = true
|
411
346
|
```
|
412
347
|
|
413
|
-
|
414
|
-
|
415
|
-
* Fix Hstore deserialize regression.
|
416
|
-
|
417
|
-
*edsharp*
|
418
|
-
|
348
|
+
And is the default for new applications created in Rails 7.1.
|
419
349
|
|
420
|
-
|
421
|
-
|
422
|
-
* Change ActiveRecord::Coders::YAMLColumn default to safe_load
|
423
|
-
|
424
|
-
This adds two new configuration options The configuration options are as
|
425
|
-
follows:
|
426
|
-
|
427
|
-
* `config.active_record.use_yaml_unsafe_load`
|
350
|
+
*Jean Boussier*
|
428
351
|
|
429
|
-
|
430
|
-
"unsafe" YAML loading strategy, maintaining the existing behavior but leaving
|
431
|
-
the possible escalation vulnerability in place. Setting this option to true
|
432
|
-
is *not* recommended, but can aid in upgrading.
|
352
|
+
* Deprecate `name` argument on `#remove_connection`.
|
433
353
|
|
434
|
-
|
354
|
+
The `name` argument is deprecated on `#remove_connection` without replacement. `#remove_connection` should be called directly on the class that established the connection.
|
435
355
|
|
436
|
-
|
437
|
-
by default. This option allows you to specify classes deemed "safe" in your
|
438
|
-
application. For example, if your application uses Symbol and Time in
|
439
|
-
serialized data, you can add Symbol and Time to the allowed list as follows:
|
356
|
+
*Eileen M. Uchitelle*
|
440
357
|
|
441
|
-
|
442
|
-
config.active_record.yaml_column_permitted_classes = [Symbol, Date, Time]
|
443
|
-
```
|
358
|
+
* Fix has_one through singular building with inverse.
|
444
359
|
|
445
|
-
|
360
|
+
Allows building of records from an association with a has_one through a
|
361
|
+
singular association with inverse. For belongs_to through associations,
|
362
|
+
linking the foreign key to the primary key model isn't needed.
|
363
|
+
For has_one, we cannot build records due to the association not being mutable.
|
446
364
|
|
365
|
+
*Gannon McGibbon*
|
447
366
|
|
448
|
-
|
367
|
+
* Disable database prepared statements when query logs are enabled
|
449
368
|
|
450
|
-
|
451
|
-
methods in class objects that referenced reloadable constants. See
|
452
|
-
[#44125](https://github.com/rails/rails/issues/44125) for details.
|
369
|
+
Prepared Statements and Query Logs are incompatible features due to query logs making every query unique.
|
453
370
|
|
454
|
-
*
|
371
|
+
*zzak, Jean Boussier*
|
455
372
|
|
456
|
-
*
|
373
|
+
* Support decrypting data encrypted non-deterministically with a SHA1 hash digest.
|
457
374
|
|
458
|
-
|
459
|
-
|
460
|
-
added as string content when saving new records.
|
375
|
+
This adds a new Active Record encryption option to support decrypting data encrypted
|
376
|
+
non-deterministically with a SHA1 hash digest:
|
461
377
|
|
462
|
-
|
378
|
+
```
|
379
|
+
Rails.application.config.active_record.encryption.support_sha1_for_non_deterministic_encryption = true
|
380
|
+
```
|
463
381
|
|
464
|
-
|
382
|
+
The new option addresses a problem when upgrading from 7.0 to 7.1. Due to a bug in how Active Record
|
383
|
+
Encryption was getting initialized, the key provider used for non-deterministic encryption were using
|
384
|
+
SHA-1 as its digest class, instead of the one configured globally by Rails via
|
385
|
+
`Rails.application.config.active_support.key_generator_hash_digest_class`.
|
465
386
|
|
466
|
-
*
|
387
|
+
*Cadu Ribeiro and Jorge Manrubia*
|
467
388
|
|
468
|
-
*
|
389
|
+
* Added PostgreSQL migration commands for enum rename, add value, and rename value.
|
469
390
|
|
470
|
-
|
471
|
-
|
391
|
+
`rename_enum` and `rename_enum_value` are reversible. Due to Postgres
|
392
|
+
limitation, `add_enum_value` is not reversible since you cannot delete enum
|
393
|
+
values. As an alternative you should drop and recreate the enum entirely.
|
472
394
|
|
473
395
|
```ruby
|
474
|
-
|
396
|
+
rename_enum :article_status, to: :article_state
|
475
397
|
```
|
476
398
|
|
477
|
-
|
399
|
+
```ruby
|
400
|
+
add_enum_value :article_state, "archived" # will be at the end of existing values
|
401
|
+
add_enum_value :article_state, "in review", before: "published"
|
402
|
+
add_enum_value :article_state, "approved", after: "in review"
|
403
|
+
```
|
478
404
|
|
479
|
-
|
405
|
+
```ruby
|
406
|
+
rename_enum_value :article_state, from: "archived", to: "deleted"
|
407
|
+
```
|
480
408
|
|
481
|
-
|
482
|
-
parameter, instead of just `name`. This prevents unintended filtering of parameters
|
483
|
-
with a matching name in other models.
|
409
|
+
*Ray Faddis*
|
484
410
|
|
485
|
-
|
411
|
+
* Allow composite primary key to be derived from schema
|
486
412
|
|
487
|
-
|
413
|
+
Booting an application with a schema that contains composite primary keys
|
414
|
+
will not issue warning and won't `nil`ify the `ActiveRecord::Base#primary_key` value anymore.
|
488
415
|
|
489
|
-
|
416
|
+
Given a `travel_routes` table definition and a `TravelRoute` model like:
|
417
|
+
```ruby
|
418
|
+
create_table :travel_routes, primary_key: [:origin, :destination], force: true do |t|
|
419
|
+
t.string :origin
|
420
|
+
t.string :destination
|
421
|
+
end
|
490
422
|
|
491
|
-
|
423
|
+
class TravelRoute < ActiveRecord::Base; end
|
424
|
+
```
|
425
|
+
The `TravelRoute.primary_key` value will be automatically derived to `["origin", "destination"]`
|
492
426
|
|
493
|
-
*
|
427
|
+
*Nikita Vasilevsky*
|
494
428
|
|
495
|
-
|
429
|
+
* Include the `connection_pool` with exceptions raised from an adapter.
|
496
430
|
|
497
|
-
|
431
|
+
The `connection_pool` provides added context such as the connection used
|
432
|
+
that led to the exception as well as which role and shard.
|
498
433
|
|
434
|
+
*Luan Vieira*
|
499
435
|
|
500
|
-
|
436
|
+
* Support multiple column ordering for `find_each`, `find_in_batches` and `in_batches`.
|
501
437
|
|
502
|
-
|
438
|
+
When find_each/find_in_batches/in_batches are performed on a table with composite primary keys, ascending or descending order can be selected for each key.
|
503
439
|
|
440
|
+
```ruby
|
441
|
+
Person.find_each(order: [:desc, :asc]) do |person|
|
442
|
+
person.party_all_night!
|
443
|
+
end
|
444
|
+
```
|
504
445
|
|
505
|
-
|
446
|
+
*Takuya Kurimoto*
|
506
447
|
|
507
|
-
*
|
448
|
+
* Fix where on association with has_one/has_many polymorphic relations.
|
508
449
|
|
450
|
+
Before:
|
451
|
+
```ruby
|
452
|
+
Treasure.where(price_estimates: PriceEstimate.all)
|
453
|
+
#=> SELECT (...) WHERE "treasures"."id" IN (SELECT "price_estimates"."estimate_of_id" FROM "price_estimates")
|
454
|
+
```
|
509
455
|
|
510
|
-
|
456
|
+
Later:
|
457
|
+
```ruby
|
458
|
+
Treasure.where(price_estimates: PriceEstimate.all)
|
459
|
+
#=> SELECT (...) WHERE "treasures"."id" IN (SELECT "price_estimates"."estimate_of_id" FROM "price_estimates" WHERE "price_estimates"."estimate_of_type" = 'Treasure')
|
460
|
+
```
|
511
461
|
|
512
|
-
*
|
462
|
+
*Lázaro Nixon*
|
513
463
|
|
464
|
+
* Assign auto populated columns on Active Record record creation.
|
514
465
|
|
515
|
-
|
466
|
+
Changes record creation logic to allow for the `auto_increment` column to be assigned
|
467
|
+
immediately after creation regardless of it's relation to the model's primary key.
|
516
468
|
|
517
|
-
|
469
|
+
The PostgreSQL adapter benefits the most from the change allowing for any number of auto-populated
|
470
|
+
columns to be assigned on the object immediately after row insertion utilizing the `RETURNING` statement.
|
518
471
|
|
519
472
|
*Nikita Vasilevsky*
|
520
473
|
|
521
|
-
*
|
474
|
+
* Use the first key in the `shards` hash from `connected_to` for the `default_shard`.
|
522
475
|
|
523
|
-
|
476
|
+
Some applications may not want to use `:default` as a shard name in their connection model. Unfortunately Active Record expects there to be a `:default` shard because it must assume a shard to get the right connection from the pool manager. Rather than force applications to manually set this, `connects_to` can infer the default shard name from the hash of shards and will now assume that the first shard is your default.
|
524
477
|
|
525
|
-
|
478
|
+
For example if your model looked like this:
|
526
479
|
|
527
|
-
|
528
|
-
|
529
|
-
|
530
|
-
|
531
|
-
*Nikita Vasilevsky*
|
532
|
-
|
533
|
-
* Dump the database schema containing the current Rails version.
|
534
|
-
|
535
|
-
Since https://github.com/rails/rails/pull/42297, Rails now generate datetime columns
|
536
|
-
with a default precision of 6. This means that users upgrading to Rails 7.0 from 6.1,
|
537
|
-
when loading the database schema, would get the new precision value, which would not match
|
538
|
-
the production schema.
|
539
|
-
|
540
|
-
To avoid this the schema dumper will generate the new format which will include the Rails
|
541
|
-
version and will look like this:
|
480
|
+
```ruby
|
481
|
+
class ShardRecord < ApplicationRecord
|
482
|
+
self.abstract_class = true
|
542
483
|
|
484
|
+
connects_to shards: {
|
485
|
+
shard_one: { writing: :shard_one },
|
486
|
+
shard_two: { writing: :shard_two }
|
487
|
+
}
|
543
488
|
```
|
544
|
-
ActiveRecord::Schema[7.0].define
|
545
|
-
```
|
546
|
-
|
547
|
-
When upgrading from Rails 6.1 to Rails 7.0, you can run the `rails app:update` task that will
|
548
|
-
set the current schema version to 6.1.
|
549
|
-
|
550
|
-
*Rafael Mendonça França*
|
551
489
|
|
552
|
-
|
490
|
+
Then the `default_shard` for this class would be set to `shard_one`.
|
553
491
|
|
554
|
-
|
492
|
+
Fixes: #45390
|
555
493
|
|
556
|
-
*
|
557
|
-
when bulk-inserting fixtures that exceed `max_allowed_packet` configuration.
|
494
|
+
*Eileen M. Uchitelle*
|
558
495
|
|
559
|
-
|
496
|
+
* Fix mutation detection for serialized attributes backed by binary columns.
|
560
497
|
|
561
|
-
*
|
498
|
+
*Jean Boussier*
|
562
499
|
|
563
|
-
|
500
|
+
* Add `ActiveRecord.disconnect_all!` method to immediately close all connections from all pools.
|
564
501
|
|
565
|
-
*
|
502
|
+
*Jean Boussier*
|
566
503
|
|
567
|
-
|
504
|
+
* Discard connections which may have been left in a transaction.
|
568
505
|
|
569
|
-
|
506
|
+
There are cases where, due to an error, `within_new_transaction` may unexpectedly leave a connection in an open transaction. In these cases the connection may be reused, and the following may occur:
|
507
|
+
- Writes appear to fail when they actually succeed.
|
508
|
+
- Writes appear to succeed when they actually fail.
|
509
|
+
- Reads return stale or uncommitted data.
|
570
510
|
|
571
|
-
|
511
|
+
Previously, the following case was detected:
|
512
|
+
- An error is encountered during the transaction, then another error is encountered while attempting to roll it back.
|
572
513
|
|
573
|
-
|
514
|
+
Now, the following additional cases are detected:
|
515
|
+
- An error is encountered just after successfully beginning a transaction.
|
516
|
+
- An error is encountered while committing a transaction, then another error is encountered while attempting to roll it back.
|
517
|
+
- An error is encountered while rolling back a transaction.
|
574
518
|
|
575
|
-
|
519
|
+
*Nick Dower*
|
576
520
|
|
577
|
-
|
521
|
+
* Active Record query cache now evicts least recently used entries
|
578
522
|
|
579
|
-
|
523
|
+
By default it only keeps the `100` most recently used queries.
|
580
524
|
|
581
|
-
|
525
|
+
The cache size can be configured via `database.yml`
|
582
526
|
|
527
|
+
```yaml
|
528
|
+
development:
|
529
|
+
adapter: mysql2
|
530
|
+
query_cache: 200
|
531
|
+
```
|
583
532
|
|
584
|
-
|
533
|
+
It can also be entirely disabled:
|
585
534
|
|
535
|
+
```yaml
|
536
|
+
development:
|
537
|
+
adapter: mysql2
|
538
|
+
query_cache: false
|
539
|
+
```
|
586
540
|
|
587
|
-
*
|
541
|
+
*Jean Boussier*
|
588
542
|
|
589
|
-
|
543
|
+
* Deprecate `check_pending!` in favor of `check_all_pending!`.
|
590
544
|
|
591
|
-
|
545
|
+
`check_pending!` will only check for pending migrations on the current database connection or the one passed in. This has been deprecated in favor of `check_all_pending!` which will find all pending migrations for the database configurations in a given environment.
|
592
546
|
|
593
|
-
*
|
547
|
+
*Eileen M. Uchitelle*
|
594
548
|
|
595
|
-
|
549
|
+
* Make `increment_counter`/`decrement_counter` accept an amount argument
|
596
550
|
|
597
551
|
```ruby
|
598
|
-
|
552
|
+
Post.increment_counter(:comments_count, 5, by: 3)
|
599
553
|
```
|
600
554
|
|
601
|
-
|
602
|
-
|
603
|
-
*Oliver Günther*
|
555
|
+
*fatkodima*
|
604
556
|
|
605
|
-
*
|
557
|
+
* Add support for `Array#intersect?` to `ActiveRecord::Relation`.
|
606
558
|
|
607
|
-
|
559
|
+
`Array#intersect?` is only available on Ruby 3.1 or later.
|
608
560
|
|
609
|
-
|
561
|
+
This allows the Rubocop `Style/ArrayIntersect` cop to work with `ActiveRecord::Relation` objects.
|
610
562
|
|
611
|
-
*
|
563
|
+
*John Harry Kelly*
|
612
564
|
|
613
|
-
*
|
565
|
+
* The deferrable foreign key can be passed to `t.references`.
|
614
566
|
|
615
|
-
*
|
567
|
+
*Hiroyuki Ishii*
|
616
568
|
|
617
|
-
*
|
569
|
+
* Deprecate `deferrable: true` option of `add_foreign_key`.
|
618
570
|
|
619
|
-
|
571
|
+
`deferrable: true` is deprecated in favor of `deferrable: :immediate`, and
|
572
|
+
will be removed in Rails 7.2.
|
620
573
|
|
621
|
-
|
574
|
+
Because `deferrable: true` and `deferrable: :deferred` are hard to understand.
|
575
|
+
Both true and :deferred are truthy values.
|
576
|
+
This behavior is the same as the deferrable option of the add_unique_key method, added in #46192.
|
622
577
|
|
623
|
-
*
|
578
|
+
*Hiroyuki Ishii*
|
624
579
|
|
625
|
-
|
580
|
+
* `AbstractAdapter#execute` and `#exec_query` now clear the query cache
|
626
581
|
|
627
|
-
|
582
|
+
If you need to perform a read only SQL query without clearing the query
|
583
|
+
cache, use `AbstractAdapter#select_all`.
|
628
584
|
|
629
|
-
*
|
585
|
+
*Jean Boussier*
|
630
586
|
|
631
|
-
*
|
587
|
+
* Make `.joins` / `.left_outer_joins` work with CTEs.
|
632
588
|
|
633
|
-
|
589
|
+
For example:
|
634
590
|
|
635
|
-
|
591
|
+
```ruby
|
592
|
+
Post
|
593
|
+
.with(commented_posts: Comment.select(:post_id).distinct)
|
594
|
+
.joins(:commented_posts)
|
595
|
+
#=> WITH (...) SELECT ... INNER JOIN commented_posts on posts.id = commented_posts.post_id
|
596
|
+
```
|
636
597
|
|
637
|
-
|
638
|
-
bigint instead of integer for the SQLite Adapter.
|
598
|
+
*Vladimir Dementyev*
|
639
599
|
|
640
|
-
|
600
|
+
* Add a load hook for `ActiveRecord::ConnectionAdapters::Mysql2Adapter`
|
601
|
+
(named `active_record_mysql2adapter`) to allow for overriding aspects of the
|
602
|
+
`ActiveRecord::ConnectionAdapters::Mysql2Adapter` class. This makes `Mysql2Adapter`
|
603
|
+
consistent with `PostgreSQLAdapter` and `SQLite3Adapter` that already have load hooks.
|
641
604
|
|
642
|
-
*
|
605
|
+
*fatkodima*
|
643
606
|
|
644
|
-
|
607
|
+
* Introduce adapter for Trilogy database client
|
645
608
|
|
646
|
-
|
609
|
+
Trilogy is a MySQL-compatible database client. Rails applications can use Trilogy
|
610
|
+
by configuring their `config/database.yml`:
|
647
611
|
|
648
|
-
```
|
649
|
-
|
612
|
+
```yaml
|
613
|
+
development:
|
614
|
+
adapter: trilogy
|
615
|
+
database: blog_development
|
616
|
+
pool: 5
|
650
617
|
```
|
651
618
|
|
652
|
-
|
653
|
-
value is still ordered.
|
654
|
-
|
655
|
-
*Jean Boussier*
|
656
|
-
|
657
|
-
* Fix `rails dbconsole` for 3-tier config.
|
619
|
+
Or by using the `DATABASE_URL` environment variable:
|
658
620
|
|
659
|
-
|
621
|
+
```ruby
|
622
|
+
ENV['DATABASE_URL'] # => "trilogy://localhost/blog_development?pool=5"
|
623
|
+
```
|
660
624
|
|
661
|
-
*
|
625
|
+
*Adrianna Chang*
|
662
626
|
|
663
|
-
|
664
|
-
is a valid identifier.
|
627
|
+
* `after_commit` callbacks defined on models now execute in the correct order.
|
665
628
|
|
666
629
|
```ruby
|
667
|
-
class
|
668
|
-
|
630
|
+
class User < ActiveRecord::Base
|
631
|
+
after_commit { puts("this gets called first") }
|
632
|
+
after_commit { puts("this gets called second") }
|
669
633
|
end
|
670
|
-
Test.group(:id).count
|
671
|
-
# syntax error at or near "1" (ActiveRecord::StatementInvalid)
|
672
|
-
# LINE 1: SELECT COUNT(*) AS count_all, "1abc"."id" AS 1abc_id FROM "1...
|
673
634
|
```
|
674
635
|
|
675
|
-
|
636
|
+
Previously, the callbacks executed in the reverse order. To opt in to the new behaviour:
|
637
|
+
|
638
|
+
```ruby
|
639
|
+
config.active_record.run_after_transaction_callbacks_in_order_defined = true
|
640
|
+
```
|
676
641
|
|
642
|
+
This is the default for new apps.
|
677
643
|
|
678
|
-
|
644
|
+
*Alex Ghiculescu*
|
679
645
|
|
680
|
-
*
|
646
|
+
* Infer `foreign_key` when `inverse_of` is present on `has_one` and `has_many` associations.
|
681
647
|
|
682
648
|
```ruby
|
683
|
-
|
649
|
+
has_many :citations, foreign_key: "book1_id", inverse_of: :book
|
684
650
|
```
|
685
651
|
|
686
|
-
|
687
|
-
responsible to detect write queries.
|
652
|
+
can be simplified to
|
688
653
|
|
689
|
-
|
690
|
-
|
691
|
-
|
692
|
-
*Jean Boussier*
|
654
|
+
```ruby
|
655
|
+
has_many :citations, inverse_of: :book
|
656
|
+
```
|
693
657
|
|
694
|
-
|
658
|
+
and the foreign_key will be read from the corresponding `belongs_to` association.
|
695
659
|
|
696
|
-
|
660
|
+
*Daniel Whitney*
|
697
661
|
|
698
|
-
|
662
|
+
* Limit max length of auto generated index names
|
699
663
|
|
664
|
+
Auto generated index names are now limited to 62 bytes, which fits within
|
665
|
+
the default index name length limits for MySQL, Postgres and SQLite.
|
700
666
|
|
701
|
-
|
667
|
+
Any index name over the limit will fallback to the new short format.
|
702
668
|
|
703
|
-
|
669
|
+
Before (too long):
|
670
|
+
```
|
671
|
+
index_testings_on_foo_and_bar_and_first_name_and_last_name_and_administrator
|
672
|
+
```
|
704
673
|
|
674
|
+
After (short format):
|
675
|
+
```
|
676
|
+
idx_on_foo_bar_first_name_last_name_administrator_5939248142
|
677
|
+
```
|
705
678
|
|
706
|
-
|
679
|
+
The short format includes a hash to ensure the name is unique database-wide.
|
707
680
|
|
708
|
-
*
|
681
|
+
*Mike Coutermarsh*
|
709
682
|
|
683
|
+
* Introduce a more stable and optimized Marshal serializer for Active Record models.
|
710
684
|
|
711
|
-
|
685
|
+
Can be enabled with `config.active_record.marshalling_format_version = 7.1`.
|
712
686
|
|
713
|
-
*
|
687
|
+
*Jean Boussier*
|
714
688
|
|
715
|
-
|
689
|
+
* Allow specifying where clauses with column-tuple syntax.
|
716
690
|
|
717
|
-
|
691
|
+
Querying through `#where` now accepts a new tuple-syntax which accepts, as
|
692
|
+
a key, an array of columns and, as a value, an array of corresponding tuples.
|
693
|
+
The key specifies a list of columns, while the value is an array of
|
694
|
+
ordered-tuples that conform to the column list.
|
718
695
|
|
719
|
-
|
696
|
+
For instance:
|
720
697
|
|
721
|
-
|
698
|
+
```ruby
|
699
|
+
# Cpk::Book => Cpk::Book(author_id: integer, number: integer, title: string, revision: integer)
|
700
|
+
# Cpk::Book.primary_key => ["author_id", "number"]
|
722
701
|
|
723
|
-
|
702
|
+
book = Cpk::Book.create!(author_id: 1, number: 1)
|
703
|
+
Cpk::Book.where(Cpk::Book.primary_key => [[1, 2]]) # => [book]
|
724
704
|
|
725
|
-
|
705
|
+
# Topic => Topic(id: integer, title: string, author_name: string...)
|
726
706
|
|
727
|
-
|
707
|
+
Topic.where([:title, :author_name] => [["The Alchemist", "Paulo Coelho"], ["Harry Potter", "J.K Rowling"]])
|
708
|
+
```
|
728
709
|
|
729
|
-
*
|
710
|
+
*Paarth Madan*
|
730
711
|
|
731
|
-
|
732
|
-
Single Table Inheritance. This affects enums defined in subclasses, previously
|
733
|
-
the value of these fields was not parsed and remained `nil`
|
712
|
+
* Allow warning codes to be ignore when reporting SQL warnings.
|
734
713
|
|
735
|
-
|
714
|
+
Active Record config that can ignore warning codes
|
736
715
|
|
737
|
-
|
716
|
+
```ruby
|
717
|
+
# Configure allowlist of warnings that should always be ignored
|
718
|
+
config.active_record.db_warnings_ignore = [
|
719
|
+
"1062", # MySQL Error 1062: Duplicate entry
|
720
|
+
]
|
721
|
+
```
|
738
722
|
|
739
|
-
|
723
|
+
This is supported for the MySQL and PostgreSQL adapters.
|
740
724
|
|
741
|
-
*
|
725
|
+
*Nick Borromeo*
|
742
726
|
|
743
|
-
|
727
|
+
* Introduce `:active_record_fixtures` lazy load hook.
|
744
728
|
|
745
|
-
|
729
|
+
Hooks defined with this name will be run whenever `TestFixtures` is included
|
730
|
+
in a class.
|
746
731
|
|
747
732
|
```ruby
|
748
|
-
|
749
|
-
|
733
|
+
ActiveSupport.on_load(:active_record_fixtures) do
|
734
|
+
self.fixture_paths << "test/fixtures"
|
750
735
|
end
|
751
736
|
|
752
|
-
|
753
|
-
|
754
|
-
|
755
|
-
*Alexandre Ruban*
|
737
|
+
klass = Class.new
|
738
|
+
klass.include(ActiveRecord::TestFixtures)
|
756
739
|
|
757
|
-
|
740
|
+
klass.fixture_paths # => ["test/fixtures"]
|
741
|
+
```
|
758
742
|
|
759
|
-
*
|
743
|
+
*Andrew Novoselac*
|
760
744
|
|
761
|
-
*
|
745
|
+
* Introduce `TestFixtures#fixture_paths`.
|
762
746
|
|
763
|
-
|
747
|
+
Multiple fixture paths can now be specified using the `#fixture_paths` accessor.
|
748
|
+
Apps will continue to have `test/fixtures` as their one fixture path by default,
|
749
|
+
but additional fixture paths can be specified.
|
764
750
|
|
765
751
|
```ruby
|
766
|
-
|
767
|
-
|
768
|
-
{ id: 2, name: "Copper", price: 4.84 },
|
769
|
-
{ id: 4, name: "Gold", price: 1380.87 },
|
770
|
-
{ id: 6, name: "Aluminium", price: 0.35 }
|
771
|
-
],
|
772
|
-
update_only: [:price] # Only prices will be updated
|
773
|
-
)
|
752
|
+
ActiveSupport::TestCase.fixture_paths << "component1/test/fixtures"
|
753
|
+
ActiveSupport::TestCase.fixture_paths << "component2/test/fixtures"
|
774
754
|
```
|
775
755
|
|
776
|
-
|
777
|
-
|
778
|
-
* Remove deprecated `ActiveRecord::Result#map!` and `ActiveRecord::Result#collect!`.
|
756
|
+
`TestFixtures#fixture_path` is now deprecated.
|
779
757
|
|
780
|
-
*
|
758
|
+
*Andrew Novoselac*
|
781
759
|
|
782
|
-
*
|
760
|
+
* Adds support for deferrable exclude constraints in PostgreSQL.
|
783
761
|
|
784
|
-
|
762
|
+
By default, exclude constraints in PostgreSQL are checked after each statement.
|
763
|
+
This works for most use cases, but becomes a major limitation when replacing
|
764
|
+
records with overlapping ranges by using multiple statements.
|
785
765
|
|
786
|
-
|
766
|
+
```ruby
|
767
|
+
exclusion_constraint :users, "daterange(valid_from, valid_to) WITH &&", deferrable: :immediate
|
768
|
+
```
|
787
769
|
|
788
|
-
|
770
|
+
Passing `deferrable: :immediate` checks constraint after each statement,
|
771
|
+
but allows manually deferring the check using `SET CONSTRAINTS ALL DEFERRED`
|
772
|
+
within a transaction. This will cause the excludes to be checked after the transaction.
|
789
773
|
|
790
|
-
|
774
|
+
It's also possible to change the default behavior from an immediate check
|
775
|
+
(after the statement), to a deferred check (after the transaction):
|
791
776
|
|
792
|
-
|
777
|
+
```ruby
|
778
|
+
exclusion_constraint :users, "daterange(valid_from, valid_to) WITH &&", deferrable: :deferred
|
779
|
+
```
|
793
780
|
|
794
|
-
*
|
781
|
+
*Hiroyuki Ishii*
|
795
782
|
|
796
|
-
|
783
|
+
* Respect `foreign_type` option to `delegated_type` for `{role}_class` method.
|
797
784
|
|
798
|
-
|
785
|
+
Usage of `delegated_type` with non-conventional `{role}_type` column names can now be specified with `foreign_type` option.
|
786
|
+
This option is the same as `foreign_type` as forwarded to the underlying `belongs_to` association that `delegated_type` wraps.
|
799
787
|
|
800
|
-
|
788
|
+
*Jason Karns*
|
801
789
|
|
802
|
-
|
790
|
+
* Add support for unique constraints (PostgreSQL-only).
|
803
791
|
|
792
|
+
```ruby
|
793
|
+
add_unique_key :sections, [:position], deferrable: :deferred, name: "unique_section_position"
|
794
|
+
remove_unique_key :sections, name: "unique_section_position"
|
804
795
|
```
|
805
|
-
# Before:
|
806
|
-
Foo Load (0.2ms) SELECT "foos".* FROM "foos" WHERE "foos"."passw" = ? LIMIT ? [["passw", "hello"], ["LIMIT", 1]]
|
807
796
|
|
808
|
-
#
|
809
|
-
|
797
|
+
See PostgreSQL's [Unique Constraints](https://www.postgresql.org/docs/current/ddl-constraints.html#DDL-CONSTRAINTS-UNIQUE-CONSTRAINTS) documentation for more on unique constraints.
|
798
|
+
|
799
|
+
By default, unique constraints in PostgreSQL are checked after each statement.
|
800
|
+
This works for most use cases, but becomes a major limitation when replacing
|
801
|
+
records with unique column by using multiple statements.
|
802
|
+
|
803
|
+
An example of swapping unique columns between records.
|
804
|
+
|
805
|
+
```ruby
|
806
|
+
# position is unique column
|
807
|
+
old_item = Item.create!(position: 1)
|
808
|
+
new_item = Item.create!(position: 2)
|
809
|
+
|
810
|
+
Item.transaction do
|
811
|
+
old_item.update!(position: 2)
|
812
|
+
new_item.update!(position: 1)
|
813
|
+
end
|
810
814
|
```
|
811
815
|
|
812
|
-
|
816
|
+
Using the default behavior, the transaction would fail when executing the
|
817
|
+
first `UPDATE` statement.
|
813
818
|
|
814
|
-
|
819
|
+
By passing the `:deferrable` option to the `add_unique_key` statement in
|
820
|
+
migrations, it's possible to defer this check.
|
815
821
|
|
816
|
-
|
822
|
+
```ruby
|
823
|
+
add_unique_key :items, [:position], deferrable: :immediate
|
824
|
+
```
|
817
825
|
|
818
|
-
|
826
|
+
Passing `deferrable: :immediate` does not change the behaviour of the previous example,
|
827
|
+
but allows manually deferring the check using `SET CONSTRAINTS ALL DEFERRED` within a transaction.
|
828
|
+
This will cause the unique constraints to be checked after the transaction.
|
819
829
|
|
820
|
-
|
830
|
+
It's also possible to adjust the default behavior from an immediate
|
831
|
+
check (after the statement), to a deferred check (after the transaction):
|
821
832
|
|
822
|
-
|
833
|
+
```ruby
|
834
|
+
add_unique_key :items, [:position], deferrable: :deferred
|
835
|
+
```
|
823
836
|
|
824
|
-
|
837
|
+
If you want to change an existing unique index to deferrable, you can use :using_index
|
838
|
+
to create deferrable unique constraints.
|
825
839
|
|
826
|
-
|
840
|
+
```ruby
|
841
|
+
add_unique_key :items, deferrable: :deferred, using_index: "index_items_on_position"
|
842
|
+
```
|
827
843
|
|
828
|
-
*
|
844
|
+
*Hiroyuki Ishii*
|
829
845
|
|
830
|
-
* Remove deprecated `Tasks::DatabaseTasks.
|
846
|
+
* Remove deprecated `Tasks::DatabaseTasks.schema_file_type`.
|
831
847
|
|
832
848
|
*Rafael Mendonça França*
|
833
849
|
|
834
|
-
* Remove deprecated `
|
850
|
+
* Remove deprecated `config.active_record.partial_writes`.
|
835
851
|
|
836
852
|
*Rafael Mendonça França*
|
837
853
|
|
838
|
-
*
|
839
|
-
and will be consistently replaced by the latter condition.
|
840
|
-
|
841
|
-
```ruby
|
842
|
-
# Rails 6.1 (IN clause is replaced by merger side equality condition)
|
843
|
-
Author.where(id: [david.id, mary.id]).merge(Author.where(id: bob)) # => [bob]
|
844
|
-
# Rails 6.1 (both conflict conditions exists, deprecated)
|
845
|
-
Author.where(id: david.id..mary.id).merge(Author.where(id: bob)) # => []
|
846
|
-
# Rails 6.1 with rewhere to migrate to Rails 7.0's behavior
|
847
|
-
Author.where(id: david.id..mary.id).merge(Author.where(id: bob), rewhere: true) # => [bob]
|
848
|
-
# Rails 7.0 (same behavior with IN clause, mergee side condition is consistently replaced)
|
849
|
-
Author.where(id: [david.id, mary.id]).merge(Author.where(id: bob)) # => [bob]
|
850
|
-
Author.where(id: david.id..mary.id).merge(Author.where(id: bob)) # => [bob]
|
854
|
+
* Remove deprecated `ActiveRecord::Base` config accessors.
|
851
855
|
|
852
856
|
*Rafael Mendonça França*
|
853
857
|
|
854
|
-
* Remove
|
858
|
+
* Remove the `:include_replicas` argument from `configs_for`. Use `:include_hidden` argument instead.
|
855
859
|
|
856
|
-
*
|
860
|
+
*Eileen M. Uchitelle*
|
857
861
|
|
858
|
-
*
|
862
|
+
* Allow applications to lookup a config via a custom hash key.
|
859
863
|
|
860
|
-
|
861
|
-
* `db:structure:dump`
|
862
|
-
* `db:structure:load`
|
863
|
-
* `db:structure:load_if_sql`
|
864
|
-
* `db:structure:dump:#{name}`
|
865
|
-
* `db:structure:load:#{name}`
|
866
|
-
* `db:test:load_structure`
|
867
|
-
* `db:test:load_structure:#{name}`
|
864
|
+
If you have registered a custom config or want to find configs where the hash matches a specific key, now you can pass `config_key` to `configs_for`. For example if you have a `db_config` with the key `vitess` you can look up a database configuration hash by matching that key.
|
868
865
|
|
869
|
-
|
866
|
+
```ruby
|
867
|
+
ActiveRecord::Base.configurations.configs_for(env_name: "development", name: "primary", config_key: :vitess)
|
868
|
+
ActiveRecord::Base.configurations.configs_for(env_name: "development", config_key: :vitess)
|
869
|
+
```
|
870
870
|
|
871
|
-
*
|
871
|
+
*Eileen M. Uchitelle*
|
872
872
|
|
873
|
-
|
873
|
+
* Allow applications to register a custom database configuration handler.
|
874
874
|
|
875
|
-
|
875
|
+
Adds a mechanism for registering a custom handler for cases where you want database configurations to respond to custom methods. This is useful for non-Rails database adapters or tools like Vitess that you may want to configure differently from a standard `HashConfig` or `UrlConfig`.
|
876
876
|
|
877
|
-
|
877
|
+
Given the following database YAML we want the `animals` db to create a `CustomConfig` object instead while the `primary` database will be a `UrlConfig`:
|
878
|
+
|
879
|
+
```yaml
|
880
|
+
development:
|
881
|
+
primary:
|
882
|
+
url: postgres://localhost/primary
|
883
|
+
animals:
|
884
|
+
url: postgres://localhost/animals
|
885
|
+
custom_config:
|
886
|
+
sharded: 1
|
887
|
+
```
|
878
888
|
|
879
|
-
|
880
|
-
to be committed, so in order to avoid this mistake, the transaction block is rolled back.
|
889
|
+
To register a custom handler first make a class that has your custom methods:
|
881
890
|
|
882
|
-
|
891
|
+
```ruby
|
892
|
+
class CustomConfig < ActiveRecord::DatabaseConfigurations::UrlConfig
|
893
|
+
def sharded?
|
894
|
+
custom_config.fetch("sharded", false)
|
895
|
+
end
|
883
896
|
|
884
|
-
|
897
|
+
private
|
898
|
+
def custom_config
|
899
|
+
configuration_hash.fetch(:custom_config)
|
900
|
+
end
|
901
|
+
end
|
902
|
+
```
|
885
903
|
|
886
|
-
|
904
|
+
Then register the config in an initializer:
|
887
905
|
|
888
906
|
```ruby
|
889
|
-
|
890
|
-
|
891
|
-
|
892
|
-
|
893
|
-
}
|
907
|
+
ActiveRecord::DatabaseConfigurations.register_db_config_handler do |env_name, name, url, config|
|
908
|
+
next unless config.key?(:custom_config)
|
909
|
+
CustomConfig.new(env_name, name, url, config)
|
910
|
+
end
|
894
911
|
```
|
895
912
|
|
896
|
-
|
913
|
+
When the application is booted, configuration hashes with the `:custom_config` key will be `CustomConfig` objects and respond to `sharded?`. Applications must handle the condition in which Active Record should use their custom handler.
|
897
914
|
|
898
|
-
*Eileen M. Uchitelle
|
915
|
+
*Eileen M. Uchitelle and John Crepezzi*
|
899
916
|
|
900
|
-
*
|
917
|
+
* `ActiveRecord::Base.serialize` no longer uses YAML by default.
|
901
918
|
|
902
|
-
|
919
|
+
YAML isn't particularly performant and can lead to security issues
|
920
|
+
if not used carefully.
|
903
921
|
|
904
|
-
|
922
|
+
Unfortunately there isn't really any good serializers in Ruby's stdlib
|
923
|
+
to replace it.
|
905
924
|
|
906
|
-
|
925
|
+
The obvious choice would be JSON, which is a fine format for this use case,
|
926
|
+
however the JSON serializer in Ruby's stdlib isn't strict enough, as it fallback
|
927
|
+
to casting unknown types to strings, which could lead to corrupted data.
|
907
928
|
|
908
|
-
|
929
|
+
Some third party JSON libraries like `Oj` have a suitable strict mode.
|
909
930
|
|
910
|
-
|
931
|
+
So it's preferable that users choose a serializer based on their own constraints.
|
911
932
|
|
912
|
-
|
933
|
+
The original default can be restored by setting `config.active_record.default_column_serializer = YAML`.
|
913
934
|
|
914
|
-
*
|
935
|
+
*Jean Boussier*
|
915
936
|
|
916
|
-
*
|
937
|
+
* `ActiveRecord::Base.serialize` signature changed.
|
917
938
|
|
918
|
-
|
939
|
+
Rather than a single positional argument that accepts two possible
|
940
|
+
types of values, `serialize` now accepts two distinct keyword arguments.
|
919
941
|
|
920
|
-
|
942
|
+
Before:
|
921
943
|
|
922
944
|
```ruby
|
923
|
-
|
945
|
+
serialize :content, JSON
|
946
|
+
serialize :backtrace, Array
|
924
947
|
```
|
925
948
|
|
926
|
-
|
927
|
-
|
928
|
-
* Remove deprecated support to YAML load `ActiveRecord::Base` instance in the Rails 4.2 and 4.1 formats.
|
949
|
+
After:
|
929
950
|
|
930
|
-
|
951
|
+
```ruby
|
952
|
+
serialize :content, coder: JSON
|
953
|
+
serialize :backtrace, type: Array
|
954
|
+
```
|
931
955
|
|
932
|
-
*
|
956
|
+
*Jean Boussier*
|
933
957
|
|
934
|
-
|
958
|
+
* YAML columns use `YAML.safe_dump` if available.
|
935
959
|
|
936
|
-
|
960
|
+
As of `psych 5.1.0`, `YAML.safe_dump` can now apply the same permitted
|
961
|
+
types restrictions than `YAML.safe_load`.
|
937
962
|
|
938
|
-
|
963
|
+
It's preferable to ensure the payload only use allowed types when we first
|
964
|
+
try to serialize it, otherwise you may end up with invalid records in the
|
965
|
+
database.
|
939
966
|
|
940
|
-
*
|
967
|
+
*Jean Boussier*
|
941
968
|
|
942
|
-
|
969
|
+
* `ActiveRecord::QueryLogs` better handle broken encoding.
|
943
970
|
|
944
|
-
|
971
|
+
It's not uncommon when building queries with BLOB fields to contain
|
972
|
+
binary data. Unless the call carefully encode the string in ASCII-8BIT
|
973
|
+
it generally end up being encoded in `UTF-8`, and `QueryLogs` would
|
974
|
+
end up failing on it.
|
945
975
|
|
946
|
-
|
976
|
+
`ActiveRecord::QueryLogs` no longer depend on the query to be properly encoded.
|
947
977
|
|
948
|
-
*
|
978
|
+
*Jean Boussier*
|
949
979
|
|
950
|
-
*
|
980
|
+
* Fix a bug where `ActiveRecord::Generators::ModelGenerator` would not respect create_table_migration template overrides.
|
951
981
|
|
952
|
-
```
|
953
|
-
|
954
|
-
|
955
|
-
|
956
|
-
|
982
|
+
```
|
983
|
+
rails g model create_books title:string content:text
|
984
|
+
```
|
985
|
+
will now read from the create_table_migration.rb.tt template in the following locations in order:
|
986
|
+
```
|
987
|
+
lib/templates/active_record/model/create_table_migration.rb
|
988
|
+
lib/templates/active_record/migration/create_table_migration.rb
|
989
|
+
```
|
957
990
|
|
958
|
-
|
959
|
-
# => #<Entry:0x00>
|
960
|
-
# id: 1
|
961
|
-
# entryable_id: 1,
|
962
|
-
# entryable_type: 'Message'
|
963
|
-
# ...>
|
991
|
+
*Spencer Neste*
|
964
992
|
|
965
|
-
|
966
|
-
# => #<Message:0x01>
|
967
|
-
# id: 1
|
968
|
-
# content: 'Hello world'
|
969
|
-
# ...>
|
970
|
-
```
|
993
|
+
* `ActiveRecord::Relation#explain` now accepts options.
|
971
994
|
|
972
|
-
|
995
|
+
For databases and adapters which support them (currently PostgreSQL
|
996
|
+
and MySQL), options can be passed to `explain` to provide more
|
997
|
+
detailed query plan analysis:
|
973
998
|
|
974
999
|
```ruby
|
975
|
-
|
976
|
-
# ArgumentError: Cannot build association `entryable'. Are you trying to build a polymorphic one-to-one association?
|
1000
|
+
Customer.where(id: 1).joins(:orders).explain(:analyze, :verbose)
|
977
1001
|
```
|
978
1002
|
|
979
|
-
*
|
1003
|
+
*Reid Lynch*
|
980
1004
|
|
981
|
-
*
|
1005
|
+
* Multiple `Arel::Nodes::SqlLiteral` nodes can now be added together to
|
1006
|
+
form `Arel::Nodes::Fragments` nodes. This allows joining several pieces
|
1007
|
+
of SQL.
|
982
1008
|
|
983
|
-
|
1009
|
+
*Matthew Draper*, *Ole Friis*
|
984
1010
|
|
985
|
-
|
986
|
-
|
987
|
-
```sql
|
988
|
-
DELETE FROM "posts" WHERE "posts"."id" IN (
|
989
|
-
SELECT "posts"."id" FROM "posts" INNER JOIN "comments" ON "comments"."post_id" = "posts"."id" GROUP BY "posts"."id" HAVING (count(comments.id) >= 2))
|
990
|
-
) [["flagged", "t"]]
|
991
|
-
```
|
1011
|
+
* `ActiveRecord::Base#signed_id` raises if called on a new record.
|
992
1012
|
|
993
|
-
|
1013
|
+
Previously it would return an ID that was not usable, since it was based on `id = nil`.
|
994
1014
|
|
995
|
-
*
|
1015
|
+
*Alex Ghiculescu*
|
996
1016
|
|
997
|
-
|
1017
|
+
* Allow SQL warnings to be reported.
|
998
1018
|
|
999
|
-
|
1000
|
-
UPDATE "posts" SET "flagged" = ? WHERE "posts"."id" IN (
|
1001
|
-
SELECT "posts"."id" FROM "posts" INNER JOIN "comments" ON "comments"."post_id" = "posts"."id"
|
1002
|
-
) [["flagged", "t"]]
|
1003
|
-
```
|
1019
|
+
Active Record configs can be set to enable SQL warning reporting.
|
1004
1020
|
|
1005
|
-
|
1021
|
+
```ruby
|
1022
|
+
# Configure action to take when SQL query produces warning
|
1023
|
+
config.active_record.db_warnings_action = :raise
|
1006
1024
|
|
1007
|
-
|
1008
|
-
|
1009
|
-
|
1010
|
-
|
1011
|
-
|
1025
|
+
# Configure allowlist of warnings that should always be ignored
|
1026
|
+
config.active_record.db_warnings_ignore = [
|
1027
|
+
/Invalid utf8mb4 character string/,
|
1028
|
+
"An exact warning message",
|
1029
|
+
]
|
1012
1030
|
```
|
1013
1031
|
|
1014
|
-
|
1032
|
+
This is supported for the MySQL and PostgreSQL adapters.
|
1015
1033
|
|
1016
|
-
*
|
1034
|
+
*Adrianna Chang*, *Paarth Madan*
|
1017
1035
|
|
1018
|
-
|
1036
|
+
* Add `#regroup` query method as a short-hand for `.unscope(:group).group(fields)`
|
1019
1037
|
|
1020
|
-
|
1021
|
-
|
1022
|
-
|
1023
|
-
|
1024
|
-
|
1025
|
-
animals:
|
1026
|
-
database: animals_db
|
1027
|
-
schema_dump: false
|
1038
|
+
Example:
|
1039
|
+
|
1040
|
+
```ruby
|
1041
|
+
Post.group(:title).regroup(:author)
|
1042
|
+
# SELECT `posts`.`*` FROM `posts` GROUP BY `posts`.`author`
|
1028
1043
|
```
|
1029
1044
|
|
1030
|
-
|
1045
|
+
*Danielius Visockas*
|
1031
1046
|
|
1032
|
-
|
1047
|
+
* PostgreSQL adapter method `enable_extension` now allows parameter to be `[schema_name.]<extension_name>`
|
1048
|
+
if the extension must be installed on another schema.
|
1033
1049
|
|
1034
|
-
|
1050
|
+
Example: `enable_extension('heroku_ext.hstore')`
|
1035
1051
|
|
1036
|
-
*
|
1052
|
+
*Leonardo Luarte*
|
1037
1053
|
|
1038
|
-
*
|
1054
|
+
* Add `:include` option to `add_index`.
|
1039
1055
|
|
1040
|
-
|
1056
|
+
Add support for including non-key columns in indexes for PostgreSQL
|
1057
|
+
with the `INCLUDE` parameter.
|
1041
1058
|
|
1042
|
-
|
1059
|
+
```ruby
|
1060
|
+
add_index(:users, :email, include: [:id, :created_at])
|
1061
|
+
```
|
1043
1062
|
|
1044
|
-
|
1063
|
+
will result in:
|
1045
1064
|
|
1046
|
-
|
1065
|
+
```sql
|
1066
|
+
CREATE INDEX index_users_on_email USING btree (email) INCLUDE (id, created_at)
|
1067
|
+
```
|
1047
1068
|
|
1048
|
-
*
|
1069
|
+
*Steve Abrams*
|
1049
1070
|
|
1050
|
-
|
1071
|
+
* `ActiveRecord::Relation`’s `#any?`, `#none?`, and `#one?` methods take an optional pattern
|
1072
|
+
argument, more closely matching their `Enumerable` equivalents.
|
1051
1073
|
|
1052
|
-
|
1074
|
+
*George Claghorn*
|
1053
1075
|
|
1054
|
-
|
1076
|
+
* Add `ActiveRecord::Base.normalizes` for declaring attribute normalizations.
|
1055
1077
|
|
1056
|
-
|
1078
|
+
An attribute normalization is applied when the attribute is assigned or
|
1079
|
+
updated, and the normalized value will be persisted to the database. The
|
1080
|
+
normalization is also applied to the corresponding keyword argument of query
|
1081
|
+
methods, allowing records to be queried using unnormalized values.
|
1057
1082
|
|
1058
|
-
|
1083
|
+
For example:
|
1059
1084
|
|
1060
|
-
|
1085
|
+
```ruby
|
1086
|
+
class User < ActiveRecord::Base
|
1087
|
+
normalizes :email, with: -> email { email.strip.downcase }
|
1088
|
+
normalizes :phone, with: -> phone { phone.delete("^0-9").delete_prefix("1") }
|
1089
|
+
end
|
1061
1090
|
|
1062
|
-
|
1091
|
+
user = User.create(email: " CRUISE-CONTROL@EXAMPLE.COM\n")
|
1092
|
+
user.email # => "cruise-control@example.com"
|
1063
1093
|
|
1064
|
-
|
1094
|
+
user = User.find_by(email: "\tCRUISE-CONTROL@EXAMPLE.COM ")
|
1095
|
+
user.email # => "cruise-control@example.com"
|
1096
|
+
user.email_before_type_cast # => "cruise-control@example.com"
|
1065
1097
|
|
1066
|
-
|
1098
|
+
User.where(email: "\tCRUISE-CONTROL@EXAMPLE.COM ").count # => 1
|
1099
|
+
User.where(["email = ?", "\tCRUISE-CONTROL@EXAMPLE.COM "]).count # => 0
|
1067
1100
|
|
1068
|
-
|
1101
|
+
User.exists?(email: "\tCRUISE-CONTROL@EXAMPLE.COM ") # => true
|
1102
|
+
User.exists?(["email = ?", "\tCRUISE-CONTROL@EXAMPLE.COM "]) # => false
|
1069
1103
|
|
1070
|
-
|
1104
|
+
User.normalize_value_for(:phone, "+1 (555) 867-5309") # => "5558675309"
|
1105
|
+
```
|
1071
1106
|
|
1072
|
-
*
|
1107
|
+
*Jonathan Hefner*
|
1073
1108
|
|
1074
|
-
|
1075
|
-
example, the `comments` association here now automatically detects
|
1076
|
-
`inverse_of: :post`, so we don't need to pass that option:
|
1109
|
+
* Hide changes to before_committed! callback behaviour behind flag.
|
1077
1110
|
|
1078
|
-
|
1079
|
-
|
1080
|
-
|
1081
|
-
|
1111
|
+
In #46525, behavior around before_committed! callbacks was changed so that callbacks
|
1112
|
+
would run on every enrolled record in a transaction, not just the first copy of a record.
|
1113
|
+
This change in behavior is now controlled by a configuration option,
|
1114
|
+
`config.active_record.before_committed_on_all_records`. It will be enabled by default on Rails 7.1.
|
1082
1115
|
|
1083
|
-
|
1084
|
-
belongs_to :post
|
1085
|
-
end
|
1086
|
-
```
|
1116
|
+
*Adrianna Chang*
|
1087
1117
|
|
1088
|
-
|
1089
|
-
association has a scope. In this example a scope on the `post` association
|
1090
|
-
would still prevent Rails from finding the inverse for the `comments`
|
1091
|
-
association.
|
1118
|
+
* The `namespaced_controller` Query Log tag now matches the `controller` format
|
1092
1119
|
|
1093
|
-
|
1120
|
+
For example, a request processed by `NameSpaced::UsersController` will now log as:
|
1094
1121
|
|
1095
|
-
```
|
1096
|
-
|
1122
|
+
```
|
1123
|
+
:controller # "users"
|
1124
|
+
:namespaced_controller # "name_spaced/users"
|
1097
1125
|
```
|
1098
1126
|
|
1099
|
-
*
|
1100
|
-
|
1101
|
-
* Accept optional transaction args to `ActiveRecord::Locking::Pessimistic#with_lock`
|
1102
|
-
|
1103
|
-
`#with_lock` now accepts transaction options like `requires_new:`,
|
1104
|
-
`isolation:`, and `joinable:`
|
1105
|
-
|
1106
|
-
*John Mileham*
|
1127
|
+
*Alex Ghiculescu*
|
1107
1128
|
|
1108
|
-
*
|
1129
|
+
* Return only unique ids from ActiveRecord::Calculations#ids
|
1109
1130
|
|
1110
|
-
|
1111
|
-
|
1112
|
-
One example of this is looking up / creating a person via one or more unique alias.
|
1131
|
+
Updated ActiveRecord::Calculations#ids to only return the unique ids of the base model
|
1132
|
+
when using eager_load, preload and includes.
|
1113
1133
|
|
1114
1134
|
```ruby
|
1115
|
-
|
1116
|
-
|
1117
|
-
|
1118
|
-
|
1119
|
-
|
1120
|
-
|
1121
|
-
.create_with(name: "David Heinemeier Hansson")
|
1122
|
-
.create_or_find_by(id: alias.user_id)
|
1123
|
-
end
|
1135
|
+
Post.find_by(id: 1).comments.count
|
1136
|
+
# => 5
|
1137
|
+
Post.includes(:comments).where(id: 1).pluck(:id)
|
1138
|
+
# => [1, 1, 1, 1, 1]
|
1139
|
+
Post.includes(:comments).where(id: 1).ids
|
1140
|
+
# => [1]
|
1124
1141
|
```
|
1125
1142
|
|
1126
|
-
|
1127
|
-
|
1128
|
-
By passing the `:deferrable` option to the `add_foreign_key` statement in migrations, it's possible to defer this
|
1129
|
-
check.
|
1143
|
+
*Joshua Young*
|
1130
1144
|
|
1131
|
-
|
1132
|
-
add_foreign_key :aliases, :person, deferrable: true
|
1133
|
-
```
|
1145
|
+
* Stop using `LOWER()` for case-insensitive queries on `citext` columns
|
1134
1146
|
|
1135
|
-
|
1136
|
-
`
|
1137
|
-
|
1147
|
+
Previously, `LOWER()` was added for e.g. uniqueness validations with
|
1148
|
+
`case_sensitive: false`.
|
1149
|
+
It wasn't mentioned in the documentation that the index without `LOWER()`
|
1150
|
+
wouldn't be used in this case.
|
1138
1151
|
|
1139
|
-
|
1140
|
-
(after the transaction):
|
1152
|
+
*Phil Pirozhkov*
|
1141
1153
|
|
1142
|
-
|
1143
|
-
|
1144
|
-
```
|
1154
|
+
* Extract `#sync_timezone_changes` method in AbstractMysqlAdapter to enable subclasses
|
1155
|
+
to sync database timezone changes without overriding `#raw_execute`.
|
1145
1156
|
|
1146
|
-
*
|
1157
|
+
*Adrianna Chang*, *Paarth Madan*
|
1147
1158
|
|
1148
|
-
*
|
1159
|
+
* Do not write additional new lines when dumping sql migration versions
|
1149
1160
|
|
1150
|
-
|
1151
|
-
```ruby
|
1152
|
-
ActiveRecord::DatabaseConfigurations::UrlConfig.new(
|
1153
|
-
:production, :production, 'postgres:///?user=user&password=secret&dbname=app', {}
|
1154
|
-
).configuration_hash
|
1155
|
-
```
|
1161
|
+
This change updates the `insert_versions_sql` function so that the database insert string containing the current database migration versions does not end with two additional new lines.
|
1156
1162
|
|
1157
|
-
|
1163
|
+
*Misha Schwartz*
|
1158
1164
|
|
1159
|
-
|
1160
|
-
{ :user=>"user", :password=>"secret", :dbname=>"app", :adapter=>"postgresql" }
|
1161
|
-
```
|
1165
|
+
* Fix `composed_of` value freezing and duplication.
|
1162
1166
|
|
1163
|
-
|
1167
|
+
Previously composite values exhibited two confusing behaviors:
|
1164
1168
|
|
1165
|
-
|
1169
|
+
- When reading a compositve value it'd _NOT_ be frozen, allowing it to get out of sync with its underlying database
|
1170
|
+
columns.
|
1171
|
+
- When writing a compositve value the argument would be frozen, potentially confusing the caller.
|
1166
1172
|
|
1167
|
-
|
1173
|
+
Currently, composite values instantiated based on database columns are frozen (addressing the first issue) and
|
1174
|
+
assigned compositve values are duplicated and the duplicate is frozen (addressing the second issue).
|
1168
1175
|
|
1169
|
-
|
1170
|
-
def up
|
1171
|
-
create_enum :mood, ["happy", "sad"]
|
1176
|
+
*Greg Navis*
|
1172
1177
|
|
1173
|
-
|
1174
|
-
t.enum :current_mood, enum_type: "mood", default: "happy", null: false
|
1175
|
-
end
|
1176
|
-
end
|
1177
|
-
```
|
1178
|
+
* Fix redundant updates to the column insensitivity cache
|
1178
1179
|
|
1179
|
-
|
1180
|
-
|
1180
|
+
Fixed redundant queries checking column capability for insensitive
|
1181
|
+
comparison.
|
1181
1182
|
|
1182
|
-
*
|
1183
|
+
*Phil Pirozhkov*
|
1183
1184
|
|
1184
|
-
*
|
1185
|
+
* Allow disabling methods generated by `ActiveRecord.enum`.
|
1185
1186
|
|
1186
|
-
|
1187
|
-
This allows loading the dump without a pgsql superuser account.
|
1187
|
+
*Alfred Dominic*
|
1188
1188
|
|
1189
|
-
|
1189
|
+
* Avoid validating `belongs_to` association if it has not changed.
|
1190
1190
|
|
1191
|
-
|
1191
|
+
Previously, when updating a record, Active Record will perform an extra query to check for the presence of
|
1192
|
+
`belongs_to` associations (if the presence is configured to be mandatory), even if that attribute hasn't changed.
|
1192
1193
|
|
1193
|
-
|
1194
|
+
Currently, only `belongs_to`-related columns are checked for presence. It is possible to have orphaned records with
|
1195
|
+
this approach. To avoid this problem, you need to use a foreign key.
|
1194
1196
|
|
1195
|
-
|
1196
|
-
support of those to the PostgreSQL adapter.
|
1197
|
+
This behavior can be controlled by configuration:
|
1197
1198
|
|
1198
1199
|
```ruby
|
1199
|
-
|
1200
|
-
t.string :name
|
1201
|
-
t.virtual :name_upcased, type: :string, as: 'upper(name)', stored: true
|
1202
|
-
end
|
1200
|
+
config.active_record.belongs_to_required_validates_foreign_key = false
|
1203
1201
|
```
|
1204
1202
|
|
1205
|
-
|
1203
|
+
and will be disabled by default with `config.load_defaults 7.1`.
|
1206
1204
|
|
1205
|
+
*fatkodima*
|
1207
1206
|
|
1208
|
-
|
1207
|
+
* `has_one` and `belongs_to` associations now define a `reset_association` method
|
1208
|
+
on the owner model (where `association` is the name of the association). This
|
1209
|
+
method unloads the cached associate record, if any, and causes the next access
|
1210
|
+
to query it from the database.
|
1209
1211
|
|
1210
|
-
*
|
1212
|
+
*George Claghorn*
|
1211
1213
|
|
1214
|
+
* Allow per attribute setting of YAML permitted classes (safe load) and unsafe load.
|
1212
1215
|
|
1213
|
-
|
1216
|
+
*Carlos Palhares*
|
1214
1217
|
|
1215
|
-
*
|
1218
|
+
* Add a build persistence method
|
1216
1219
|
|
1217
|
-
|
1220
|
+
Provides a wrapper for `new`, to provide feature parity with `create`s
|
1221
|
+
ability to create multiple records from an array of hashes, using the
|
1222
|
+
same notation as the `build` method on associations.
|
1218
1223
|
|
1219
|
-
|
1220
|
-
Creating scope :my_scope_name. Overwriting existing method "MyClass.my_scope_name" when overwriting existing scopes
|
1221
|
-
```
|
1224
|
+
*Sean Denny*
|
1222
1225
|
|
1223
|
-
|
1226
|
+
* Raise on assignment to readonly attributes
|
1224
1227
|
|
1225
|
-
|
1228
|
+
```ruby
|
1229
|
+
class Post < ActiveRecord::Base
|
1230
|
+
attr_readonly :content
|
1231
|
+
end
|
1232
|
+
Post.create!(content: "cannot be updated")
|
1233
|
+
post.content # "cannot be updated"
|
1234
|
+
post.content = "something else" # => ActiveRecord::ReadonlyAttributeError
|
1235
|
+
```
|
1226
1236
|
|
1227
|
-
|
1228
|
-
and not all databases support explicitly specifying additional precision.
|
1237
|
+
Previously, assignment would succeed but silently not write to the database.
|
1229
1238
|
|
1230
|
-
|
1231
|
-
for the SQL to produce a high precision timestamp on the current database.
|
1239
|
+
This behavior can be controlled by configuration:
|
1232
1240
|
|
1233
|
-
|
1241
|
+
```ruby
|
1242
|
+
config.active_record.raise_on_assign_to_attr_readonly = true
|
1243
|
+
```
|
1234
1244
|
|
1235
|
-
|
1245
|
+
and will be enabled by default with `config.load_defaults 7.1`.
|
1236
1246
|
|
1237
|
-
*
|
1247
|
+
*Alex Ghiculescu*, *Hartley McGuire*
|
1238
1248
|
|
1239
|
-
|
1240
|
-
when running postgresql database tasks.
|
1249
|
+
* Allow unscoping of preload and eager_load associations
|
1241
1250
|
|
1242
|
-
|
1243
|
-
|
1251
|
+
Added the ability to unscope preload and eager_load associations just like
|
1252
|
+
includes, joins, etc. See ActiveRecord::QueryMethods::VALID_UNSCOPING_VALUES
|
1253
|
+
for the full list of supported unscopable scopes.
|
1244
1254
|
|
1245
|
-
|
1246
|
-
|
1247
|
-
sslcert: client.crt
|
1248
|
-
sslkey: client.key
|
1249
|
-
sslrootcert: ca.crt
|
1255
|
+
```ruby
|
1256
|
+
query.unscope(:eager_load, :preload).group(:id).select(:id)
|
1250
1257
|
```
|
1251
1258
|
|
1252
|
-
|
1259
|
+
*David Morehouse*
|
1253
1260
|
|
1254
|
-
|
1255
|
-
PGSSLMODE=verify-full
|
1256
|
-
PGSSLCERT=client.crt
|
1257
|
-
PGSSLKEY=client.key
|
1258
|
-
PGSSLROOTCERT=ca.crt
|
1259
|
-
```
|
1261
|
+
* Add automatic filtering of encrypted attributes on inspect
|
1260
1262
|
|
1261
|
-
|
1263
|
+
This feature is enabled by default but can be disabled with
|
1264
|
+
|
1265
|
+
```ruby
|
1266
|
+
config.active_record.encryption.add_to_filter_parameters = false
|
1267
|
+
```
|
1262
1268
|
|
1263
|
-
*
|
1269
|
+
*Hartley McGuire*
|
1264
1270
|
|
1265
|
-
*
|
1271
|
+
* Clear locking column on #dup
|
1266
1272
|
|
1267
|
-
|
1268
|
-
and not also to the callbacks from the update itself.
|
1273
|
+
This change fixes not to duplicate locking_column like id and timestamps.
|
1269
1274
|
|
1270
|
-
|
1275
|
+
```
|
1276
|
+
car = Car.create!
|
1277
|
+
car.touch
|
1278
|
+
car.lock_version #=> 1
|
1279
|
+
car.dup.lock_version #=> 0
|
1280
|
+
```
|
1271
1281
|
|
1272
|
-
*
|
1273
|
-
using `String#constantize` instead of the model's `polymorphic_class_for`.
|
1282
|
+
*Shouichi Kamiya*, *Seonggi Yang*, *Ryohei UEDA*
|
1274
1283
|
|
1275
|
-
|
1276
|
-
1. `touch`ing the previously associated record
|
1277
|
-
2. updating the previously associated record's `counter_cache`
|
1284
|
+
* Invalidate transaction as early as possible
|
1278
1285
|
|
1279
|
-
|
1286
|
+
After rescuing a `TransactionRollbackError` exception Rails invalidates transactions earlier in the flow
|
1287
|
+
allowing the framework to skip issuing the `ROLLBACK` statement in more cases.
|
1288
|
+
Only affects adapters that have `savepoint_errors_invalidate_transactions?` configured as `true`,
|
1289
|
+
which at this point is only applicable to the `mysql2` adapter.
|
1280
1290
|
|
1281
|
-
*
|
1291
|
+
*Nikita Vasilevsky*
|
1282
1292
|
|
1283
|
-
|
1293
|
+
* Allow configuring columns list to be used in SQL queries issued by an `ActiveRecord::Base` object
|
1284
1294
|
|
1285
|
-
|
1295
|
+
It is now possible to configure columns list that will be used to build an SQL query clauses when
|
1296
|
+
updating, deleting or reloading an `ActiveRecord::Base` object
|
1286
1297
|
|
1287
1298
|
```ruby
|
1288
|
-
|
1299
|
+
class Developer < ActiveRecord::Base
|
1300
|
+
query_constraints :company_id, :id
|
1301
|
+
end
|
1302
|
+
developer = Developer.first.update(name: "Bob")
|
1303
|
+
# => UPDATE "developers" SET "name" = 'Bob' WHERE "developers"."company_id" = 1 AND "developers"."id" = 1
|
1289
1304
|
```
|
1290
1305
|
|
1291
|
-
|
1306
|
+
*Nikita Vasilevsky*
|
1292
1307
|
|
1293
|
-
|
1294
|
-
config.active_record.schema_cache_ignored_tables = [/^_/]
|
1295
|
-
```
|
1308
|
+
* Adds `validate` to foreign keys and check constraints in schema.rb
|
1296
1309
|
|
1297
|
-
|
1310
|
+
Previously, `schema.rb` would not record if `validate: false` had been used when adding a foreign key or check
|
1311
|
+
constraint, so restoring a database from the schema could result in foreign keys or check constraints being
|
1312
|
+
incorrectly validated.
|
1298
1313
|
|
1299
|
-
*
|
1314
|
+
*Tommy Graves*
|
1300
1315
|
|
1301
|
-
|
1302
|
-
|
1303
|
-
database adapters. This change unifies the behavior so each method behaves the same regardless
|
1304
|
-
of adapter.
|
1316
|
+
* Adapter `#execute` methods now accept an `allow_retry` option. When set to `true`, the SQL statement will be
|
1317
|
+
retried, up to the database's configured `connection_retries` value, upon encountering connection-related errors.
|
1305
1318
|
|
1306
|
-
|
1319
|
+
*Adrianna Chang*
|
1307
1320
|
|
1308
|
-
|
1309
|
-
`columns_hash`: (unchanged) raises a db error if the table does not exist.
|
1310
|
-
`primary_keys`: (unchanged) returns `nil` if the table does not exist.
|
1311
|
-
`indexes`: (changed for mysql2) returns `[]` if the table does not exist.
|
1321
|
+
* Only trigger `after_commit :destroy` callbacks when a database row is deleted.
|
1312
1322
|
|
1313
|
-
|
1323
|
+
This prevents `after_commit :destroy` callbacks from being triggered again
|
1324
|
+
when `destroy` is called multiple times on the same record.
|
1314
1325
|
|
1315
|
-
*
|
1326
|
+
*Ben Sheldon*
|
1316
1327
|
|
1317
|
-
|
1328
|
+
* Fix `ciphertext_for` for yet-to-be-encrypted values.
|
1318
1329
|
|
1319
|
-
|
1330
|
+
Previously, `ciphertext_for` returned the cleartext of values that had not
|
1331
|
+
yet been encrypted, such as with an unpersisted record:
|
1320
1332
|
|
1321
|
-
|
1333
|
+
```ruby
|
1334
|
+
Post.encrypts :body
|
1322
1335
|
|
1323
|
-
|
1324
|
-
|
1325
|
-
|
1336
|
+
post = Post.create!(body: "Hello")
|
1337
|
+
post.ciphertext_for(:body)
|
1338
|
+
# => "{\"p\":\"abc..."
|
1326
1339
|
|
1327
|
-
|
1328
|
-
|
1340
|
+
post.body = "World"
|
1341
|
+
post.ciphertext_for(:body)
|
1342
|
+
# => "World"
|
1343
|
+
```
|
1329
1344
|
|
1330
|
-
|
1331
|
-
|
1332
|
-
database: my_database
|
1333
|
-
adapter: mysql2
|
1334
|
-
animals:
|
1335
|
-
database: my_animals_database
|
1336
|
-
adapter: mysql2
|
1337
|
-
database_tasks: false
|
1338
|
-
```
|
1345
|
+
Now, `ciphertext_for` will always return the ciphertext of encrypted
|
1346
|
+
attributes:
|
1339
1347
|
|
1340
|
-
|
1348
|
+
```ruby
|
1349
|
+
Post.encrypts :body
|
1341
1350
|
|
1342
|
-
|
1351
|
+
post = Post.create!(body: "Hello")
|
1352
|
+
post.ciphertext_for(:body)
|
1353
|
+
# => "{\"p\":\"abc..."
|
1343
1354
|
|
1344
|
-
|
1345
|
-
|
1355
|
+
post.body = "World"
|
1356
|
+
post.ciphertext_for(:body)
|
1357
|
+
# => "{\"p\":\"xyz..."
|
1358
|
+
```
|
1346
1359
|
|
1347
|
-
|
1360
|
+
*Jonathan Hefner*
|
1348
1361
|
|
1349
|
-
*
|
1362
|
+
* Fix a bug where using groups and counts with long table names would return incorrect results.
|
1350
1363
|
|
1351
|
-
|
1364
|
+
*Shota Toguchi*, *Yusaku Ono*
|
1352
1365
|
|
1353
|
-
|
1354
|
-
# config/application.rb
|
1355
|
-
module MyApp
|
1356
|
-
class Application < Rails::Application
|
1357
|
-
config.active_record.query_log_tags_enabled = true
|
1358
|
-
end
|
1359
|
-
end
|
1360
|
-
```
|
1366
|
+
* Fix encryption of column default values.
|
1361
1367
|
|
1362
|
-
|
1368
|
+
Previously, encrypted attributes that used column default values appeared to
|
1369
|
+
be encrypted on create, but were not:
|
1363
1370
|
|
1364
|
-
|
1365
|
-
|
1366
|
-
def index
|
1367
|
-
@books = Book.all
|
1368
|
-
end
|
1369
|
-
end
|
1370
|
-
```
|
1371
|
+
```ruby
|
1372
|
+
Book.encrypts :name
|
1371
1373
|
|
1372
|
-
|
1373
|
-
|
1374
|
-
|
1375
|
-
|
1374
|
+
book = Book.create!
|
1375
|
+
book.name
|
1376
|
+
# => "<untitled>"
|
1377
|
+
book.name_before_type_cast
|
1378
|
+
# => "{\"p\":\"abc..."
|
1379
|
+
book.reload.name_before_type_cast
|
1380
|
+
# => "<untitled>"
|
1381
|
+
```
|
1376
1382
|
|
1377
|
-
|
1383
|
+
Now, attributes with column default values are encrypted:
|
1378
1384
|
|
1379
|
-
|
1380
|
-
|
1381
|
-
:application,
|
1382
|
-
:controller,
|
1383
|
-
:action,
|
1384
|
-
{
|
1385
|
-
custom_static: "foo",
|
1386
|
-
custom_dynamic: -> { Time.now }
|
1387
|
-
}
|
1388
|
-
]
|
1389
|
-
```
|
1385
|
+
```ruby
|
1386
|
+
Book.encrypts :name
|
1390
1387
|
|
1391
|
-
|
1388
|
+
book = Book.create!
|
1389
|
+
book.name
|
1390
|
+
# => "<untitled>"
|
1391
|
+
book.name_before_type_cast
|
1392
|
+
# => "{\"p\":\"abc..."
|
1393
|
+
book.reload.name_before_type_cast
|
1394
|
+
# => "{\"p\":\"abc..."
|
1395
|
+
```
|
1392
1396
|
|
1393
|
-
*
|
1397
|
+
*Jonathan Hefner*
|
1394
1398
|
|
1395
|
-
|
1399
|
+
* Deprecate delegation from `Base` to `connection_handler`.
|
1396
1400
|
|
1397
|
-
|
1401
|
+
Calling `Base.clear_all_connections!`, `Base.clear_active_connections!`, `Base.clear_reloadable_connections!` and `Base.flush_idle_connections!` is deprecated. Please call these methods on the connection handler directly. In future Rails versions, the delegation from `Base` to the `connection_handler` will be removed.
|
1398
1402
|
|
1399
|
-
|
1400
|
-
about to use for `#or` or `#and` is structurally compatible with the
|
1401
|
-
receiver.
|
1403
|
+
*Eileen M. Uchitelle*
|
1402
1404
|
|
1403
|
-
|
1405
|
+
* Allow ActiveRecord::QueryMethods#reselect to receive hash values, similar to ActiveRecord::QueryMethods#select
|
1404
1406
|
|
1405
|
-
*
|
1407
|
+
*Sampat Badhe*
|
1406
1408
|
|
1407
|
-
|
1408
|
-
returned in based on a SQL expression. By default, this will be accomplished
|
1409
|
-
using a case statement, as in:
|
1409
|
+
* Validate options when managing columns and tables in migrations.
|
1410
1410
|
|
1411
|
-
|
1412
|
-
|
1413
|
-
|
1411
|
+
If an invalid option is passed to a migration method like `create_table` and `add_column`, an error will be raised
|
1412
|
+
instead of the option being silently ignored. Validation of the options will only be applied for new migrations
|
1413
|
+
that are created.
|
1414
1414
|
|
1415
|
-
|
1415
|
+
*Guo Xiang Tan*, *George Wambold*
|
1416
1416
|
|
1417
|
-
|
1418
|
-
SELECT "posts".* FROM "posts" ORDER BY CASE "posts"."id" WHEN 3 THEN 1 WHEN 5 THEN 2 WHEN 1 THEN 3 ELSE 4 END ASC
|
1419
|
-
```
|
1417
|
+
* Update query log tags to use the [SQLCommenter](https://open-telemetry.github.io/opentelemetry-sqlcommenter/) format by default. See [#46179](https://github.com/rails/rails/issues/46179)
|
1420
1418
|
|
1421
|
-
|
1422
|
-
`FIELD` function, that connection adapter will generate the following SQL
|
1423
|
-
instead:
|
1419
|
+
To opt out of SQLCommenter-formatted query log tags, set `config.active_record.query_log_tags_format = :legacy`. By default, this is set to `:sqlcommenter`.
|
1424
1420
|
|
1425
|
-
|
1426
|
-
SELECT "posts".* FROM "posts" ORDER BY FIELD("posts"."id", 1, 5, 3) DESC
|
1427
|
-
```
|
1421
|
+
*Modulitos* and *Iheanyi*
|
1428
1422
|
|
1429
|
-
|
1423
|
+
* Allow any ERB in the database.yml when creating rake tasks.
|
1430
1424
|
|
1431
|
-
|
1425
|
+
Any ERB can be used in `database.yml` even if it accesses environment
|
1426
|
+
configurations.
|
1432
1427
|
|
1433
|
-
|
1428
|
+
Deprecates `config.active_record.suppress_multiple_database_warning`.
|
1434
1429
|
|
1435
|
-
|
1436
|
-
scope = Post.includes(:comments).order(:"comments.label")
|
1437
|
-
=> true
|
1438
|
-
```
|
1430
|
+
*Eike Send*
|
1439
1431
|
|
1440
|
-
|
1432
|
+
* Add table to error for duplicate column definitions.
|
1441
1433
|
|
1442
|
-
|
1434
|
+
If a migration defines duplicate columns for a table, the error message
|
1435
|
+
shows which table it concerns.
|
1443
1436
|
|
1444
|
-
|
1445
|
-
if a different associated object has been assigned and the foreign key will be updated in the
|
1446
|
-
next save.
|
1437
|
+
*Petrik de Heus*
|
1447
1438
|
|
1448
|
-
|
1449
|
-
association to reference a different associated object.
|
1439
|
+
* Fix erroneous nil default precision on virtual datetime columns.
|
1450
1440
|
|
1451
|
-
|
1441
|
+
Prior to this change, virtual datetime columns did not have the same
|
1442
|
+
default precision as regular datetime columns, resulting in the following
|
1443
|
+
being erroneously equivalent:
|
1452
1444
|
|
1453
|
-
|
1445
|
+
t.virtual :name, type: datetime, as: "expression"
|
1446
|
+
t.virtual :name, type: datetime, precision: nil, as: "expression"
|
1454
1447
|
|
1455
|
-
|
1456
|
-
|
1448
|
+
This change fixes the default precision lookup, so virtual and regular
|
1449
|
+
datetime column default precisions match.
|
1457
1450
|
|
1458
|
-
|
1459
|
-
# config/database.yml
|
1451
|
+
*Sam Bostock*
|
1460
1452
|
|
1461
|
-
|
1462
|
-
schema_dump: false
|
1463
|
-
```
|
1453
|
+
* Use connection from `#with_raw_connection` in `#quote_string`.
|
1464
1454
|
|
1465
|
-
|
1455
|
+
This ensures that the string quoting is wrapped in the reconnect and retry logic
|
1456
|
+
that `#with_raw_connection` offers.
|
1466
1457
|
|
1467
|
-
*
|
1458
|
+
*Adrianna Chang*
|
1468
1459
|
|
1469
|
-
|
1470
|
-
on an outer table.
|
1460
|
+
* Add `expires_at` option to `signed_id`.
|
1471
1461
|
|
1472
|
-
|
1473
|
-
Post.includes(:comments).order({ "comments.label": :ASC }).eager_loading?
|
1474
|
-
# => true
|
1475
|
-
```
|
1462
|
+
*Shouichi Kamiya*
|
1476
1463
|
|
1477
|
-
|
1464
|
+
* Allow applications to set retry deadline for query retries.
|
1478
1465
|
|
1479
|
-
|
1466
|
+
Building on the work done in #44576 and #44591, we extend the logic that automatically
|
1467
|
+
reconnects database connections to take into account a timeout limit. We won't retry
|
1468
|
+
a query if a given amount of time has elapsed since the query was first attempted. This
|
1469
|
+
value defaults to nil, meaning that all retryable queries are retried regardless of time elapsed,
|
1470
|
+
but this can be changed via the `retry_deadline` option in the database config.
|
1480
1471
|
|
1481
|
-
|
1472
|
+
*Adrianna Chang*
|
1482
1473
|
|
1483
|
-
|
1474
|
+
* Fix a case where the query cache can return wrong values. See #46044
|
1484
1475
|
|
1485
|
-
*
|
1476
|
+
*Aaron Patterson*
|
1486
1477
|
|
1487
|
-
|
1478
|
+
* Support MySQL's ssl-mode option for MySQLDatabaseTasks.
|
1488
1479
|
|
1489
|
-
|
1490
|
-
|
1491
|
-
|
1480
|
+
Verifying the identity of the database server requires setting the ssl-mode
|
1481
|
+
option to VERIFY_CA or VERIFY_IDENTITY. This option was previously ignored
|
1482
|
+
for MySQL database tasks like creating a database and dumping the structure.
|
1492
1483
|
|
1493
|
-
|
1494
|
-
would cause old processes to no longer be able to create new records.
|
1484
|
+
*Petrik de Heus*
|
1495
1485
|
|
1496
|
-
|
1497
|
-
to stop using it.
|
1486
|
+
* Move `ActiveRecord::InternalMetadata` to an independent object.
|
1498
1487
|
|
1499
|
-
|
1488
|
+
`ActiveRecord::InternalMetadata` no longer inherits from `ActiveRecord::Base` and is now an independent object that should be instantiated with a `connection`. This class is private and should not be used by applications directly. If you want to interact with the schema migrations table, please access it on the connection directly, for example: `ActiveRecord::Base.connection.schema_migration`.
|
1500
1489
|
|
1501
|
-
*
|
1490
|
+
*Eileen M. Uchitelle*
|
1502
1491
|
|
1503
|
-
|
1492
|
+
* Deprecate quoting `ActiveSupport::Duration` as an integer
|
1504
1493
|
|
1505
|
-
|
1506
|
-
|
1494
|
+
Using ActiveSupport::Duration as an interpolated bind parameter in a SQL
|
1495
|
+
string template is deprecated. To avoid this warning, you should explicitly
|
1496
|
+
convert the duration to a more specific database type. For example, if you
|
1497
|
+
want to use a duration as an integer number of seconds:
|
1498
|
+
```
|
1499
|
+
Record.where("duration = ?", 1.hour.to_i)
|
1500
|
+
```
|
1501
|
+
If you want to use a duration as an ISO 8601 string:
|
1502
|
+
```
|
1503
|
+
Record.where("duration = ?", 1.hour.iso8601)
|
1507
1504
|
```
|
1508
1505
|
|
1509
|
-
|
1510
|
-
|
1511
|
-
The feature is supported by SQLite and PostgreSQL, other adapters can also add support for it.
|
1506
|
+
*Aram Greenman*
|
1512
1507
|
|
1513
|
-
|
1508
|
+
* Allow `QueryMethods#in_order_of` to order by a string column name.
|
1514
1509
|
|
1515
|
-
|
1510
|
+
```ruby
|
1511
|
+
Post.in_order_of("id", [4,2,3,1]).to_a
|
1512
|
+
Post.joins(:author).in_order_of("authors.name", ["Bob", "Anna", "John"]).to_a
|
1513
|
+
```
|
1516
1514
|
|
1517
|
-
|
1518
|
-
the owner should still return `nil` on the `has_one` relation.
|
1515
|
+
*Igor Kasyanchuk*
|
1519
1516
|
|
1520
|
-
|
1517
|
+
* Move `ActiveRecord::SchemaMigration` to an independent object.
|
1521
1518
|
|
1522
|
-
|
1519
|
+
`ActiveRecord::SchemaMigration` no longer inherits from `ActiveRecord::Base` and is now an independent object that should be instantiated with a `connection`. This class is private and should not be used by applications directly. If you want to interact with the schema migrations table, please access it on the connection directly, for example: `ActiveRecord::Base.connection.schema_migration`.
|
1523
1520
|
|
1524
|
-
*
|
1521
|
+
*Eileen M. Uchitelle*
|
1525
1522
|
|
1526
|
-
|
1523
|
+
* Deprecate `all_connection_pools` and make `connection_pool_list` more explicit.
|
1527
1524
|
|
1528
|
-
|
1525
|
+
Following on #45924 `all_connection_pools` is now deprecated. `connection_pool_list` will either take an explicit role or applications can opt into the new behavior by passing `:all`.
|
1529
1526
|
|
1530
|
-
|
1531
|
-
that already exists or when removing a foreign key that does not exist.
|
1527
|
+
*Eileen M. Uchitelle*
|
1532
1528
|
|
1533
|
-
|
1529
|
+
* Fix connection handler methods to operate on all pools.
|
1534
1530
|
|
1535
|
-
|
1536
|
-
class AddAuthorsForeignKeyToArticles < ActiveRecord::Migration[7.0]
|
1537
|
-
def change
|
1538
|
-
add_foreign_key :articles, :authors, if_not_exists: true
|
1539
|
-
end
|
1540
|
-
end
|
1541
|
-
```
|
1531
|
+
`active_connections?`, `clear_active_connections!`, `clear_reloadable_connections!`, `clear_all_connections!`, and `flush_idle_connections!` now operate on all pools by default. Previously they would default to using the `current_role` or `:writing` role unless specified.
|
1542
1532
|
|
1543
|
-
|
1544
|
-
class RemoveAuthorsForeignKeyFromArticles < ActiveRecord::Migration[7.0]
|
1545
|
-
def change
|
1546
|
-
remove_foreign_key :articles, :authors, if_exists: true
|
1547
|
-
end
|
1548
|
-
end
|
1549
|
-
```
|
1533
|
+
*Eileen M. Uchitelle*
|
1550
1534
|
|
1551
|
-
*Roberto Miranda*
|
1552
1535
|
|
1553
|
-
*
|
1536
|
+
* Allow ActiveRecord::QueryMethods#select to receive hash values.
|
1554
1537
|
|
1555
|
-
|
1556
|
-
environment variables which persisted beyond the command being run, and may
|
1557
|
-
have caused subsequent commands and connections to fail. Tasks running
|
1558
|
-
across multiple postgresql databases like `rails db:test:prepare` may have
|
1559
|
-
been affected.
|
1538
|
+
Currently, `select` might receive only raw sql and symbols to define columns and aliases to select.
|
1560
1539
|
|
1561
|
-
|
1540
|
+
With this change we can provide `hash` as argument, for example:
|
1562
1541
|
|
1563
|
-
|
1542
|
+
```ruby
|
1543
|
+
Post.joins(:comments).select(posts: [:id, :title, :created_at], comments: [:id, :body, :author_id])
|
1544
|
+
#=> "SELECT \"posts\".\"id\", \"posts\".\"title\", \"posts\".\"created_at\", \"comments\".\"id\", \"comments\".\"body\", \"comments\".\"author_id\"
|
1545
|
+
# FROM \"posts\" INNER JOIN \"comments\" ON \"comments\".\"post_id\" = \"posts\".\"id\""
|
1564
1546
|
|
1565
|
-
|
1547
|
+
Post.joins(:comments).select(posts: { id: :post_id, title: :post_title }, comments: { id: :comment_id, body: :comment_body })
|
1548
|
+
#=> "SELECT posts.id as post_id, posts.title as post_title, comments.id as comment_id, comments.body as comment_body
|
1549
|
+
# FROM \"posts\" INNER JOIN \"comments\" ON \"comments\".\"post_id\" = \"posts\".\"id\""
|
1550
|
+
```
|
1551
|
+
*Oleksandr Holubenko*, *Josef Šimánek*, *Jean Boussier*
|
1566
1552
|
|
1567
|
-
|
1553
|
+
* Adapts virtual attributes on `ActiveRecord::Persistence#becomes`.
|
1568
1554
|
|
1569
|
-
|
1555
|
+
When source and target classes have a different set of attributes adapts
|
1556
|
+
attributes such that the extra attributes from target are added.
|
1570
1557
|
|
1571
|
-
|
1558
|
+
```ruby
|
1559
|
+
class Person < ApplicationRecord
|
1560
|
+
end
|
1572
1561
|
|
1573
|
-
|
1562
|
+
class WebUser < Person
|
1563
|
+
attribute :is_admin, :boolean
|
1564
|
+
after_initialize :set_admin
|
1574
1565
|
|
1575
|
-
|
1566
|
+
def set_admin
|
1567
|
+
write_attribute(:is_admin, email =~ /@ourcompany\.com$/)
|
1568
|
+
end
|
1569
|
+
end
|
1576
1570
|
|
1577
|
-
|
1578
|
-
|
1579
|
-
|
1580
|
-
|
1571
|
+
person = Person.find_by(email: "email@ourcompany.com")
|
1572
|
+
person.respond_to? :is_admin
|
1573
|
+
# => false
|
1574
|
+
person.becomes(WebUser).is_admin?
|
1575
|
+
# => true
|
1576
|
+
```
|
1581
1577
|
|
1582
|
-
|
1583
|
-
that is `Encoding::UTF_8` by default. It can be disabled by setting it to `nil`.
|
1578
|
+
*Jacopo Beschi*, *Sampson Crowley*
|
1584
1579
|
|
1585
|
-
|
1580
|
+
* Fix `ActiveRecord::QueryMethods#in_order_of` to include `nil`s, to match the
|
1581
|
+
behavior of `Enumerable#in_order_of`.
|
1586
1582
|
|
1587
|
-
|
1583
|
+
For example, `Post.in_order_of(:title, [nil, "foo"])` will now include posts
|
1584
|
+
with `nil` titles, the same as `Post.all.to_a.in_order_of(:title, [nil, "foo"])`.
|
1588
1585
|
|
1589
|
-
|
1590
|
-
instance `"foo" = 0`, will implicitly cast `"foo"` to `0` and will evaluate to `TRUE` which can
|
1591
|
-
lead to security vulnerabilities.
|
1586
|
+
*fatkodima*
|
1592
1587
|
|
1593
|
-
|
1594
|
-
being compared, however until now it was still vulnerable when using bind parameters:
|
1588
|
+
* Optimize `add_timestamps` to use a single SQL statement.
|
1595
1589
|
|
1596
1590
|
```ruby
|
1597
|
-
|
1591
|
+
add_timestamps :my_table
|
1598
1592
|
```
|
1599
1593
|
|
1600
|
-
|
1594
|
+
Now results in the following SQL:
|
1601
1595
|
|
1602
1596
|
```sql
|
1603
|
-
|
1597
|
+
ALTER TABLE "my_table" ADD COLUMN "created_at" datetime(6) NOT NULL, ADD COLUMN "updated_at" datetime(6) NOT NULL
|
1604
1598
|
```
|
1605
1599
|
|
1606
|
-
|
1607
|
-
|
1608
|
-
```sql
|
1609
|
-
SELECT * FROM `users` WHERE `login_token` = '0' LIMIT 1;
|
1610
|
-
```
|
1600
|
+
*Iliana Hadzhiatanasova*
|
1611
1601
|
|
1612
|
-
|
1602
|
+
* Add `drop_enum` migration command for PostgreSQL
|
1613
1603
|
|
1614
|
-
|
1604
|
+
This does the inverse of `create_enum`. Before dropping an enum, ensure you have
|
1605
|
+
dropped columns that depend on it.
|
1615
1606
|
|
1616
|
-
|
1617
|
-
would silently have no effects.
|
1607
|
+
*Alex Ghiculescu*
|
1618
1608
|
|
1619
|
-
|
1609
|
+
* Adds support for `if_exists` option when removing a check constraint.
|
1620
1610
|
|
1621
|
-
|
1611
|
+
The `remove_check_constraint` method now accepts an `if_exists` option. If set
|
1612
|
+
to true an error won't be raised if the check constraint doesn't exist.
|
1622
1613
|
|
1623
|
-
|
1614
|
+
*Margaret Parsa* and *Aditya Bhutani*
|
1624
1615
|
|
1625
|
-
|
1626
|
-
Person.update!(:all, state: "confirmed")
|
1627
|
-
```
|
1616
|
+
* `find_or_create_by` now try to find a second time if it hits a unicity constraint.
|
1628
1617
|
|
1629
|
-
|
1618
|
+
`find_or_create_by` always has been inherently racy, either creating multiple
|
1619
|
+
duplicate records or failing with `ActiveRecord::RecordNotUnique` depending on
|
1620
|
+
whether a proper unicity constraint was set.
|
1630
1621
|
|
1631
|
-
|
1622
|
+
`create_or_find_by` was introduced for this use case, however it's quite wasteful
|
1623
|
+
when the record is expected to exist most of the time, as INSERT require to send
|
1624
|
+
more data than SELECT and require more work from the database. Also on some
|
1625
|
+
databases it can actually consume a primary key increment which is undesirable.
|
1632
1626
|
|
1633
|
-
|
1627
|
+
So for case where most of the time the record is expected to exist, `find_or_create_by`
|
1628
|
+
can be made race-condition free by re-trying the `find` if the `create` failed
|
1629
|
+
with `ActiveRecord::RecordNotUnique`. This assumes that the table has the proper
|
1630
|
+
unicity constraints, if not, `find_or_create_by` will still lead to duplicated records.
|
1634
1631
|
|
1635
|
-
*
|
1632
|
+
*Jean Boussier*, *Alex Kitchens*
|
1636
1633
|
|
1637
|
-
*
|
1634
|
+
* Introduce a simpler constructor API for ActiveRecord database adapters.
|
1638
1635
|
|
1639
|
-
|
1636
|
+
Previously the adapter had to know how to build a new raw connection to
|
1637
|
+
support reconnect, but also expected to be passed an initial already-
|
1638
|
+
established connection.
|
1640
1639
|
|
1641
|
-
|
1640
|
+
When manually creating an adapter instance, it will now accept a single
|
1641
|
+
config hash, and only establish the real connection on demand.
|
1642
1642
|
|
1643
|
-
*
|
1643
|
+
*Matthew Draper*
|
1644
1644
|
|
1645
|
-
|
1645
|
+
* Avoid redundant `SELECT 1` connection-validation query during DB pool
|
1646
|
+
checkout when possible.
|
1646
1647
|
|
1647
|
-
|
1648
|
+
If the first query run during a request is known to be idempotent, it can be
|
1649
|
+
used directly to validate the connection, saving a network round-trip.
|
1648
1650
|
|
1649
|
-
|
1651
|
+
*Matthew Draper*
|
1650
1652
|
|
1651
|
-
|
1653
|
+
* Automatically reconnect broken database connections when safe, even
|
1654
|
+
mid-request.
|
1652
1655
|
|
1653
|
-
|
1656
|
+
When an error occurs while attempting to run a known-idempotent query, and
|
1657
|
+
not inside a transaction, it is safe to immediately reconnect to the
|
1658
|
+
database server and try again, so this is now the default behavior.
|
1654
1659
|
|
1655
|
-
|
1656
|
-
|
1660
|
+
This new default should always be safe -- to support that, it's consciously
|
1661
|
+
conservative about which queries are considered idempotent -- but if
|
1662
|
+
necessary it can be disabled by setting the `connection_retries` connection
|
1663
|
+
option to `0`.
|
1657
1664
|
|
1658
|
-
*
|
1665
|
+
*Matthew Draper*
|
1659
1666
|
|
1660
|
-
*
|
1667
|
+
* Avoid removing a PostgreSQL extension when there are dependent objects.
|
1661
1668
|
|
1662
|
-
|
1663
|
-
on a subclass won't change the parent's logger.
|
1669
|
+
Previously, removing an extension also implicitly removed dependent objects. Now, this will raise an error.
|
1664
1670
|
|
1665
|
-
|
1671
|
+
You can force removing the extension:
|
1666
1672
|
|
1667
|
-
|
1673
|
+
```ruby
|
1674
|
+
disable_extension :citext, force: :cascade
|
1675
|
+
```
|
1668
1676
|
|
1669
|
-
|
1677
|
+
Fixes #29091.
|
1670
1678
|
|
1671
|
-
*
|
1679
|
+
*fatkodima*
|
1672
1680
|
|
1673
|
-
|
1681
|
+
* Allow nested functions as safe SQL string
|
1674
1682
|
|
1675
|
-
*
|
1683
|
+
*Michael Siegfried*
|
1676
1684
|
|
1677
|
-
|
1678
|
-
the `column_exists?` check would look for a column with the same name and type as the migration.
|
1685
|
+
* Allow `destroy_association_async_job=` to be configured with a class string instead of a constant.
|
1679
1686
|
|
1680
|
-
|
1681
|
-
|
1682
|
-
|
1683
|
-
the type to the database type without running the migration, we opted to drop the type check from
|
1684
|
-
`add_column`. This means that migrations adding a duplicate column with a different type will no
|
1685
|
-
longer raise an error.
|
1687
|
+
Defers an autoloading dependency between `ActiveRecord::Base` and `ActiveJob::Base`
|
1688
|
+
and moves the configuration of `ActiveRecord::DestroyAssociationAsyncJob`
|
1689
|
+
from ActiveJob to ActiveRecord.
|
1686
1690
|
|
1687
|
-
|
1691
|
+
Deprecates `ActiveRecord::ActiveJobRequiredError` and now raises a `NameError`
|
1692
|
+
if the job class is unloadable or an `ActiveRecord::ConfigurationError` if
|
1693
|
+
`dependent: :destroy_async` is declared on an association but there is no job
|
1694
|
+
class configured.
|
1688
1695
|
|
1689
|
-
*
|
1696
|
+
*Ben Sheldon*
|
1690
1697
|
|
1691
|
-
|
1692
|
-
in a new Rails application.
|
1693
|
-
For the above reasons log a warning message when running SQLite in production.
|
1698
|
+
* Fix `ActiveRecord::Store` to serialize as a regular Hash
|
1694
1699
|
|
1695
|
-
|
1700
|
+
Previously it would serialize as an `ActiveSupport::HashWithIndifferentAccess`
|
1701
|
+
which is wasteful and cause problem with YAML safe_load.
|
1696
1702
|
|
1697
|
-
*
|
1703
|
+
*Jean Boussier*
|
1698
1704
|
|
1699
|
-
* Add
|
1705
|
+
* Add `timestamptz` as a time zone aware type for PostgreSQL
|
1700
1706
|
|
1701
|
-
|
1702
|
-
databases. When set, this option instructs Rails to generate 2 or
|
1703
|
-
more queries rather than generating joins for `has_one` associations.
|
1707
|
+
This is required for correctly parsing `timestamp with time zone` values in your database.
|
1704
1708
|
|
1705
|
-
|
1709
|
+
If you don't want this, you can opt out by adding this initializer:
|
1706
1710
|
|
1707
1711
|
```ruby
|
1708
|
-
|
1709
|
-
has_one :dog
|
1710
|
-
has_one :veterinarian, through: :dog, disable_joins: true
|
1711
|
-
end
|
1712
|
-
```
|
1713
|
-
|
1714
|
-
Then instead of generating join SQL, two queries are used for `@person.veterinarian`:
|
1715
|
-
|
1716
|
-
```
|
1717
|
-
SELECT "dogs"."id" FROM "dogs" WHERE "dogs"."person_id" = ? [["person_id", 1]]
|
1718
|
-
SELECT "veterinarians".* FROM "veterinarians" WHERE "veterinarians"."dog_id" = ? [["dog_id", 1]]
|
1712
|
+
ActiveRecord::Base.time_zone_aware_types -= [:timestamptz]
|
1719
1713
|
```
|
1720
1714
|
|
1721
|
-
*
|
1722
|
-
|
1723
|
-
* `Arel::Visitors::Dot` now renders a complete set of properties when visiting
|
1724
|
-
`Arel::Nodes::SelectCore`, `SelectStatement`, `InsertStatement`, `UpdateStatement`, and
|
1725
|
-
`DeleteStatement`, which fixes #42026. Previously, some properties were omitted.
|
1726
|
-
|
1727
|
-
*Mike Dalessio*
|
1715
|
+
*Alex Ghiculescu*
|
1728
1716
|
|
1729
|
-
*
|
1730
|
-
`DistinctOn`, `Else`, `Except`, `InfixOperation`, `Intersect`, `Lock`, `NotRegexp`, `Quoted`,
|
1731
|
-
`Regexp`, `UnaryOperation`, `Union`, `UnionAll`, `When`, and `With`. Previously, these node
|
1732
|
-
types caused an exception to be raised by `Arel::Visitors::Dot#accept`.
|
1717
|
+
* Add new `ActiveRecord::Base.generates_token_for` API.
|
1733
1718
|
|
1734
|
-
|
1719
|
+
Currently, `signed_id` fulfills the role of generating tokens for e.g.
|
1720
|
+
resetting a password. However, signed IDs cannot reflect record state, so
|
1721
|
+
if a token is intended to be single-use, it must be tracked in a database at
|
1722
|
+
least until it expires.
|
1735
1723
|
|
1736
|
-
|
1724
|
+
With `generates_token_for`, a token can embed data from a record. When
|
1725
|
+
using the token to fetch the record, the data from the token and the current
|
1726
|
+
data from the record will be compared. If the two do not match, the token
|
1727
|
+
will be treated as invalid, the same as if it had expired. For example:
|
1737
1728
|
|
1738
1729
|
```ruby
|
1739
|
-
|
1740
|
-
|
1730
|
+
class User < ActiveRecord::Base
|
1731
|
+
has_secure_password
|
1741
1732
|
|
1742
|
-
|
1733
|
+
generates_token_for :password_reset, expires_in: 15.minutes do
|
1734
|
+
# A password's BCrypt salt changes when the password is updated.
|
1735
|
+
# By embedding (part of) the salt in a token, the token will
|
1736
|
+
# expire when the password is updated.
|
1737
|
+
BCrypt::Password.new(password_digest).salt[-10..]
|
1738
|
+
end
|
1739
|
+
end
|
1743
1740
|
|
1744
|
-
|
1745
|
-
|
1746
|
-
```
|
1741
|
+
user = User.first
|
1742
|
+
token = user.generate_token_for(:password_reset)
|
1747
1743
|
|
1748
|
-
|
1744
|
+
User.find_by_token_for(:password_reset, token) # => user
|
1749
1745
|
|
1750
|
-
|
1746
|
+
user.update!(password: "new password")
|
1747
|
+
User.find_by_token_for(:password_reset, token) # => nil
|
1748
|
+
```
|
1751
1749
|
|
1752
|
-
|
1753
|
-
By doing this the autosave callback are made more consistent for
|
1754
|
-
all 3 cases: `has_many`, `has_one`, and `belongs_to`.
|
1750
|
+
*Jonathan Hefner*
|
1755
1751
|
|
1756
|
-
|
1752
|
+
* Optimize Active Record batching for whole table iterations.
|
1757
1753
|
|
1758
|
-
|
1754
|
+
Previously, `in_batches` got all the ids and constructed an `IN`-based query for each batch.
|
1755
|
+
When iterating over the whole tables, this approach is not optimal as it loads unneeded ids and
|
1756
|
+
`IN` queries with lots of items are slow.
|
1759
1757
|
|
1760
|
-
|
1761
|
-
|
1762
|
-
|
1758
|
+
Now, whole table iterations use range iteration (`id >= x AND id <= y`) by default which can make iteration
|
1759
|
+
several times faster. E.g., tested on a PostgreSQL table with 10 million records: querying (`253s` vs `30s`),
|
1760
|
+
updating (`288s` vs `124s`), deleting (`268s` vs `83s`).
|
1763
1761
|
|
1764
|
-
|
1762
|
+
Only whole table iterations use this style of iteration by default. You can disable this behavior by passing `use_ranges: false`.
|
1763
|
+
If you iterate over the table and the only condition is, e.g., `archived_at: nil` (and only a tiny fraction
|
1764
|
+
of the records are archived), it makes sense to opt in to this approach:
|
1765
1765
|
|
1766
1766
|
```ruby
|
1767
|
-
|
1768
|
-
|
1769
|
-
has_many :humans
|
1767
|
+
Project.where(archived_at: nil).in_batches(use_ranges: true) do |relation|
|
1768
|
+
# do something
|
1770
1769
|
end
|
1771
1770
|
```
|
1772
1771
|
|
1773
|
-
|
1774
|
-
|
1775
|
-
```
|
1776
|
-
SELECT "humans"."id" FROM "humans" WHERE "humans"."dog_id" = ? [["dog_id", 1]]
|
1777
|
-
SELECT "treats".* FROM "treats" WHERE "treats"."human_id" IN (?, ?, ?) [["human_id", 1], ["human_id", 2], ["human_id", 3]]
|
1778
|
-
```
|
1779
|
-
|
1780
|
-
*Eileen M. Uchitelle*, *Aaron Patterson*, *Lee Quarella*
|
1781
|
-
|
1782
|
-
* Add setting for enumerating column names in SELECT statements.
|
1772
|
+
See #45414 for more details.
|
1783
1773
|
|
1784
|
-
|
1785
|
-
change the result of wildcard `SELECT *` queries, which invalidates the result
|
1786
|
-
of cached prepared statements and raises a `PreparedStatementCacheExpired` error.
|
1787
|
-
|
1788
|
-
When enabled, Active Record will avoid wildcards and always include column names
|
1789
|
-
in `SELECT` queries, which will return consistent results and avoid prepared
|
1790
|
-
statement errors.
|
1774
|
+
*fatkodima*
|
1791
1775
|
|
1792
|
-
|
1776
|
+
* `.with` query method added. Construct common table expressions with ease and get `ActiveRecord::Relation` back.
|
1793
1777
|
|
1794
1778
|
```ruby
|
1795
|
-
|
1796
|
-
#
|
1779
|
+
Post.with(posts_with_comments: Post.where("comments_count > ?", 0))
|
1780
|
+
# => ActiveRecord::Relation
|
1781
|
+
# WITH posts_with_comments AS (SELECT * FROM posts WHERE (comments_count > 0)) SELECT * FROM posts
|
1797
1782
|
```
|
1798
1783
|
|
1799
|
-
|
1800
|
-
|
1801
|
-
```ruby
|
1802
|
-
# config/application.rb
|
1803
|
-
module MyApp
|
1804
|
-
class Application < Rails::Application
|
1805
|
-
config.active_record.enumerate_columns_in_select_statements = true
|
1806
|
-
end
|
1807
|
-
end
|
1784
|
+
*Vlado Cingel*
|
1808
1785
|
|
1809
|
-
|
1810
|
-
class Book < ApplicationRecord
|
1811
|
-
self.enumerate_columns_in_select_statements = true
|
1812
|
-
end
|
1813
|
-
```
|
1786
|
+
* Don't establish a new connection if an identical pool exists already.
|
1814
1787
|
|
1815
|
-
|
1816
|
-
Book.limit(5)
|
1817
|
-
# SELECT id, author_id, name, format, status, language, etc FROM books LIMIT 5
|
1818
|
-
```
|
1788
|
+
Previously, if `establish_connection` was called on a class that already had an established connection, the existing connection would be removed regardless of whether it was the same config. Now if a pool is found with the same values as the new connection, the existing connection will be returned instead of creating a new one.
|
1819
1789
|
|
1820
|
-
|
1790
|
+
This has a slight change in behavior if application code is depending on a new connection being established regardless of whether it's identical to an existing connection. If the old behavior is desirable, applications should call `ActiveRecord::Base#remove_connection` before establishing a new one. Calling `establish_connection` with a different config works the same way as it did previously.
|
1821
1791
|
|
1822
|
-
*
|
1792
|
+
*Eileen M. Uchitelle*
|
1823
1793
|
|
1824
|
-
|
1825
|
-
Book.upsert_all(
|
1826
|
-
[{ id: 1, status: 1 }, { id: 2, status: 1 }],
|
1827
|
-
on_duplicate: Arel.sql("status = GREATEST(books.status, EXCLUDED.status)")
|
1828
|
-
)
|
1829
|
-
```
|
1794
|
+
* Update `db:prepare` task to load schema when an uninitialized database exists, and dump schema after migrations.
|
1830
1795
|
|
1831
|
-
*
|
1796
|
+
*Ben Sheldon*
|
1832
1797
|
|
1833
|
-
*
|
1798
|
+
* Fix supporting timezone awareness for `tsrange` and `tstzrange` array columns.
|
1834
1799
|
|
1835
1800
|
```ruby
|
1836
|
-
|
1837
|
-
|
1838
|
-
|
1839
|
-
|
1840
|
-
|
1841
|
-
|
1842
|
-
)
|
1801
|
+
# In database migrations
|
1802
|
+
add_column :shops, :open_hours, :tsrange, array: true
|
1803
|
+
# In app config
|
1804
|
+
ActiveRecord::Base.time_zone_aware_types += [:tsrange]
|
1805
|
+
# In the code times are properly converted to app time zone
|
1806
|
+
Shop.create!(open_hours: [Time.current..8.hour.from_now])
|
1843
1807
|
```
|
1844
1808
|
|
1845
|
-
*
|
1809
|
+
*Wojciech Wnętrzak*
|
1846
1810
|
|
1847
|
-
*
|
1811
|
+
* Introduce strategy pattern for executing migrations.
|
1848
1812
|
|
1849
|
-
|
1813
|
+
By default, migrations will use a strategy object that delegates the method
|
1814
|
+
to the connection adapter. Consumers can implement custom strategy objects
|
1815
|
+
to change how their migrations run.
|
1850
1816
|
|
1851
|
-
*
|
1817
|
+
*Adrianna Chang*
|
1852
1818
|
|
1853
|
-
|
1854
|
-
are regular Active Record attributes backed by a column with
|
1855
|
-
the same name. The system will transparently encrypt these
|
1856
|
-
attributes before saving them into the database and will
|
1857
|
-
decrypt them when retrieving their values.
|
1819
|
+
* Add adapter option disallowing foreign keys
|
1858
1820
|
|
1821
|
+
This adds a new option to be added to `database.yml` which enables skipping
|
1822
|
+
foreign key constraints usage even if the underlying database supports them.
|
1859
1823
|
|
1860
|
-
|
1861
|
-
|
1862
|
-
|
1863
|
-
|
1864
|
-
|
1824
|
+
Usage:
|
1825
|
+
```yaml
|
1826
|
+
development:
|
1827
|
+
<<: *default
|
1828
|
+
database: storage/development.sqlite3
|
1829
|
+
foreign_keys: false
|
1865
1830
|
```
|
1866
1831
|
|
1867
|
-
|
1868
|
-
guide](https://edgeguides.rubyonrails.org/active_record_encryption.html).
|
1832
|
+
*Paulo Barros*
|
1869
1833
|
|
1870
|
-
|
1834
|
+
* Add configurable deprecation warning for singular associations
|
1871
1835
|
|
1872
|
-
|
1873
|
-
|
1836
|
+
This adds a deprecation warning when using the plural name of a singular associations in `where`.
|
1837
|
+
It is possible to opt into the new more performant behavior with `config.active_record.allow_deprecated_singular_associations_name = false`
|
1874
1838
|
|
1875
|
-
*
|
1839
|
+
*Adam Hess*
|
1876
1840
|
|
1877
|
-
*
|
1841
|
+
* Run transactional callbacks on the freshest instance to save a given
|
1842
|
+
record within a transaction.
|
1878
1843
|
|
1879
|
-
|
1880
|
-
|
1844
|
+
When multiple Active Record instances change the same record within a
|
1845
|
+
transaction, Rails runs `after_commit` or `after_rollback` callbacks for
|
1846
|
+
only one of them. `config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction`
|
1847
|
+
was added to specify how Rails chooses which instance receives the
|
1848
|
+
callbacks. The framework defaults were changed to use the new logic.
|
1881
1849
|
|
1882
|
-
|
1883
|
-
|
1850
|
+
When `config.active_record.run_commit_callbacks_on_first_saved_instances_in_transaction`
|
1851
|
+
is `true`, transactional callbacks are run on the first instance to save,
|
1852
|
+
even though its instance state may be stale.
|
1884
1853
|
|
1885
|
-
|
1886
|
-
|
1887
|
-
|
1854
|
+
When it is `false`, which is the new framework default starting with version
|
1855
|
+
7.1, transactional callbacks are run on the instances with the freshest
|
1856
|
+
instance state. Those instances are chosen as follows:
|
1888
1857
|
|
1889
|
-
|
1890
|
-
|
1891
|
-
|
1892
|
-
|
1858
|
+
- In general, run transactional callbacks on the last instance to save a
|
1859
|
+
given record within the transaction.
|
1860
|
+
- There are two exceptions:
|
1861
|
+
- If the record is created within the transaction, then updated by
|
1862
|
+
another instance, `after_create_commit` callbacks will be run on the
|
1863
|
+
second instance. This is instead of the `after_update_commit`
|
1864
|
+
callbacks that would naively be run based on that instance’s state.
|
1865
|
+
- If the record is destroyed within the transaction, then
|
1866
|
+
`after_destroy_commit` callbacks will be fired on the last destroyed
|
1867
|
+
instance, even if a stale instance subsequently performed an update
|
1868
|
+
(which will have affected 0 rows).
|
1893
1869
|
|
1894
|
-
*
|
1870
|
+
*Cameron Bothner and Mitch Vollebregt*
|
1895
1871
|
|
1896
|
-
*
|
1872
|
+
* Enable strict strings mode for `SQLite3Adapter`.
|
1897
1873
|
|
1898
|
-
|
1874
|
+
Configures SQLite with a strict strings mode, which disables double-quoted string literals.
|
1899
1875
|
|
1900
|
-
|
1901
|
-
|
1902
|
-
|
1876
|
+
SQLite has some quirks around double-quoted string literals.
|
1877
|
+
It first tries to consider double-quoted strings as identifier names, but if they don't exist
|
1878
|
+
it then considers them as string literals. Because of this, typos can silently go unnoticed.
|
1879
|
+
For example, it is possible to create an index for a non existing column.
|
1880
|
+
See [SQLite documentation](https://www.sqlite.org/quirks.html#double_quoted_string_literals_are_accepted) for more details.
|
1903
1881
|
|
1904
|
-
|
1905
|
-
create_table "postgresql_infinities" do |t|
|
1906
|
-
t.datetime "datetime"
|
1907
|
-
end
|
1882
|
+
If you don't want this behavior, you can disable it via:
|
1908
1883
|
|
1909
|
-
|
1910
|
-
|
1911
|
-
|
1884
|
+
```ruby
|
1885
|
+
# config/application.rb
|
1886
|
+
config.active_record.sqlite3_adapter_strict_strings_by_default = false
|
1912
1887
|
```
|
1913
1888
|
|
1914
|
-
|
1889
|
+
Fixes #27782.
|
1890
|
+
|
1891
|
+
*fatkodima*, *Jean Boussier*
|
1915
1892
|
|
1916
|
-
|
1893
|
+
* Resolve issue where a relation cache_version could be left stale.
|
1917
1894
|
|
1918
|
-
|
1895
|
+
Previously, when `reset` was called on a relation object it did not reset the cache_versions
|
1896
|
+
ivar. This led to a confusing situation where despite having the correct data the relation
|
1897
|
+
still reported a stale cache_version.
|
1919
1898
|
|
1920
|
-
|
1899
|
+
Usage:
|
1921
1900
|
|
1922
1901
|
```ruby
|
1923
|
-
|
1924
|
-
|
1925
|
-
end
|
1926
|
-
```
|
1902
|
+
developers = Developer.all
|
1903
|
+
developers.cache_version
|
1927
1904
|
|
1928
|
-
|
1905
|
+
Developer.update_all(updated_at: Time.now.utc + 1.second)
|
1929
1906
|
|
1930
|
-
|
1931
|
-
|
1932
|
-
|
1933
|
-
# => #<Book id: 1, status: "proposed", ...> (for mysql2 adapter)
|
1934
|
-
# => ActiveRecord::StatementInvalid: PG::InvalidTextRepresentation: ERROR: invalid input syntax for type integer: "prohibited" (for postgresql adapter)
|
1935
|
-
# => nil (for sqlite3 adapter)
|
1907
|
+
developers.cache_version # Stale cache_version
|
1908
|
+
developers.reset
|
1909
|
+
developers.cache_version # Returns the current correct cache_version
|
1936
1910
|
```
|
1937
1911
|
|
1938
|
-
|
1912
|
+
Fixes #45341.
|
1913
|
+
|
1914
|
+
*Austen Madden*
|
1915
|
+
|
1916
|
+
* Add support for exclusion constraints (PostgreSQL-only).
|
1939
1917
|
|
1940
1918
|
```ruby
|
1941
|
-
|
1942
|
-
|
1943
|
-
# => nil (for all adapters)
|
1919
|
+
add_exclusion_constraint :invoices, "daterange(start_date, end_date) WITH &&", using: :gist, name: "invoices_date_overlap"
|
1920
|
+
remove_exclusion_constraint :invoices, name: "invoices_date_overlap"
|
1944
1921
|
```
|
1945
1922
|
|
1946
|
-
|
1923
|
+
See PostgreSQL's [`CREATE TABLE ... EXCLUDE ...`](https://www.postgresql.org/docs/12/sql-createtable.html#SQL-CREATETABLE-EXCLUDE) documentation for more on exclusion constraints.
|
1947
1924
|
|
1948
|
-
*
|
1925
|
+
*Alex Robbin*
|
1949
1926
|
|
1950
|
-
|
1927
|
+
* `change_column_null` raises if a non-boolean argument is provided
|
1951
1928
|
|
1952
|
-
|
1953
|
-
|
1954
|
-
|
1955
|
-
name: George the Monkey
|
1956
|
-
fruits: apple
|
1929
|
+
Previously if you provided a non-boolean argument, `change_column_null` would
|
1930
|
+
treat it as truthy and make your column nullable. This could be surprising, so now
|
1931
|
+
the input must be either `true` or `false`.
|
1957
1932
|
|
1958
|
-
|
1959
|
-
|
1960
|
-
|
1933
|
+
```ruby
|
1934
|
+
change_column_null :table, :column, true # good
|
1935
|
+
change_column_null :table, :column, false # good
|
1936
|
+
change_column_null :table, :column, from: true, to: false # raises (previously this made the column nullable)
|
1961
1937
|
```
|
1962
1938
|
|
1963
|
-
If the join table (`fruit_monkeys`) contains `created_at` or `updated_at` columns,
|
1964
|
-
these will now be populated when loading the fixture. Previously, fixture loading
|
1965
|
-
would crash if these columns were required, and leave them as null otherwise.
|
1966
|
-
|
1967
1939
|
*Alex Ghiculescu*
|
1968
1940
|
|
1969
|
-
*
|
1941
|
+
* Enforce limit on table names length.
|
1970
1942
|
|
1971
|
-
|
1972
|
-
a single global thread pool for all queries. By default, Rails will set `async_query_executor`
|
1973
|
-
to `nil` which will not initialize any executor. If `load_async` is called and no executor
|
1974
|
-
has been configured, the query will be executed in the foreground.
|
1943
|
+
Fixes #45130.
|
1975
1944
|
|
1976
|
-
|
1977
|
-
`config.active_record.async_query_executor` to `:global_thread_pool` and optionally define
|
1978
|
-
`config.active_record.global_executor_concurrency`. This defaults to 4. For applications that want
|
1979
|
-
to have a thread pool for each database connection, `config.active_record.async_query_executor` can
|
1980
|
-
be set to `:multi_thread_pool`. The configuration for each thread pool is set in the database
|
1981
|
-
configuration.
|
1945
|
+
*fatkodima*
|
1982
1946
|
|
1983
|
-
|
1947
|
+
* Adjust the minimum MariaDB version for check constraints support.
|
1984
1948
|
|
1985
|
-
*
|
1949
|
+
*Eddie Lebow*
|
1986
1950
|
|
1987
|
-
|
1951
|
+
* Fix Hstore deserialize regression.
|
1988
1952
|
|
1989
|
-
|
1990
|
-
class Book < ActiveRecord::Base
|
1991
|
-
enum status: [ :proposed, :written ], _prefix: true, _scopes: false
|
1992
|
-
enum cover: [ :hard, :soft ], _suffix: true, _default: :hard
|
1993
|
-
end
|
1994
|
-
```
|
1953
|
+
*edsharp*
|
1995
1954
|
|
1996
|
-
|
1955
|
+
* Add validity for PostgreSQL indexes.
|
1997
1956
|
|
1998
1957
|
```ruby
|
1999
|
-
|
2000
|
-
|
2001
|
-
enum :cover, [ :hard, :soft ], suffix: true, default: :hard
|
2002
|
-
end
|
1958
|
+
connection.index_exists?(:users, :email, valid: true)
|
1959
|
+
connection.indexes(:users).select(&:valid?)
|
2003
1960
|
```
|
2004
1961
|
|
2005
|
-
*
|
1962
|
+
*fatkodima*
|
2006
1963
|
|
2007
|
-
*
|
1964
|
+
* Fix eager loading for models without primary keys.
|
2008
1965
|
|
2009
|
-
|
1966
|
+
*Anmol Chopra*, *Matt Lawrence*, and *Jonathan Hefner*
|
2010
1967
|
|
2011
|
-
|
2012
|
-
the query, it will be performed in the foreground.
|
1968
|
+
* Avoid validating a unique field if it has not changed and is backed by a unique index.
|
2013
1969
|
|
2014
|
-
|
2015
|
-
|
1970
|
+
Previously, when saving a record, Active Record will perform an extra query to check for the
|
1971
|
+
uniqueness of each attribute having a `uniqueness` validation, even if that attribute hasn't changed.
|
1972
|
+
If the database has the corresponding unique index, then this validation can never fail for persisted
|
1973
|
+
records, and we could safely skip it.
|
2016
1974
|
|
2017
|
-
|
2018
|
-
def index
|
2019
|
-
@categories = Category.some_complex_scope.load_async
|
2020
|
-
@posts = Post.some_complex_scope.load_async
|
2021
|
-
end
|
2022
|
-
```
|
1975
|
+
*fatkodima*
|
2023
1976
|
|
2024
|
-
|
2025
|
-
the main thread had to wait to access the result. This timing is useful to know
|
2026
|
-
whether or not it's worth to load the query asynchronously.
|
1977
|
+
* Stop setting `sql_auto_is_null`
|
2027
1978
|
|
2028
|
-
|
2029
|
-
DEBUG -- : Category Load (62.1ms) SELECT * FROM `categories` LIMIT 50
|
2030
|
-
DEBUG -- : ASYNC Post Load (64ms) (db time 126.1ms) SELECT * FROM `posts` LIMIT 100
|
2031
|
-
```
|
1979
|
+
Since version 5.5 the default has been off, we no longer have to manually turn it off.
|
2032
1980
|
|
2033
|
-
|
2034
|
-
waiting for the results, and the second set of parens with "db time" is how long
|
2035
|
-
the entire query took to execute.
|
1981
|
+
*Adam Hess*
|
2036
1982
|
|
2037
|
-
|
1983
|
+
* Fix `touch` to raise an error for readonly columns.
|
2038
1984
|
|
2039
|
-
*
|
1985
|
+
*fatkodima*
|
2040
1986
|
|
2041
|
-
|
2042
|
-
the resulting relation:
|
1987
|
+
* Add ability to ignore tables by regexp for SQL schema dumps.
|
2043
1988
|
|
2044
1989
|
```ruby
|
2045
|
-
|
2046
|
-
Post.excluding(post_one, post_two)
|
1990
|
+
ActiveRecord::SchemaDumper.ignore_tables = [/^_/]
|
2047
1991
|
```
|
2048
1992
|
|
2049
|
-
|
2050
|
-
|
2051
|
-
```ruby
|
2052
|
-
post.comments.excluding(comment)
|
2053
|
-
post.comments.excluding(comment_one, comment_two)
|
2054
|
-
```
|
1993
|
+
*fatkodima*
|
2055
1994
|
|
2056
|
-
|
2057
|
-
and `Post.where.not(id: [post_one.id, post_two.id])` (for a collection).
|
1995
|
+
* Avoid queries when performing calculations on contradictory relations.
|
2058
1996
|
|
2059
|
-
|
1997
|
+
Previously calculations would make a query even when passed a
|
1998
|
+
contradiction, such as `User.where(id: []).count`. We no longer perform a
|
1999
|
+
query in that scenario.
|
2060
2000
|
|
2061
|
-
|
2062
|
-
|
2001
|
+
This applies to the following calculations: `count`, `sum`, `average`,
|
2002
|
+
`minimum` and `maximum`
|
2063
2003
|
|
2064
|
-
|
2065
|
-
references an aliased select value would generate an error when
|
2066
|
-
#include? was called, due to an optimisation that would generate
|
2067
|
-
call #exists? on the relation instead, which effectively alters
|
2068
|
-
the select values of the query (and thus removes the aliased select
|
2069
|
-
values), but leaves the having clause intact. Because the having
|
2070
|
-
clause is then referencing an aliased column that is no longer
|
2071
|
-
present in the simplified query, an ActiveRecord::InvalidStatement
|
2072
|
-
error was raised.
|
2004
|
+
*Luan Vieira, John Hawthorn and Daniel Colson*
|
2073
2005
|
|
2074
|
-
|
2006
|
+
* Allow using aliased attributes with `insert_all`/`upsert_all`.
|
2075
2007
|
|
2076
2008
|
```ruby
|
2077
|
-
|
2078
|
-
|
2079
|
-
|
2080
|
-
|
2081
|
-
|
2009
|
+
class Book < ApplicationRecord
|
2010
|
+
alias_attribute :title, :name
|
2011
|
+
end
|
2012
|
+
|
2013
|
+
Book.insert_all [{ title: "Remote", author_id: 1 }], returning: :title
|
2082
2014
|
```
|
2083
2015
|
|
2084
|
-
|
2085
|
-
simplified #exists? query, which simply checks for the presence of
|
2086
|
-
a having clause.
|
2016
|
+
*fatkodima*
|
2087
2017
|
|
2088
|
-
|
2018
|
+
* Support encrypted attributes on columns with default db values.
|
2089
2019
|
|
2090
|
-
|
2020
|
+
This adds support for encrypted attributes defined on columns with default values.
|
2021
|
+
It will encrypt those values at creation time. Before, it would raise an
|
2022
|
+
error unless `config.active_record.encryption.support_unencrypted_data` was true.
|
2091
2023
|
|
2092
|
-
*
|
2093
|
-
without Rails knowledge (e.g., if app gets killed during long-running query or due to Rack::Timeout), app won't end
|
2094
|
-
up in perpetual crash state for being inconsistent with PostgreSQL.
|
2024
|
+
*Jorge Manrubia* and *Dima Fatko*
|
2095
2025
|
|
2096
|
-
|
2026
|
+
* Allow overriding `reading_request?` in `DatabaseSelector::Resolver`
|
2097
2027
|
|
2098
|
-
|
2028
|
+
The default implementation checks if a request is a `get?` or `head?`,
|
2029
|
+
but you can now change it to anything you like. If the method returns true,
|
2030
|
+
`Resolver#read` gets called meaning the request could be served by the
|
2031
|
+
replica database.
|
2099
2032
|
|
2100
|
-
|
2101
|
-
worked on certain types of queries. This change allows the `scoping` method to apply
|
2102
|
-
to all queries for a model in a block.
|
2033
|
+
*Alex Ghiculescu*
|
2103
2034
|
|
2104
|
-
|
2105
|
-
Post.where(blog_id: post.blog_id).scoping(all_queries: true) do
|
2106
|
-
post.update(title: "a post title") # adds `posts.blog_id = 1` to the query
|
2107
|
-
end
|
2108
|
-
```
|
2035
|
+
* Remove `ActiveRecord.legacy_connection_handling`.
|
2109
2036
|
|
2110
2037
|
*Eileen M. Uchitelle*
|
2111
2038
|
|
2112
|
-
* `
|
2113
|
-
(aliased as `ActiveRecord::Calculations.average`) will now use column-based
|
2114
|
-
type casting. This means that floating-point number columns will now be
|
2115
|
-
aggregated as `Float` and decimal columns will be aggregated as `BigDecimal`.
|
2039
|
+
* `rails db:schema:{dump,load}` now checks `ENV["SCHEMA_FORMAT"]` before config
|
2116
2040
|
|
2117
|
-
|
2118
|
-
|
2041
|
+
Since `rails db:structure:{dump,load}` was deprecated there wasn't a simple
|
2042
|
+
way to dump a schema to both SQL and Ruby formats. You can now do this with
|
2043
|
+
an environment variable. For example:
|
2119
2044
|
|
2120
|
-
```
|
2121
|
-
|
2122
|
-
|
2123
|
-
t.float "temperature"
|
2124
|
-
end
|
2045
|
+
```
|
2046
|
+
SCHEMA_FORMAT=sql rake db:schema:dump
|
2047
|
+
```
|
2125
2048
|
|
2126
|
-
|
2127
|
-
Measurement.average(:temperature).class
|
2128
|
-
# => BigDecimal
|
2049
|
+
*Alex Ghiculescu*
|
2129
2050
|
|
2130
|
-
|
2131
|
-
|
2132
|
-
|
2133
|
-
|
2051
|
+
* Fixed MariaDB default function support.
|
2052
|
+
|
2053
|
+
Defaults would be written wrong in "db/schema.rb" and not work correctly
|
2054
|
+
if using `db:schema:load`. Further more the function name would be
|
2055
|
+
added as string content when saving new records.
|
2134
2056
|
|
2135
|
-
|
2136
|
-
database adapter. This is not the case anymore. If you relied on that kind
|
2137
|
-
of magic, you now need to register your own `ActiveRecord::Type`
|
2138
|
-
(see `ActiveRecord::Attributes::ClassMethods` for documentation).
|
2057
|
+
*kaspernj*
|
2139
2058
|
|
2140
|
-
|
2059
|
+
* Add `active_record.destroy_association_async_batch_size` configuration
|
2141
2060
|
|
2142
|
-
|
2061
|
+
This allows applications to specify the maximum number of records that will
|
2062
|
+
be destroyed in a single background job by the `dependent: :destroy_async`
|
2063
|
+
association option. By default, the current behavior will remain the same:
|
2064
|
+
when a parent record is destroyed, all dependent records will be destroyed
|
2065
|
+
in a single background job. If the number of dependent records is greater
|
2066
|
+
than this configuration, the records will be destroyed in multiple
|
2067
|
+
background jobs.
|
2143
2068
|
|
2144
|
-
|
2145
|
-
a migration or schema. It takes a symbol which must correspond to one of the configured
|
2146
|
-
`NATIVE_DATABASE_TYPES`. The default is `:timestamp`, meaning `t.datetime` in a migration
|
2147
|
-
will create a "timestamp without time zone" column. To use "timestamp with time zone",
|
2148
|
-
change this to `:timestamptz` in an initializer.
|
2069
|
+
*Nick Holden*
|
2149
2070
|
|
2150
|
-
|
2071
|
+
* Fix `remove_foreign_key` with `:if_exists` option when foreign key actually exists.
|
2151
2072
|
|
2152
|
-
*
|
2073
|
+
*fatkodima*
|
2074
|
+
|
2075
|
+
* Remove `--no-comments` flag in structure dumps for PostgreSQL
|
2153
2076
|
|
2154
|
-
|
2077
|
+
This broke some apps that used custom schema comments. If you don't want
|
2078
|
+
comments in your structure dump, you can use:
|
2155
2079
|
|
2156
|
-
|
2157
|
-
|
2080
|
+
```ruby
|
2081
|
+
ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = ['--no-comments']
|
2082
|
+
```
|
2158
2083
|
|
2159
2084
|
*Alex Ghiculescu*
|
2160
2085
|
|
2161
|
-
*
|
2162
|
-
`ActiveRecord::Sanitization.disallow_raw_sql!`.
|
2086
|
+
* Reduce the memory footprint of fixtures accessors.
|
2163
2087
|
|
2164
|
-
|
2088
|
+
Until now fixtures accessors were eagerly defined using `define_method`.
|
2089
|
+
So the memory usage was directly dependent of the number of fixtures and
|
2090
|
+
test suites.
|
2165
2091
|
|
2166
|
-
|
2092
|
+
Instead fixtures accessors are now implemented with `method_missing`,
|
2093
|
+
so they incur much less memory and CPU overhead.
|
2167
2094
|
|
2168
|
-
|
2169
|
-
named `ApplicationRecord` can now set a specific class to be the `primary_abstract_class`.
|
2095
|
+
*Jean Boussier*
|
2170
2096
|
|
2171
|
-
|
2172
|
-
class PrimaryApplicationRecord
|
2173
|
-
self.primary_abstract_class
|
2174
|
-
end
|
2175
|
-
```
|
2097
|
+
* Fix `config.active_record.destroy_association_async_job` configuration
|
2176
2098
|
|
2177
|
-
|
2178
|
-
|
2179
|
-
|
2180
|
-
|
2181
|
-
|
2099
|
+
`config.active_record.destroy_association_async_job` should allow
|
2100
|
+
applications to specify the job that will be used to destroy associated
|
2101
|
+
records in the background for `has_many` associations with the
|
2102
|
+
`dependent: :destroy_async` option. Previously, that was ignored, which
|
2103
|
+
meant the default `ActiveRecord::DestroyAssociationAsyncJob` always
|
2104
|
+
destroyed records in the background.
|
2182
2105
|
|
2183
|
-
*
|
2106
|
+
*Nick Holden*
|
2184
2107
|
|
2185
|
-
*
|
2186
|
-
Now that Active Record supports multiple databases configuration,
|
2187
|
-
we need a way to pass specific flags for dump/load databases since
|
2188
|
-
the options are not the same for different adapters.
|
2189
|
-
We can use in the original way:
|
2108
|
+
* Fix `change_column_comment` to preserve column's AUTO_INCREMENT in the MySQL adapter
|
2190
2109
|
|
2191
|
-
|
2192
|
-
ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = ['--no-defaults', '--skip-add-drop-table']
|
2193
|
-
# or
|
2194
|
-
ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = '--no-defaults --skip-add-drop-table'
|
2195
|
-
```
|
2110
|
+
*fatkodima*
|
2196
2111
|
|
2197
|
-
|
2198
|
-
is the adapter
|
2112
|
+
* Fix quoting of `ActiveSupport::Duration` and `Rational` numbers in the MySQL adapter.
|
2199
2113
|
|
2200
|
-
|
2201
|
-
ActiveRecord::Tasks::DatabaseTasks.structure_dump_flags = {
|
2202
|
-
mysql2: ['--no-defaults', '--skip-add-drop-table'],
|
2203
|
-
postgres: '--no-tablespaces'
|
2204
|
-
}
|
2205
|
-
```
|
2114
|
+
*Kevin McPhillips*
|
2206
2115
|
|
2207
|
-
|
2116
|
+
* Allow column name with COLLATE (e.g., title COLLATE "C") as safe SQL string
|
2208
2117
|
|
2209
|
-
*
|
2210
|
-
adapter if the "url" protocol is "jdbc", "http", or "https". Previously only
|
2211
|
-
urls with the "jdbc" prefix were passed to the Active Record Adapter, others
|
2212
|
-
are assumed to be adapter specification urls.
|
2118
|
+
*Shugo Maeda*
|
2213
2119
|
|
2214
|
-
|
2120
|
+
* Permit underscores in the VERSION argument to database rake tasks.
|
2215
2121
|
|
2216
|
-
*
|
2122
|
+
*Eddie Lebow*
|
2217
2123
|
|
2218
|
-
*
|
2124
|
+
* Reversed the order of `INSERT` statements in `structure.sql` dumps
|
2219
2125
|
|
2220
|
-
This
|
2221
|
-
|
2126
|
+
This should decrease the likelihood of merge conflicts. New migrations
|
2127
|
+
will now be added at the top of the list.
|
2222
2128
|
|
2223
|
-
|
2224
|
-
|
2225
|
-
has_many :bookmarks
|
2226
|
-
has_many :articles, strict_loading: true
|
2227
|
-
end
|
2129
|
+
For existing apps, there will be a large diff the next time `structure.sql`
|
2130
|
+
is generated.
|
2228
2131
|
|
2229
|
-
|
2230
|
-
user.articles # => ActiveRecord::StrictLoadingViolationError
|
2231
|
-
user.bookmarks # => #<ActiveRecord::Associations::CollectionProxy>
|
2132
|
+
*Alex Ghiculescu*, *Matt Larraz*
|
2232
2133
|
|
2233
|
-
|
2234
|
-
user.bookmarks # => ActiveRecord::StrictLoadingViolationError
|
2134
|
+
* Fix PG.connect keyword arguments deprecation warning on ruby 2.7
|
2235
2135
|
|
2236
|
-
|
2237
|
-
user.bookmarks # => #<ActiveRecord::Associations::CollectionProxy>
|
2238
|
-
user.articles.strict_loading!(false) # => #<ActiveRecord::Associations::CollectionProxy>
|
2239
|
-
```
|
2136
|
+
Fixes #44307.
|
2240
2137
|
|
2241
|
-
*
|
2138
|
+
*Nikita Vasilevsky*
|
2242
2139
|
|
2243
|
-
*
|
2244
|
-
presence of exactly one record.
|
2140
|
+
* Fix dropping DB connections after serialization failures and deadlocks.
|
2245
2141
|
|
2246
|
-
|
2247
|
-
|
2248
|
-
|
2142
|
+
Prior to 6.1.4, serialization failures and deadlocks caused rollbacks to be
|
2143
|
+
issued for both real transactions and savepoints. This breaks MySQL which
|
2144
|
+
disallows rollbacks of savepoints following a deadlock.
|
2249
2145
|
|
2250
|
-
|
2251
|
-
|
2252
|
-
# => ActiveRecord::RecordNotFound (if no Product with given price)
|
2253
|
-
# => #<Product ...> (if one Product with given price)
|
2254
|
-
# => ActiveRecord::SoleRecordExceeded (if more than one Product with given price)
|
2146
|
+
6.1.4 removed these rollbacks, for both transactions and savepoints, causing
|
2147
|
+
the DB connection to be left in an unknown state and thus discarded.
|
2255
2148
|
|
2256
|
-
|
2257
|
-
# as above
|
2258
|
-
```
|
2149
|
+
These rollbacks are now restored, except for savepoints on MySQL.
|
2259
2150
|
|
2260
|
-
*
|
2151
|
+
*Thomas Morgan*
|
2261
2152
|
|
2262
|
-
*
|
2153
|
+
* Make `ActiveRecord::ConnectionPool` Fiber-safe
|
2263
2154
|
|
2264
|
-
|
2155
|
+
When `ActiveSupport::IsolatedExecutionState.isolation_level` is set to `:fiber`,
|
2156
|
+
the connection pool now supports multiple Fibers from the same Thread checking
|
2157
|
+
out connections from the pool.
|
2158
|
+
|
2159
|
+
*Alex Matchneer*
|
2160
|
+
|
2161
|
+
* Add `update_attribute!` to `ActiveRecord::Persistence`
|
2162
|
+
|
2163
|
+
Similar to `update_attribute`, but raises `ActiveRecord::RecordNotSaved` when a `before_*` callback throws `:abort`.
|
2265
2164
|
|
2266
2165
|
```ruby
|
2267
|
-
class
|
2268
|
-
|
2269
|
-
|
2166
|
+
class Topic < ActiveRecord::Base
|
2167
|
+
before_save :check_title
|
2168
|
+
|
2169
|
+
def check_title
|
2170
|
+
throw(:abort) if title == "abort"
|
2270
2171
|
end
|
2271
2172
|
end
|
2272
2173
|
|
2273
|
-
|
2274
|
-
|
2275
|
-
|
2276
|
-
|
2277
|
-
|
2174
|
+
topic = Topic.create(title: "Test Title")
|
2175
|
+
# #=> #<Topic title: "Test Title">
|
2176
|
+
topic.update_attribute!(:title, "Another Title")
|
2177
|
+
# #=> #<Topic title: "Another Title">
|
2178
|
+
topic.update_attribute!(:title, "abort")
|
2179
|
+
# raises ActiveRecord::RecordNotSaved
|
2278
2180
|
```
|
2279
2181
|
|
2280
|
-
|
2182
|
+
*Drew Tempelmeyer*
|
2281
2183
|
|
2282
|
-
|
2184
|
+
* Avoid loading every record in `ActiveRecord::Relation#pretty_print`
|
2283
2185
|
|
2284
|
-
|
2186
|
+
```ruby
|
2187
|
+
# Before
|
2188
|
+
pp Foo.all # Loads the whole table.
|
2189
|
+
|
2190
|
+
# After
|
2191
|
+
pp Foo.all # Shows 10 items and an ellipsis.
|
2192
|
+
```
|
2285
2193
|
|
2286
|
-
*
|
2194
|
+
*Ulysse Buonomo*
|
2287
2195
|
|
2288
|
-
|
2289
|
-
`singular_id` defined by it does not work when the foreign_key does
|
2290
|
-
not end with `id`. This change fixes it by taking into account
|
2291
|
-
`primary_key` and `foreign_key` in the options.
|
2196
|
+
* Change `QueryMethods#in_order_of` to drop records not listed in values.
|
2292
2197
|
|
2293
|
-
|
2198
|
+
`in_order_of` now filters down to the values provided, to match the behavior of the `Enumerable` version.
|
2294
2199
|
|
2295
|
-
*
|
2200
|
+
*Kevin Newton*
|
2296
2201
|
|
2297
|
-
|
2298
|
-
class User
|
2299
|
-
scope :active, -> { where(accepted: true, locked: false) }
|
2300
|
-
end
|
2202
|
+
* Allow named expression indexes to be revertible.
|
2301
2203
|
|
2302
|
-
|
2303
|
-
# ... WHERE `accepted` = 1 AND `locked` = 0
|
2204
|
+
Previously, the following code would raise an error in a reversible migration executed while rolling back, due to the index name not being used in the index removal.
|
2304
2205
|
|
2305
|
-
|
2306
|
-
|
2206
|
+
```ruby
|
2207
|
+
add_index(:settings, "(data->'property')", using: :gin, name: :index_settings_data_property)
|
2307
2208
|
```
|
2308
2209
|
|
2309
|
-
|
2210
|
+
Fixes #43331.
|
2211
|
+
|
2212
|
+
*Oliver Günther*
|
2310
2213
|
|
2311
|
-
*
|
2214
|
+
* Fix incorrect argument in PostgreSQL structure dump tasks.
|
2312
2215
|
|
2313
|
-
|
2314
|
-
to throw an error saying :polymorphic would not be a valid option.
|
2216
|
+
Updating the `--no-comment` argument added in Rails 7 to the correct `--no-comments` argument.
|
2315
2217
|
|
2316
|
-
*
|
2218
|
+
*Alex Dent*
|
2317
2219
|
|
2318
|
-
*
|
2220
|
+
* Fix migration compatibility to create SQLite references/belongs_to column as integer when migration version is 6.0.
|
2319
2221
|
|
2320
|
-
|
2222
|
+
Reference/belongs_to in migrations with version 6.0 were creating columns as
|
2223
|
+
bigint instead of integer for the SQLite Adapter.
|
2321
2224
|
|
2322
|
-
*
|
2225
|
+
*Marcelo Lauxen*
|
2323
2226
|
|
2324
|
-
|
2325
|
-
and the index name should be specified explicitly. Now, the index name is inferred
|
2326
|
-
automatically.
|
2227
|
+
* Fix `QueryMethods#in_order_of` to handle empty order list.
|
2327
2228
|
|
2328
2229
|
```ruby
|
2329
|
-
|
2230
|
+
Post.in_order_of(:id, []).to_a
|
2330
2231
|
```
|
2331
2232
|
|
2332
|
-
|
2333
|
-
|
2334
|
-
*fatkodima*
|
2335
|
-
|
2336
|
-
* Only warn about negative enums if a positive form that would cause conflicts exists.
|
2337
|
-
|
2338
|
-
Fixes #39065.
|
2339
|
-
|
2340
|
-
*Alex Ghiculescu*
|
2233
|
+
Also more explicitly set the column as secondary order, so that any other
|
2234
|
+
value is still ordered.
|
2341
2235
|
|
2342
|
-
*
|
2236
|
+
*Jean Boussier*
|
2343
2237
|
|
2344
|
-
|
2238
|
+
* Fix quoting of column aliases generated by calculation methods.
|
2345
2239
|
|
2346
|
-
|
2240
|
+
Since the alias is derived from the table name, we can't assume the result
|
2241
|
+
is a valid identifier.
|
2347
2242
|
|
2348
2243
|
```ruby
|
2349
|
-
class
|
2350
|
-
|
2244
|
+
class Test < ActiveRecord::Base
|
2245
|
+
self.table_name = '1abc'
|
2351
2246
|
end
|
2247
|
+
Test.group(:id).count
|
2248
|
+
# syntax error at or near "1" (ActiveRecord::StatementInvalid)
|
2249
|
+
# LINE 1: SELECT COUNT(*) AS count_all, "1abc"."id" AS 1abc_id FROM "1...
|
2352
2250
|
```
|
2353
2251
|
|
2354
|
-
*
|
2252
|
+
*Jean Boussier*
|
2355
2253
|
|
2356
|
-
* Add `
|
2254
|
+
* Add `authenticate_by` when using `has_secure_password`.
|
2357
2255
|
|
2358
|
-
|
2359
|
-
|
2360
|
-
account.users.joins(:contact).where.not(contact_id: nil)
|
2256
|
+
`authenticate_by` is intended to replace code like the following, which
|
2257
|
+
returns early when a user with a matching email is not found:
|
2361
2258
|
|
2362
|
-
|
2363
|
-
|
2259
|
+
```ruby
|
2260
|
+
User.find_by(email: "...")&.authenticate("...")
|
2364
2261
|
```
|
2365
2262
|
|
2366
|
-
|
2263
|
+
Such code is vulnerable to timing-based enumeration attacks, wherein an
|
2264
|
+
attacker can determine if a user account with a given email exists. After
|
2265
|
+
confirming that an account exists, the attacker can try passwords associated
|
2266
|
+
with that email address from other leaked databases, in case the user
|
2267
|
+
re-used a password across multiple sites (a common practice). Additionally,
|
2268
|
+
knowing an account email address allows the attacker to attempt a targeted
|
2269
|
+
phishing ("spear phishing") attack.
|
2367
2270
|
|
2368
|
-
|
2271
|
+
`authenticate_by` addresses the vulnerability by taking the same amount of
|
2272
|
+
time regardless of whether a user with a matching email is found:
|
2369
2273
|
|
2370
|
-
|
2371
|
-
|
2274
|
+
```ruby
|
2275
|
+
User.authenticate_by(email: "...", password: "...")
|
2276
|
+
```
|
2372
2277
|
|
2373
|
-
*
|
2278
|
+
*Jonathan Hefner*
|
2374
2279
|
|
2375
2280
|
|
2376
|
-
Please check [
|
2281
|
+
Please check [7-0-stable](https://github.com/rails/rails/blob/7-0-stable/activerecord/CHANGELOG.md) for previous changes.
|