Package: python-oslo.db / 4.40.0-3
Patch seriesview the series file
|Resolve_SAWarning_in_Query.soft_delete.patch | (download)||
6 3 + 3 - 0 !
[patch] resolve sawarning in query.soft_delete() We currently see a lot of warnings like this from the soft_delete() method: . sqlalchemy.exc.SAWarning: Evaluating non-mapped column expression 'updated_at' onto ORM instances; this is a deprecated use case. Please make use of the actual mapped columns in ORM-evaluated UPDATE / DELETE expressions. . This is because the "evaluate" synchronization strategy would like to search for objects and update them based on the UPDATE criteria passed, however the columns given, literal_column('id'), literal_column('updated_at'), are not mapped to anything. The evaluator has to make a guess that the string contained in these expressions should be matched to a mapped attribute on the given entity and this guess was first removed in , then added back in  with a warning (likely since oslo.db is invoking it). . This uses the actual entity-mapped column for the query rather than the literal string column. .  https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-b1e620dece39006ab44c47044e9a6fee  https://docs.sqlalchemy.org/en/latest/changelog/changelog_12.html#change-dff3a469788c81a46440584406cb22be Date: Fri, 1 Feb 2019 11:53:26 -0500