Replace deprecated with_lockmode with with_for_update
The Query.with_lockmode() method is deprecated since version 0.9.0
and will be removed in a future release. [1]
This patch replaces it with Query.with_for_update().
The 'faultstring' was been modified to 'Exactly 5 or 6 columns has to be
specified for iterator expression', so adds one space between "iterator"
and "expression" for 'expected_error_msg'.
Also use upper-constraints in doc build to avoid issues in pdf build.
Reviewed: https:/ /review. opendev. org/c/openstack /watcher/ +/797889 /opendev. org/openstack/ watcher/ commit/ 9ca44fa3ab16ba9 9c65b75c7fa2fde 3b2c160b1d
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit 9ca44fa3ab16ba9 9c65b75c7fa2fde 3b2c160b1d 163.com>
Author: ericxiett <eric_xiett@
Date: Thu Jun 24 12:27:05 2021 +0000
Replace deprecated with_lockmode with with_for_update
The Query.with_ lockmode( ) method is deprecated since version 0.9.0 for_update( ). error_msg' .
and will be removed in a future release. [1]
This patch replaces it with Query.with_
The 'faultstring' was been modified to 'Exactly 5 or 6 columns has to be
specified for iterator expression', so adds one space between "iterator"
and "expression" for 'expected_
Also use upper-constraints in doc build to avoid issues in pdf build.
[1] /docs.sqlalchem y.org/en/ 13/orm/ query.html# sqlalchemy. orm.query. Query.with_ lockmode
https:/
Closes-Bug: #1933226 8790259fd27e56a 41f6dbbbaa0
Change-Id: I0ad514da647bb0