--------------------------------------------------------------------------
SQLAlchemy 1.3 was not able to accommodate bound parameter names that included
-percent signs or parenthesis under the psycopg2 dialect, which meant that
-column names which included these characters were also problematic as
+percent signs or parenthesis under the psycopg2 dialect. This in turn meant
+that column names which included these characters were also problematic as
INSERT and other DML statements would generate parameter names that matched
-that of the column, unless the :paramref:`_schema.Column.key` parameter
-were used to provide an alternate name that would be used to generate
-the parameter, or otherwise the parameter style of the dialect had to be
-changed. As of SQLAlchemy 1.4.0beta3 all naming limitations have been removed
-and parameters are fully escaped in all scenarios.
+that of the column, which would then cause failures. The workaround was to make
+use of the :paramref:`_schema.Column.key` parameter so that an alternate name
+that would be used to generate the parameter, or otherwise the parameter style
+of the dialect had to be changed at the :func:`_sa.create_engine` level. As of
+SQLAlchemy 1.4.0beta3 all naming limitations have been removed and parameters
+are fully escaped in all scenarios, so these workarounds are no longer
+necessary.
:ticket:`5941`
parenthesis in psycopg2's "pyformat" style.
As part of this change, the format used by the asyncpg DBAPI adapter (which
- is local to SQLAlchemy's asyncpg diaelct) has been changed from using
+ is local to SQLAlchemy's asyncpg dialect) has been changed from using
"qmark" paramstyle to "format", as there is a standard and internally
supported SQL string escaping style for names that use percent signs with
"format" style (i.e. to double percent signs), as opposed to names that use