Pg full combination between anyConflict and conflict set all isn't accepted by postgres

[jappeace]

These functions combined: Pg.onConflict Pg.anyConflict Pg.onConflictSetAll

produce the following runtime error:

"ON CONFLICT DO UPDATE requires inference specification or constraint name"

I would expect beam to give me a type error.

[tp-woven]

Just ran into a similar issue with onConflict, anyConflict and onConflictUpdateAll as well. Solved it by changing anyConflict to conflictingFields (\tbl -> primaryKey tbl).