Bump sqlalchemy from 1.3.16 to 1.3.20
Bumps sqlalchemy from 1.3.16 to 1.3.20.
Release notes
Sourced from sqlalchemy's releases.
1.3.20
Released: October 12, 2020
orm
[orm] [bug] An
ArgumentError
with more detail is now raised if the target parameter for_query.Query.join()
is set to an unmapped object. Prior to this change a less detailedAttributeError
was raised. Pull request courtesy Ramon Williams.References: #4428
[orm] [bug] Fixed issue where using a loader option against a string attribute name that is not actually a mapped attribute, such as a plain Python descriptor, would raise an uninformative AttributeError; a descriptive error is now raised.
References: #4589
engine
[engine] [bug] Fixed issue where a non-string object sent to
_exc.SQLAlchemyError
or a subclass, as occurs with some third party dialects, would fail to stringify correctly. Pull request courtesy Andrzej Bartosiński.References: #5599
[engine] [bug] Repaired a function-level import that was not using SQLAlchemy's standard late-import system within the sqlalchemy.exc module.
References: #5632
sql
... (truncated)
[sql] [bug] Fixed issue where the
pickle.dumps()
operation against_expression.Over
construct would produce a recursion overflow.References: #5644
[sql] [bug] Fixed bug where an error was not raised in the case where a
_sql.column()
were added to more than one_sql.table()
at a time. This raised correctly for the_schema.Column
and_schema.Table
objects. An_exc.ArgumentError
is now raised when this occurs.
Commits
- See full diff in compare view