From b4eb29253cb29a069973503f36d1103d4a18311c Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Wed, 4 Apr 2018 13:36:28 -0400 Subject: Ensure all visit_sequence accepts **kw args Fixed issue where the compilation of an INSERT statement with the "literal_binds" option that also uses an explicit sequence and "inline" generation, as on Postgresql and Oracle, would fail to accommodate the extra keyword argument within the sequence processing routine. Change-Id: Ibdab7d340aea7429a210c9535ccf1a3e85f074fb Fixes: #4231 --- lib/sqlalchemy/dialects/postgresql/base.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'lib/sqlalchemy/dialects/postgresql/base.py') diff --git a/lib/sqlalchemy/dialects/postgresql/base.py b/lib/sqlalchemy/dialects/postgresql/base.py index c5b0db6ce..0160239b7 100644 --- a/lib/sqlalchemy/dialects/postgresql/base.py +++ b/lib/sqlalchemy/dialects/postgresql/base.py @@ -1489,7 +1489,7 @@ class PGCompiler(compiler.SQLCompiler): value = value.replace('\\', '\\\\') return value - def visit_sequence(self, seq): + def visit_sequence(self, seq, **kw): return "nextval('%s')" % self.preparer.format_sequence(seq) def limit_clause(self, select, **kw): -- cgit v1.2.1