From 8070cbde716a247f8b31c1334c80fa53327e6d8e Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Sat, 8 Dec 2012 16:17:20 -0500 Subject: 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. --- lib/sqlalchemy/testing/requirements.py | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) (limited to 'lib/sqlalchemy/testing') 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." ) -- cgit v1.2.1