strong_migrations 1.8.0 → 2.3.0

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: f6462f35144a092664bb7456db2a1ad402695c6b5b1ba7001c1f1f977ea88d3e
-  data.tar.gz: fc71c84ae237b8dbbd3413af7b47ab4fa9962dcbbdd6b3e99b9edd816d3ae009
+  metadata.gz: 3538811c535186c2757c2e92a56ec753c77842a99728a727aabe323dd8852182
+  data.tar.gz: 6d33a69582e57e3035d7ef540894ce0020957aef8d4e081e693552615ac9af8b
 SHA512:
-  metadata.gz: 2c4e5bf21e4bb42046fc2d4a530e40d9fc5f843db7c630779789934ec1a47965398e6b637707dc6a7106eb339ef26231ecfea73c312fd9a04f66f96504fcdc6a
-  data.tar.gz: 542be70454fa38a8ad0c29e6bedcf670e54323ff8d9ae8f5eb59756476bbbaca6092a15f09c54163714e3db83261a8554e1fe51b00da8ad05ca7667a4612c3c8
+  metadata.gz: 50a4b8ea0d0677bc0d5a3fa740f9f2e8b00acee0e673abaf7197c0c89540165ecb0cad913ed4244b61e3ac23342d4c44b8209991dea3841ee6dd7d7fbef827e3
+  data.tar.gz: fd6d44273d6365ca9e33a246e072a24da93191bfc73b5d425df22c0b3b6523ce218d6aa6360dd6a8fcbcf88b5a06bf41c7221ccdceb69f26b734510cd38876f7

data/CHANGELOG.md

@@ -1,3 +1,41 @@
+## 2.3.0 (2025-04-03)
+
+- Added check for `change_column` for columns with check constraints with Postgres
+
+## 2.2.1 (2025-03-21)
+
+- Added support for `change_column_null` with default value with `safe_by_default` option
+- Improved backfill instructions
+- Fixed `safe_by_default` applying to migrations before `start_after`
+
+## 2.2.0 (2025-02-01)
+
+- Fixed constraint name for long table and column names with `change_column_null`
+- Dropped support for Active Record < 7
+
+## 2.1.0 (2024-11-08)
+
+- Added `skip_database` method
+- Added experimental `remove_invalid_indexes` option
+- Added warning for unsupported adapters
+- Improved output for `db:forward`, `db:rollback`, `db:migrate:up`, and `db:migrate:down`
+- Made operations more retriable with `safe_by_default`
+
+## 2.0.2 (2024-10-30)
+
+- Fixed migrations not running with Active Record 8 rc2
+
+## 2.0.1 (2024-10-14)
+
+- Fixed issue with `alphabetize_schema` and virtual columns
+
+## 2.0.0 (2024-06-28)
+
+- Improved install generator for Trilogy
+- Fixed charset check for MariaDB 11.4
+- Dropped support for Ruby < 3.1 and Active Record < 6.1
+- Dropped support for Postgres < 12, MySQL < 8.0, and MariaDB < 10.5
+
 ## 1.8.0 (2024-03-11)
 
 - Added check for `add_column` with auto-incrementing columns

data/LICENSE.txt

@@ -1,4 +1,4 @@
-Copyright (c) 2013 Bob Remeika and David Waller, 2015-2024 Andrew Kane
+Copyright (c) 2013 Bob Remeika and David Waller, 2015-2025 Andrew Kane
 
 MIT License
 

data/README.md

@@ -43,7 +43,7 @@ end
 
 Deploy the code, then wrap this step in a safety_assured { ... } block.
 
-class RemoveColumn < ActiveRecord::Migration[7.1]
+class RemoveColumn < ActiveRecord::Migration[8.0]
   def change
     safety_assured { remove_column :users, :name }
   end
@@ -64,7 +64,7 @@ Potentially dangerous operations:
 - [renaming a column](#renaming-a-column)
 - [renaming a table](#renaming-a-table)
 - [creating a table with the force option](#creating-a-table-with-the-force-option)
-- [adding an auto-incrementing column](#adding-an-auto-incrementing-column) [unreleased]
+- [adding an auto-incrementing column](#adding-an-auto-incrementing-column)
 - [adding a stored generated column](#adding-a-stored-generated-column)
 - [adding a check constraint](#adding-a-check-constraint)
 - [executing SQL directly](#executing-SQL-directly)
@@ -79,7 +79,7 @@ Postgres-specific checks:
 - [adding an exclusion constraint](#adding-an-exclusion-constraint)
 - [adding a json column](#adding-a-json-column)
 - [setting NOT NULL on an existing column](#setting-not-null-on-an-existing-column)
-- [adding a column with a default value](#adding-a-column-with-a-default-value)
+- [adding a column with a volatile default value](#adding-a-column-with-a-volatile-default-value)
 
 Config-specific checks:
 
@@ -98,7 +98,7 @@ You can also add [custom checks](#custom-checks) or [disable specific checks](#d
 Active Record caches database columns at runtime, so if you drop a column, it can cause exceptions until your app reboots.
 
 ```ruby
-class RemoveSomeColumnFromUsers < ActiveRecord::Migration[7.1]
+class RemoveSomeColumnFromUsers < ActiveRecord::Migration[8.0]
   def change
     remove_column :users, :some_column
   end
@@ -119,7 +119,7 @@ end
 3. Write a migration to remove the column (wrap in `safety_assured` block)
 
   ```ruby
-  class RemoveSomeColumnFromUsers < ActiveRecord::Migration[7.1]
+  class RemoveSomeColumnFromUsers < ActiveRecord::Migration[8.0]
     def change
       safety_assured { remove_column :users, :some_column }
     end
@@ -136,7 +136,7 @@ end
 Changing the type of a column causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
 
 ```ruby
-class ChangeSomeColumnType < ActiveRecord::Migration[7.1]
+class ChangeSomeColumnType < ActiveRecord::Migration[8.0]
   def change
     change_column :users, :some_column, :new_type
   end
@@ -182,7 +182,7 @@ A safer approach is to:
 Renaming a column that’s in use will cause errors in your application.
 
 ```ruby
-class RenameSomeColumn < ActiveRecord::Migration[7.1]
+class RenameSomeColumn < ActiveRecord::Migration[8.0]
   def change
     rename_column :users, :some_column, :new_name
   end
@@ -207,7 +207,7 @@ A safer approach is to:
 Renaming a table that’s in use will cause errors in your application.
 
 ```ruby
-class RenameUsersToCustomers < ActiveRecord::Migration[7.1]
+class RenameUsersToCustomers < ActiveRecord::Migration[8.0]
   def change
     rename_table :users, :customers
   end
@@ -232,7 +232,7 @@ A safer approach is to:
 The `force` option can drop an existing table.
 
 ```ruby
-class CreateUsers < ActiveRecord::Migration[7.1]
+class CreateUsers < ActiveRecord::Migration[8.0]
   def change
     create_table :users, force: true do |t|
       # ...
@@ -246,7 +246,7 @@ end
 Create tables without the `force` option.
 
 ```ruby
-class CreateUsers < ActiveRecord::Migration[7.1]
+class CreateUsers < ActiveRecord::Migration[8.0]
   def change
     create_table :users do |t|
       # ...
@@ -264,7 +264,7 @@ If you intend to drop an existing table, run `drop_table` first.
 Adding an auto-incrementing column (`serial`/`bigserial` in Postgres and `AUTO_INCREMENT` in MySQL and MariaDB) causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
 
 ```ruby
-class AddIdToCitiesUsers < ActiveRecord::Migration[7.1]
+class AddIdToCitiesUsers < ActiveRecord::Migration[8.0]
   def change
     add_column :cities_users, :id, :primary_key
   end
@@ -284,7 +284,7 @@ Create a new table and migrate the data with the same steps as [renaming a table
 Adding a stored generated column causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres, and writes are blocked in MySQL and MariaDB.
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[8.0]
   def change
     add_column :users, :some_column, :virtual, type: :string, as: "...", stored: true
   end
@@ -304,7 +304,7 @@ Add a non-generated column and use callbacks or triggers instead (or a virtual g
 Adding a check constraint blocks reads and writes in Postgres and blocks writes in MySQL and MariaDB while every row is checked.
 
 ```ruby
-class AddCheckConstraint < ActiveRecord::Migration[7.1]
+class AddCheckConstraint < ActiveRecord::Migration[8.0]
   def change
     add_check_constraint :users, "price > 0", name: "price_check"
   end
@@ -316,7 +316,7 @@ end
 Add the check constraint without validating existing rows:
 
 ```ruby
-class AddCheckConstraint < ActiveRecord::Migration[7.1]
+class AddCheckConstraint < ActiveRecord::Migration[8.0]
   def change
     add_check_constraint :users, "price > 0", name: "price_check", validate: false
   end
@@ -326,7 +326,7 @@ end
 Then validate them in a separate migration.
 
 ```ruby
-class ValidateCheckConstraint < ActiveRecord::Migration[7.1]
+class ValidateCheckConstraint < ActiveRecord::Migration[8.0]
   def change
     validate_check_constraint :users, name: "price_check"
   end
@@ -342,7 +342,7 @@ end
 Strong Migrations can’t ensure safety for raw SQL statements. Make really sure that what you’re doing is safe, then use:
 
 ```ruby
-class ExecuteSQL < ActiveRecord::Migration[7.1]
+class ExecuteSQL < ActiveRecord::Migration[8.0]
   def change
     safety_assured { execute "..." }
   end
@@ -351,12 +351,14 @@ end
 
 ### Backfilling data
 
+Note: Strong Migrations does not detect dangerous backfills.
+
 #### Bad
 
 Active Record creates a transaction around each migration, and backfilling in the same transaction that alters a table keeps the table locked for the [duration of the backfill](https://wework.github.io/data/2015/11/05/add-columns-with-default-values-to-large-tables-in-rails-postgres/).
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[8.0]
   def change
     add_column :users, :some_column, :text
     User.update_all some_column: "default_value"
@@ -371,18 +373,20 @@ Also, running a single query to update data can cause issues for large tables.
 There are three keys to backfilling safely: batching, throttling, and running it outside a transaction. Use the Rails console or a separate migration with `disable_ddl_transaction!`.
 
 ```ruby
-class BackfillSomeColumn < ActiveRecord::Migration[7.1]
+class BackfillSomeColumn < ActiveRecord::Migration[8.0]
   disable_ddl_transaction!
 
   def up
-    User.unscoped.in_batches do |relation|
-      relation.update_all some_column: "default_value"
+    User.unscoped.in_batches(of: 10000) do |relation|
+      relation.where(some_column: nil).update_all some_column: "default_value"
       sleep(0.01) # throttle
     end
   end
 end
 ```
 
+Note: If backfilling with a method other than `update_all`, use `User.reset_column_information` to ensure the model has up-to-date column information.
+
 ### Adding an index non-concurrently
 
 :turtle: Safe by default available
@@ -392,7 +396,7 @@ end
 In Postgres, adding an index non-concurrently blocks writes.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[8.0]
   def change
     add_index :users, :some_column
   end
@@ -404,7 +408,7 @@ end
 Add indexes concurrently.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[8.0]
   disable_ddl_transaction!
 
   def change
@@ -430,7 +434,7 @@ rails g index table column
 Rails adds an index non-concurrently to references by default, which blocks writes in Postgres.
 
 ```ruby
-class AddReferenceToUsers < ActiveRecord::Migration[7.1]
+class AddReferenceToUsers < ActiveRecord::Migration[8.0]
   def change
     add_reference :users, :city
   end
@@ -442,7 +446,7 @@ end
 Make sure the index is added concurrently.
 
 ```ruby
-class AddReferenceToUsers < ActiveRecord::Migration[7.1]
+class AddReferenceToUsers < ActiveRecord::Migration[8.0]
   disable_ddl_transaction!
 
   def change
@@ -460,7 +464,7 @@ end
 In Postgres, adding a foreign key blocks writes on both tables.
 
 ```ruby
-class AddForeignKeyOnUsers < ActiveRecord::Migration[7.1]
+class AddForeignKeyOnUsers < ActiveRecord::Migration[8.0]
   def change
     add_foreign_key :users, :orders
   end
@@ -470,7 +474,7 @@ end
 or
 
 ```ruby
-class AddReferenceToUsers < ActiveRecord::Migration[7.1]
+class AddReferenceToUsers < ActiveRecord::Migration[8.0]
   def change
     add_reference :users, :order, foreign_key: true
   end
@@ -482,7 +486,7 @@ end
 Add the foreign key without validating existing rows:
 
 ```ruby
-class AddForeignKeyOnUsers < ActiveRecord::Migration[7.1]
+class AddForeignKeyOnUsers < ActiveRecord::Migration[8.0]
   def change
     add_foreign_key :users, :orders, validate: false
   end
@@ -492,7 +496,7 @@ end
 Then validate them in a separate migration.
 
 ```ruby
-class ValidateForeignKeyOnUsers < ActiveRecord::Migration[7.1]
+class ValidateForeignKeyOnUsers < ActiveRecord::Migration[8.0]
   def change
     validate_foreign_key :users, :orders
   end
@@ -506,7 +510,7 @@ end
 In Postgres, adding a unique constraint creates a unique index, which blocks reads and writes.
 
 ```ruby
-class AddUniqueContraint < ActiveRecord::Migration[7.1]
+class AddUniqueConstraint < ActiveRecord::Migration[8.0]
   def change
     add_unique_constraint :users, :some_column
   end
@@ -518,7 +522,7 @@ end
 Create a unique index concurrently, then use it for the constraint.
 
 ```ruby
-class AddUniqueContraint < ActiveRecord::Migration[7.1]
+class AddUniqueConstraint < ActiveRecord::Migration[8.0]
   disable_ddl_transaction!
 
   def up
@@ -539,7 +543,7 @@ end
 In Postgres, adding an exclusion constraint blocks reads and writes while every row is checked.
 
 ```ruby
-class AddExclusionContraint < ActiveRecord::Migration[7.1]
+class AddExclusionConstraint < ActiveRecord::Migration[8.0]
   def change
     add_exclusion_constraint :users, "number WITH =", using: :gist
   end
@@ -557,7 +561,7 @@ end
 In Postgres, there’s no equality operator for the `json` column type, which can cause errors for existing `SELECT DISTINCT` queries in your application.
 
 ```ruby
-class AddPropertiesToUsers < ActiveRecord::Migration[7.1]
+class AddPropertiesToUsers < ActiveRecord::Migration[8.0]
   def change
     add_column :users, :properties, :json
   end
@@ -569,7 +573,7 @@ end
 Use `jsonb` instead.
 
 ```ruby
-class AddPropertiesToUsers < ActiveRecord::Migration[7.1]
+class AddPropertiesToUsers < ActiveRecord::Migration[8.0]
   def change
     add_column :users, :properties, :jsonb
   end
@@ -585,7 +589,7 @@ end
 In Postgres, setting `NOT NULL` on an existing column blocks reads and writes while every row is checked.
 
 ```ruby
-class SetSomeColumnNotNull < ActiveRecord::Migration[7.1]
+class SetSomeColumnNotNull < ActiveRecord::Migration[8.0]
   def change
     change_column_null :users, :some_column, false
   end
@@ -596,87 +600,54 @@ end
 
 Instead, add a check constraint.
 
-For Rails 6.1+, use:
-
 ```ruby
-class SetSomeColumnNotNull < ActiveRecord::Migration[7.1]
+class SetSomeColumnNotNull < ActiveRecord::Migration[8.0]
   def change
     add_check_constraint :users, "some_column IS NOT NULL", name: "users_some_column_null", validate: false
   end
 end
 ```
 
-For Rails < 6.1, use:
-
-```ruby
-class SetSomeColumnNotNull < ActiveRecord::Migration[6.0]
-  def change
-    safety_assured do
-      execute 'ALTER TABLE "users" ADD CONSTRAINT "users_some_column_null" CHECK ("some_column" IS NOT NULL) NOT VALID'
-    end
-  end
-end
-```
-
-Then validate it in a separate migration. A `NOT NULL` check constraint is [functionally equivalent](https://medium.com/doctolib/adding-a-not-null-constraint-on-pg-faster-with-minimal-locking-38b2c00c4d1c) to setting `NOT NULL` on the column (but it won’t show up in `schema.rb` in Rails < 6.1). In Postgres 12+, once the check constraint is validated, you can safely set `NOT NULL` on the column and drop the check constraint.
-
-For Rails 6.1+, use:
+Then validate it in a separate migration. Once the check constraint is validated, you can safely set `NOT NULL` on the column and drop the check constraint.
 
 ```ruby
-class ValidateSomeColumnNotNull < ActiveRecord::Migration[7.1]
-  def change
+class ValidateSomeColumnNotNull < ActiveRecord::Migration[8.0]
+  def up
     validate_check_constraint :users, name: "users_some_column_null"
-
-    # in Postgres 12+, you can then safely set NOT NULL on the column
     change_column_null :users, :some_column, false
     remove_check_constraint :users, name: "users_some_column_null"
   end
-end
-```
-
-For Rails < 6.1, use:
-
-```ruby
-class ValidateSomeColumnNotNull < ActiveRecord::Migration[6.0]
-  def change
-    safety_assured do
-      execute 'ALTER TABLE "users" VALIDATE CONSTRAINT "users_some_column_null"'
-    end
 
-    # in Postgres 12+, you can then safely set NOT NULL on the column
-    change_column_null :users, :some_column, false
-    safety_assured do
-      execute 'ALTER TABLE "users" DROP CONSTRAINT "users_some_column_null"'
-    end
+  def down
+    add_check_constraint :users, "some_column IS NOT NULL", name: "users_some_column_null", validate: false
+    change_column_null :users, :some_column, true
   end
 end
 ```
 
-### Adding a column with a default value
+### Adding a column with a volatile default value
 
 #### Bad
 
-In earlier versions of Postgres, adding a column with a default value to an existing table causes the entire table to be rewritten. During this time, reads and writes are blocked in Postgres.
+Adding a column with a volatile default value to an existing table causes the entire table to be rewritten. During this time, reads and writes are blocked.
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[8.0]
   def change
-    add_column :users, :some_column, :text, default: "default_value"
+    add_column :users, :some_column, :uuid, default: "gen_random_uuid()"
   end
 end
 ```
 
-In Postgres 11+, this no longer requires a table rewrite and is safe (except for volatile functions like `gen_random_uuid()`).
-
 #### Good
 
 Instead, add the column without a default value, then change the default.
 
 ```ruby
-class AddSomeColumnToUsers < ActiveRecord::Migration[7.1]
+class AddSomeColumnToUsers < ActiveRecord::Migration[8.0]
   def up
-    add_column :users, :some_column, :text
-    change_column_default :users, :some_column, "default_value"
+    add_column :users, :some_column, :uuid
+    change_column_default :users, :some_column, from: nil, to: "gen_random_uuid()"
   end
 
   def down
@@ -724,7 +695,7 @@ config.active_record.partial_inserts = false
 Adding a non-unique index with more than three columns rarely improves performance.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[8.0]
   def change
     add_index :users, [:a, :b, :c, :d]
   end
@@ -736,9 +707,9 @@ end
 Instead, start an index with columns that narrow down the results the most.
 
 ```ruby
-class AddSomeIndexToUsers < ActiveRecord::Migration[7.1]
+class AddSomeIndexToUsers < ActiveRecord::Migration[8.0]
   def change
-    add_index :users, [:b, :d]
+    add_index :users, [:d, :b]
   end
 end
 ```
@@ -750,7 +721,7 @@ For Postgres, be sure to add them concurrently.
 To mark a step in the migration as safe, despite using a method that might otherwise be dangerous, wrap it in a `safety_assured` block.
 
 ```ruby
-class MySafeMigration < ActiveRecord::Migration[7.1]
+class MySafeMigration < ActiveRecord::Migration[8.0]
   def change
     safety_assured { remove_column :users, :some_column }
   end
@@ -761,7 +732,7 @@ Certain methods like `execute` and `change_table` cannot be inspected and are pr
 
 ## Safe by Default
 
-Make operations safe by default.
+Make certain operations safe by default. This allows you to write the code under the "Bad" section, but the migration will be performed as if you had written the "Good" version.
 
 - adding and removing an index
 - adding a foreign key
@@ -810,6 +781,16 @@ StrongMigrations.disable_check(:add_index)
 
 Check the [source code](https://github.com/ankane/strong_migrations/blob/master/lib/strong_migrations/error_messages.rb) for the list of keys.
 
+## Skip Databases
+
+Skip checks and other functionality for specific databases with:
+
+```ruby
+StrongMigrations.skip_database(:catalog)
+```
+
+Note: This does not affect `alphabetize_schema`.
+
 ## Down Migrations / Rollbacks
 
 By default, checks are disabled when migrating down. Enable them with:
@@ -891,7 +872,21 @@ production:
 
 For HTTP connections, Redis, and other services, check out [this guide](https://github.com/ankane/the-ultimate-guide-to-ruby-timeouts).
 
-## Lock Timeout Retries [experimental]
+## Invalid Indexes
+
+In Postgres, adding an index non-concurrently can leave behind an invalid index if the lock timeout is reached. Running the migration again can result in an error.
+
+To automatically remove the invalid index when the migration runs again, use:
+
+```ruby
+StrongMigrations.remove_invalid_indexes = true
+```
+
+Note: This feature is experimental.
+
+## Lock Timeout Retries
+
+Note: This feature is experimental.
 
 There’s the option to automatically retry statements for migrations when the lock timeout is reached. Here’s how it works:
 
@@ -915,7 +910,7 @@ StrongMigrations.lock_timeout_retry_delay = 10.seconds
 To mark migrations as safe that were created before installing this gem, create an initializer with:
 
 ```ruby
-StrongMigrations.start_after = 20230101000000
+StrongMigrations.start_after = 20250101000000
 ```
 
 Use the version from your latest migration.
@@ -925,14 +920,14 @@ Use the version from your latest migration.
 If your development database version is different from production, you can specify the production version so the right checks run in development.
 
 ```ruby
-StrongMigrations.target_version = 10 # or "8.0.12", "10.3.2", etc
+StrongMigrations.target_version = 10 # or 8.0, 10.5, etc
 ```
 
-The major version works well for Postgres, while the full version is recommended for MySQL and MariaDB.
+The major version works well for Postgres, while the major and minor version is recommended for MySQL and MariaDB.
 
 For safety, this option only affects development and test environments. In other environments, the actual server version is always used.
 
-If your app has multiple databases with different versions, with Rails 6.1+, you can use:
+If your app has multiple databases with different versions, you can use:
 
 ```ruby
 StrongMigrations.target_version = {primary: 13, catalog: 15}
@@ -972,15 +967,18 @@ You probably don’t need this gem for smaller projects, as operations that are
 
 ## Additional Reading
 
-- [Rails Migrations with No Downtime](https://pedro.herokuapp.com/past/2011/7/13/rails_migrations_with_no_downtime/)
 - [PostgreSQL at Scale: Database Schema Changes Without Downtime](https://medium.com/braintree-product-technology/postgresql-at-scale-database-schema-changes-without-downtime-20d3749ed680)
-- [An Overview of DDL Algorithms in MySQL](https://mydbops.wordpress.com/2020/03/04/an-overview-of-ddl-algorithms-in-mysql-covers-mysql-8/)
+- [MySQL InnoDB Online DDL Operations](https://dev.mysql.com/doc/refman/en/innodb-online-ddl-operations.html)
 - [MariaDB InnoDB Online DDL Overview](https://mariadb.com/kb/en/innodb-online-ddl-overview/)
 
 ## Credits
 
 Thanks to Bob Remeika and David Waller for the [original code](https://github.com/foobarfighter/safe-migrations) and [Sean Huber](https://github.com/LendingHome/zero_downtime_migrations) for the bad/good readme format.
 
+## History
+
+View the [changelog](https://github.com/ankane/strong_migrations/blob/master/CHANGELOG.md)
+
 ## Contributing
 
 Everyone is encouraged to help improve this project. Here are a few ways you can help:

data/lib/generators/strong_migrations/install_generator.rb

@@ -21,21 +21,17 @@ module StrongMigrations
 
       def target_version
         case adapter
-        when /mysql/
+        when /mysql|trilogy/
           # could try to connect to database and check for MariaDB
           # but this should be fine
-          '"8.0.12"'
+          "8.0"
         else
           "10"
         end
       end
 
       def adapter
-        if ActiveRecord::VERSION::STRING.to_f >= 6.1
-          ActiveRecord::Base.connection_db_config.adapter.to_s
-        else
-          ActiveRecord::Base.connection_config[:adapter].to_s
-        end
+        ActiveRecord::Base.connection_db_config.adapter.to_s
       end
 
       def postgresql?

data/lib/strong_migrations/adapters/abstract_adapter.rb

@@ -13,11 +13,11 @@ module StrongMigrations
       end
 
       def set_statement_timeout(timeout)
-        raise StrongMigrations::Error, "Statement timeout not supported for this database"
+        # do nothing
       end
 
       def set_lock_timeout(timeout)
-        raise StrongMigrations::Error, "Lock timeout not supported for this database"
+        # do nothing
       end
 
       def check_lock_timeout(limit)
@@ -40,6 +40,9 @@ module StrongMigrations
         ["primary_key"]
       end
 
+      def max_constraint_name_length
+      end
+
       private
 
       def connection
@@ -55,14 +58,6 @@ module StrongMigrations
         version =
           if target_version && StrongMigrations.developer_env?
             if target_version.is_a?(Hash)
-              # Active Record 6.0 supports multiple databases
-              # but connection.pool.spec.name always returns "primary"
-              # in migrations with rails db:migrate
-              if ActiveRecord::VERSION::STRING.to_f < 6.1
-                # error class is not shown in db:migrate output so ensure message is descriptive
-                raise StrongMigrations::Error, "StrongMigrations.target_version does not support multiple databases for Active Record < 6.1"
-              end
-
               db_config_name = connection.pool.db_config.name
               target_version.stringify_keys.fetch(db_config_name) do
                 # error class is not shown in db:migrate output so ensure message is descriptive

data/lib/strong_migrations/adapters/mariadb_adapter.rb

@@ -6,7 +6,7 @@ module StrongMigrations
       end
 
       def min_version
-        "10.2"
+        "10.5"
       end
 
       def server_version