Bump sqlalchemy from 1.3.16 to 1.3.21

Bumps sqlalchemy from 1.3.16 to 1.3.21.

Release notes

Sourced from sqlalchemy's releases.

1.3.21

Released: December 17, 2020

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 _orm.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 _orm.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.

  References: #5774

• [orm] [bug] Fixed bug in _query.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.

  References: #5664

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

  References: #5737

sql

• [sql] [bug] A warning is emmitted if a returning() method such as _sql.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 _sql.Insert.returning() and _sql.ValuesBase.return_defaults() methods now raises an error as these methods are mutually exclusive; previously the operation would fail silently.

  References: #5691

• [sql] [bug] Fixed structural compiler issue where some constructs such as MySQL / PostgreSQL "on conflict / on duplicate key" would rely upon the state of

... (truncated)

Commits

• See full diff in compare view