Turned our that there is no bug: page_reverse just implies behaviour
that is different from what I expected: it merely changes the order in
which the page is read (so with a marker, it will return the previous
page before the marker in db order; it is not supposed to reverse the
page result itself).
** Changed in: neutron
Status: In Progress => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1583289
Title:
api: page_reverse does not work if limit passed
Status in neutron:
Invalid
Bug description:
In API, if page_reverse is passed with limit, then the result is not
in reversed order. This is because common_db_mixin mistakenly apply
.reverse() on the result from database, breaking the order as returned
from database backend.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1583289/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
