From 942c2429c033255979b6a55de836b9b26370673e Mon Sep 17 00:00:00 2001 From: Mike Bayer Date: Mon, 7 Nov 2016 21:41:11 -0500 Subject: Put include_table=True for DO UPDATE..WHERE, but not ON CONFLICT Fixed regression caused by the fix in :ticket:`3807` (version 1.1.0) where we ensured that the tablename was qualified in the WHERE clause of the DO UPDATE portion of PostgreSQL's ON CONFLICT, however you *cannot* put the table name in the WHERE clause in the actual ON CONFLICT itself. This was an incorrect assumption, so that portion of the change in :ticket:`3807` is rolled back. Change-Id: I442d8629496a8e405b54711cfcf487761810ae8a Fixes: #3846 Fixes: #3807 --- lib/sqlalchemy/dialects/postgresql/base.py | 1 + 1 file changed, 1 insertion(+) (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 9898e4ba4..4c82325f5 100644 --- a/lib/sqlalchemy/dialects/postgresql/base.py +++ b/lib/sqlalchemy/dialects/postgresql/base.py @@ -1433,6 +1433,7 @@ class PGCompiler(compiler.SQLCompiler): target_text += ' WHERE %s' % \ self.process( clause.inferred_target_whereclause, + include_table=False, use_schema=False ) else: -- cgit v1.2.1