Log Message:
py-sqlalchemy: updated to 1.3.21

1.3.21

orm

[orm] [bug]

Added a comprehensive check and an informative error message for the case where \ 
a mapped class, or a string mapped class name, is passed to \ 
relationship.secondary. This is an extremely common error which warrants a clear \ 
message.

Additionally, added a new rule to the class registry resolution such that with \ 
regards to the relationship.secondary parameter, if a mapped class and its table \ 
are of the identical string name, the Table will be favored when resolving this \ 
parameter. In all other cases, the class continues to be favored if a class and \ 
table share the identical name.

[orm] [bug]

Fixed bug in Query.update() where objects in the _ormsession.Session that were \ 
already expired would be unnecessarily SELECTed individually when they were \ 
refreshed by the “evaluate”synchronize strategy.

[orm] [bug]

Fixed bug involving the restore_load_context option of ORM events such as \ 
InstanceEvents.load() such that the flag would not be carried along to \ 
subclasses which were mapped after the event handler were first established.

sql

[sql] [bug]

A warning is emmitted if a returning() method such as Insert.returning() is \ 
called multiple times, as this does not yet support additive operation. Version \ 
1.4 will support additive operation for this. Additionally, any combination of \ 
the Insert.returning() and ValuesBase.return_defaults() methods now raises an \ 
error as these methods are mutually exclusive; previously the operation would \ 
fail silently.

[sql] [bug]

Fixed structural compiler issue where some constructs such as MySQL / PostgreSQL \ 
“on conflict / on duplicate key” would rely upon the state of the Compiler \ 
object being fixed against their statement as the top level statement, which \ 
would fail in cases where those statements are branched from a different \ 
context, such as a DDL construct linked to a SQL statement.

postgresql

[postgresql] [usecase]

Added new parameter ExcludeConstraint.ops to the ExcludeConstraint object, to \ 
support operator class specification with this constraint. Pull request courtesy \ 
Alon Menczer.

[postgresql] [bug] [mysql]

Fixed regression introduced in 1.3.2 for the PostgreSQL dialect, also copied out \ 
to the MySQL dialect’s feature in 1.3.18, where usage of a non Table construct \ 
such as text() as the argument to Select.with_for_update.of would fail to be \ 
accommodated correctly within the PostgreSQL or MySQL compilers.

mysql

[mysql] [bug] [reflection]

Fixed issue where reflecting a server default on MariaDB only that contained a \ 
decimal point in the value would fail to be reflected correctly, leading towards \ 
a reflected table that lacked any server default.

[mysql] [sql]

Added missing keywords to the RESERVED_WORDS list for the MySQL dialect: action, \ 
level, mode, status, text, time. Pull request courtesy Oscar Batori.

sqlite

[sqlite] [usecase]

Added sqlite_with_rowid=False dialect keyword to enable creating tables as \ 
CREATE TABLE … WITHOUT ROWID. Patch courtesy Sean Anderson.

mssql

[mssql] [bug]

Fixed bug where a CREATE INDEX statement was rendered incorrectly when both \ 
mssql-include and mssql_where were specified. Pull request courtesy @Adiorz.

[mssql] [bug]

Added SQL Server code “01000” to the list of disconnect codes.

[mssql] [reflection] [sqlite]

Fixed issue with composite primary key columns not being reported in the correct \ 
order. Patch courtesy @fulpm.

oracle

[oracle] [usecase]

Implemented support for the SERIALIZABLE isolation level for Oracle databases, \ 
as well as a real implementation for Connection.get_isolation_level().