ed31d819bb
Accepting request 842694 from system:homeautomation:home-assistant:unstable
Tomáš Chvátal
2020-10-20 07:53:08 +00:00
0d6fd6dc04
- Replace pytest_depr_from_parent.patch with the upstream commit resolving same issue (gh#sqlalchemy/sqlalchemy#commit40cdb9c0bf4d).
Matej Cepl2020-10-09 13:52:28 +00:00
cf13b151ec
- Add pytest_depr_from_parent.patch to fix FTBGS with pytest 6.* (gh#sqlalchemy/sqlalchemy#5635)
Matej Cepl2020-10-08 15:45:35 +00:00
f668cbb37b
- update to 1.3.19 * Adjusted the workings of the Mapper.all_orm_descriptors() * The name of the virtual column used when using the AbstractConcreteBase and ConcreteBase classes can now be customized * Repaired an issue where the “ORDER BY” clause rendering a label name rather than a complete expression * The LookupError message will now provide the user with up to four possible values that a column is constrained to via the Enum * Fixed issue where the Connection.execution_options.schema_translate_map feature would not take effect when the Sequence.next_value() function for a Sequence were used in the Column.server_default parameter and the create table DDL were emitted. * Added a **kw argument to the DeclarativeMeta.__init__() method
Ondřej Súkup2020-08-20 12:04:06 +00:00
7e5a97dcab
- Fix build for older distributions by buildrequiring a new-enough pytest
Dirk Mueller2020-03-21 14:58:35 +00:00
20d1799fa3
- update to 1.3.15: * Adjusted the error message emitted by :meth:.Query.join when a left hand side can't be located that the :meth:.Query.select_from method is the best way to resolve the issue. Also, within the 1.3 series, used a deterministic ordering when determining the FROM clause from a given column entity passed to :class:.Query so that the same expression is determined each time. * Fixed regression in 1.3.14 due to 🎫4849 where a sys.exc_info() call failed to be invoked correctly when a flush error would occur. Test coverage has been added for this exception case. * Fixed bug where a CTE of an INSERT/UPDATE/DELETE that also uses RETURNING could then not be SELECTed from directly, as the internal state of the compiler would try to treat the outer SELECT as a DELETE statement itself and access nonexistent state. * Fixed regression caused in 1.3.13 by 🎫5056 where a refactor of the ORM path registry system made it such that a path could no longer be compared to an empty tuple, which can occur in a particular kind of joined eager loading path. The "empty tuple" use case has been resolved so that the path registry is compared to a path registry in all cases;
Dirk Mueller2020-03-14 12:37:55 +00:00
c94e89154f
- Fix build without python2
Tomáš Chvátal
2020-03-12 07:37:14 +00:00
b32f682114
- update to version 1.3.12: * [orm] [bug] Fixed issue involving lazy="raise" strategy where an ORM delete of an object would raise for a simple “use-get” style many-to-one relationship that had lazy=”raise” configured. This is inconsistent vs. the change introduced in 1.3 as part of #4353, where it was established that a history operation that does not expect emit SQL should bypass the lazy="raise" check, and instead effectively treat it as lazy="raise_on_sql" for this case. The fix adjusts the lazy loader strategy to not raise for the case where the lazy load was instructed that it should not emit SQL if the object were not present. * [orm] [bug] Fixed regression introduced in 1.3.0 related to the association proxy refactor in #4351 that prevented composite() attributes from working in terms of an association proxy that references them. * [orm] [bug] Setting persistence-related flags on relationship() while also setting viewonly=True will now emit a regular warning, as these flags do not make sense for a viewonly=True relationship. In particular, the “cascade” settings have their own warning that is generated based on the individual values, such as “delete, delete-orphan”, that should not apply to a viewonly relationship. Note however that in the case of “cascade”, these settings are still erroneously taking effect even though the relationship is set up as “viewonly”. In 1.4, all persistence-related cascade settings will be disallowed on a viewonly=True relationship in order to resolve this issue. * [orm] [bug] [py3k] Fixed issue where when assigning a collection to itself as a slice, the mutation operation would fail as it would first erase the assigned collection inadvertently. As an assignment that does not change the contents should not generate events, the operation is now a no-op. Note that the fix only applies to Python 3; in Python 2, the __setitem__ hook isn’t called in this case; __setslice__ is used instead which recreates the list item-by-item in all cases. * [orm] [bug] Fixed issue where by if the “begin” of a transaction failed at the Core engine/connection level, such as due to network error or database is
Dirk Mueller2019-12-20 19:02:07 +00:00
089147cda9
- Update to 1.3.10: * Fixed regression in selectinload loader strategy * Passing a plain string expression to Session.query() is deprecated * A warning is emitted for a condition in which the Session may implicitly swap an object out of the identity map for another one with the same primary key
Tomáš Chvátal
2019-10-30 13:47:48 +00:00
Dominique Leuenberger
Dirk Mueller
Tomáš Chvátal
Matej Cepl
Ondřej Súkup
Yuchen Lin
Todd R
Thomas Bechtold
Stephan Kulow