internally at least refer to multirow as "multivalues", to distinguish between

an INSERT that's used in executemany() as opposed to one which has a VALUES
clause with multiple entries.

1 files changed, 2 insertions, 2 deletions

diff --git a/lib/sqlalchemy/testing/requirements.py b/lib/sqlalchemy/testing/requirements.py
index 057da7849..2fb1b3143 100644
--- a/lib/sqlalchemy/testing/requirements.py
+++ b/lib/sqlalchemy/testing/requirements.py
@@ -88,12 +88,12 @@ class SuiteRequirements(Requirements):
                 )
 
     @property
-    def multirow_inserts(self):
+    def multivalues_inserts(self):
         """target database must support multiple VALUES clauses in an
         INSERT statement."""
 
         return exclusions.skip_if(
-                    lambda: not self.db.dialect.supports_multirow_insert,
+                    lambda: not self.db.dialect.supports_multivalues_insert,
                     "Backend does not support multirow inserts."
                 )