From 720f6b1ec21fb112522e664f86dfc28c5edbaefa Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Rafael=20Mendon=C3=A7a=20Fran=C3=A7a?= Date: Thu, 7 Oct 2021 21:09:02 +0000 Subject: [PATCH] Remove refenrence to destroy_all_in_batches config This feature was reverted. --- guides/source/configuring.md | 6 ------ 1 file changed, 6 deletions(-) diff --git a/guides/source/configuring.md b/guides/source/configuring.md index bd5e814ee7..a513f319bf 100644 --- a/guides/source/configuring.md +++ b/guides/source/configuring.md @@ -732,12 +732,6 @@ Allows specifying the Active Job queue to use for destroy jobs. When this option When true, will always include column names in `SELECT` statements, and avoid wildcard `SELECT * FROM ...` queries. This avoids prepared statement cache errors when adding columns to a PostgreSQL database for example. Defaults to `false`. -#### `config.active_record.destroy_all_in_batches` - -Ensures `ActiveRecord::Relation#destroy_all` performs the record's deletion in -batches. `ActiveRecord::Relation#destroy_all` will no longer return the collection -of the deleted records after enabling this option. - #### `config.active_record.verify_foreign_keys_for_fixtures` Ensures all foreign key constraints are valid after fixtures are loaded in tests. Supported by PostgreSQL and SQLite only. Defaults to `false`.