--- /dev/null
+.. change::
+ :tags: bug, postgresql
+ :tickets: 4074
+ :versions: 1.2.0b3
+
+ Fixed bug in Postgresql :meth:`.postgresql.dml.Insert.on_conflict_do_update`
+ which would prevent the insert statement from being used as a CTE,
+ e.g. via :meth:`.Insert.cte`, within another statement.
\ No newline at end of file
set_parameters = dict(clause.update_values_to_set)
# create a list of column assignment clauses as tuples
- cols = self.statement.table.c
+
+ insert_statement = self.stack[-1]['selectable']
+ cols = insert_statement.table.c
for c in cols:
col_key = c.key
if col_key in set_parameters:
"param_1": "somename",
"param_2": "unknown"})
+ def test_on_conflict_as_cte(self):
+ i = insert(
+ self.table1, values=dict(name='foo'))
+ i = i.on_conflict_do_update(
+ constraint=self.excl_constr_anon,
+ set_=dict(name=i.excluded.name),
+ where=(
+ (self.table1.c.name != i.excluded.name))
+ ).returning(literal_column("1")).cte("i_upsert")
+
+ stmt = select([i])
+
+ self.assert_compile(
+ stmt,
+ "WITH i_upsert AS "
+ "(INSERT INTO mytable (name) VALUES (%(name)s) "
+ "ON CONFLICT (name, description) "
+ "WHERE description != %(description_1)s "
+ "DO UPDATE SET name = excluded.name "
+ "WHERE mytable.name != excluded.name RETURNING 1) "
+ "SELECT i_upsert.1 "
+ "FROM i_upsert"
+ )
+
def test_quote_raw_string_col(self):
t = table('t', column("FancyName"), column("other name"))