Bump sqlalchemy from 1.3.16 to 1.3.22

Bumps sqlalchemy from 1.3.16 to 1.3.22.

Release notes

Sourced from sqlalchemy's releases.

1.3.22

Released: December 18, 2020

oracle

• [oracle] [bug] Fixed regression which occured due to #5755 which implemented isolation level support for Oracle. It has been reported that many Oracle accounts don't actually have permission to query the v$transaction view so this feature has been altered to gracefully fallback when it fails upon database connect, where the dialect will assume "READ COMMITTED" is the default isolation level as was the case prior to SQLAlchemy 1.3.21. However, explicit use of the _engine.Connection.get_isolation_level() method must now necessarily raise an exception, as Oracle databases with this restriction explicitly disallow the user from reading the current isolation level.

  References: #5784

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

... (truncated)

Commits

• See full diff in compare view