Fixed an issue where using :func:`.bindparam` with no explicit data or type
given could be coerced into the incorrect type when used in expressions
- such as when using :meth:`.ARRAY.comparator.any` and
- :meth:`.ARRAY.comparator.all`.
+ such as when using :meth:`.ARRAY.Comparator.any` and
+ :meth:`.ARRAY.Comparator.all`.
:tags: bug, sql, postgresql, sqlite
:tickets: 8014
- Fixed bug where the PostgreSQL :meth:`_postgresql.Insert.on_conflict`
- method and the SQLite :meth:`_sqlite.Insert.on_conflict` method would both
- fail to correctly accommodate a column with a separate ".key" when
- specifying the column using its key name in the dictionary passed to
- ``set_``, as well as if the :attr:`_sqlite.Insert.excluded` or
- :attr:`_postgresql.Insert.excluded` collection were used as the dictionary
- directly.
+ Fixed bug where the PostgreSQL
+ :meth:`_postgresql.Insert.on_conflict_do_update` method and the SQLite
+ :meth:`_sqlite.Insert.on_conflict_do_update` method would both fail to
+ correctly accommodate a column with a separate ".key" when specifying the
+ column using its key name in the dictionary passed to
+ :paramref:`_postgresql.Insert.on_conflict_do_update.set_`, as well as if
+ the :attr:`_postgresql.Insert.excluded` collection were used as the
+ dictionary directly.