Bump sqlalchemy from 1.3.20 to 1.4.11

Bumps sqlalchemy from 1.3.20 to 1.4.11.

Release notes

Sourced from sqlalchemy's releases.

1.4.11

Released: April 21, 2021

orm declarative

• [orm] [declarative] [bug] [regression] Fixed regression where recent changes to support Python dataclasses had the inadvertent effect that an ORM mapped class could not successfully override the __new__() method.

  References: #6331

engine

• [engine] [bug] [regression] Fixed critical regression caused by the change in #5497 where the connection pool "init" phase no longer occurred within mutexed isolation, allowing other threads to proceed with the dialect uninitialized, which could then impact the compilation of SQL statements.

  References: #6337

1.4.10

Released: April 20, 2021

orm

• [orm] [usecase] Altered some of the behavior repaired in #6232 where the immediateload loader strategy no longer goes into recursive loops; the modification is that an eager load (joinedload, selectinload, or subqueryload) from A->bs->B which then states immediateload for a simple manytoone B->a->A that's in the identity map will populate the B->A, so that this attribute is back-populated when the collection of A/A.bs are loaded. This allows the objects to be functional when detached.

• [orm] [bug] Fixed bug in new _orm.with_loader_criteria() feature where using a mixin class with _orm.declared_attr() on an attribute that were accessed inside the custom lambda would emit a warning regarding using an unmapped declared attr, when the lambda callable were first initialized. This warning is now prevented using special instrumentation for this lambda initialization step.

  References: #6320

• [orm] [bug] [regression] Fixed additional regression caused by the "eagerloaders on refresh" feature added in #1763 where the refresh operation historically would set populate_existing, which given the new feature now overwrites pending

... (truncated)

Commits

• See full diff in compare view