From 6c797d6e03d774cfcaf4529f50052e42921e9fc8 Mon Sep 17 00:00:00 2001 From: willnet Date: Thu, 7 Mar 2019 10:42:22 +0900 Subject: [PATCH] [ci skip]Fix typo: constaint -> constraint --- activerecord/lib/active_record/persistence.rb | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/activerecord/lib/active_record/persistence.rb b/activerecord/lib/active_record/persistence.rb index 72ccf7739f..a09b5f0e96 100644 --- a/activerecord/lib/active_record/persistence.rb +++ b/activerecord/lib/active_record/persistence.rb @@ -93,7 +93,7 @@ def insert(attributes, returning: nil, unique_by: nil) # record or pass returning: false to omit the clause. # # [:unique_by] - # (Postgres and SQLite only) In a table with more than one unique constaint or index, + # (Postgres and SQLite only) In a table with more than one unique constraint or index, # new records may considered duplicates according to different criteria. By default, # new rows will be skipped if they violate _any_ unique constraint/index. By defining # :unique_by, you can skip rows that would create duplicates according to the given @@ -218,7 +218,7 @@ def upsert(attributes, returning: nil, unique_by: nil) # record or pass returning: false to omit the clause. # # [:unique_by] - # (Postgres and SQLite only) In a table with more than one unique constaint or index, + # (Postgres and SQLite only) In a table with more than one unique constraint or index, # new records may considered duplicates according to different criteria. For MySQL, # an upsert will take place if a new record violates _any_ unique constraint. For # Postgres and SQLite, new rows will replace existing rows when the new row has the -- GitLab