From 7de57cfe33ec8717a51997cf85bd1702da322dab Mon Sep 17 00:00:00 2001 From: Yasuo Honda Date: Wed, 13 Mar 2019 10:31:54 +0000 Subject: [skip ci] Rails 5.1+ supports bigint primary key Follow up #35573 --- activerecord/lib/active_record/relation.rb | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'activerecord/lib') diff --git a/activerecord/lib/active_record/relation.rb b/activerecord/lib/active_record/relation.rb index ab50972e06..ac37f73b76 100644 --- a/activerecord/lib/active_record/relation.rb +++ b/activerecord/lib/active_record/relation.rb @@ -199,7 +199,7 @@ module ActiveRecord # * It relies on exception handling to handle control flow, which may be marginally slower. # * The primary key may auto-increment on each create, even if it fails. This can accelerate # the problem of running out of integers, if the underlying table is still stuck on a primary - # key of type int (note: All Rails apps since 5.0+ have defaulted to bigint, which is not liable + # key of type int (note: All Rails apps since 5.1+ have defaulted to bigint, which is not liable # to this problem). # # This method will return a record if all given attributes are covered by unique constraints -- cgit v1.2.3