Merge pull request #36255 from eugeneius/sqlite_savepoint_support

Remove SQLite version support caveats [ci skip]

activerecord/lib/active_record/connection_adapters/abstract/database_statements.rb

@@ -205,8 +205,6 @@ def truncate_tables(*table_names) # :nodoc:
       # In order to get around this problem, #transaction will emulate the effect
       # of nested transactions, by using savepoints:
       # https://dev.mysql.com/doc/refman/5.7/en/savepoint.html
-      # Savepoints are supported by MySQL and PostgreSQL. SQLite3 version >= '3.6.8'
-      # supports savepoints.
       #
       # It is safe to call this method if a database transaction is already open,
       # i.e. if #transaction is called within another #transaction block. In case

activerecord/lib/active_record/connection_adapters/abstract/schema_statements.rb

@@ -735,7 +735,7 @@ def rename_column(table_name, column_name, new_column_name)
       #
       #   CREATE UNIQUE INDEX index_accounts_on_branch_id_and_party_id ON accounts(branch_id, party_id) WHERE active
       #
-      # Note: Partial indexes are only supported for PostgreSQL and SQLite 3.8.0+.
+      # Note: Partial indexes are only supported for PostgreSQL and SQLite.
       #
       # ====== Creating an index with a specific method
       #

activerecord/lib/active_record/connection_adapters/sqlite3_adapter.rb

@@ -48,8 +48,8 @@ def sqlite3_connection(config)
   end
 
   module ConnectionAdapters #:nodoc:
-    # The SQLite3 adapter works SQLite 3.6.16 or newer
-    # with the sqlite3-ruby drivers (available as gem from https://rubygems.org/gems/sqlite3).
+    # The SQLite3 adapter works with the sqlite3-ruby drivers
+    # (available as gem from https://rubygems.org/gems/sqlite3).
     #
     # Options:
     #

activerecord/lib/active_record/transactions.rb

@@ -164,12 +164,12 @@ module Transactions
     #     end
     #   end
     #
-    # only "Kotori" is created. This works on MySQL and PostgreSQL. SQLite3 version >= '3.6.8' also supports it.
+    # only "Kotori" is created.
     #
     # Most databases don't support true nested transactions. At the time of
     # writing, the only database that we're aware of that supports true nested
     # transactions, is MS-SQL. Because of this, Active Record emulates nested
-    # transactions by using savepoints on MySQL and PostgreSQL. See
+    # transactions by using savepoints. See
     # https://dev.mysql.com/doc/refman/5.7/en/savepoint.html
     # for more information about savepoints.
     #