OCA / OCB

71%

9.0: 68%

LAST BUILD ON BRANCH 11.0-ocabot-merge-pr-855-by-pedrobaeza-bump-no

branch: 11.0-ocabot-merge-pr-855-by-pedrobaeza-bump-no

CHANGE BRANCH

x

Reset

• 11.0-ocabot-merge-pr-855-by-pedrobaeza-bump-no
• 10.0
• 10.0-ocabot-merge-pr-810-by-gurneyalex-bump-no
• 11.0
• 11.0-ocabot-merge-pr-869-by-pedrobaeza-bump-no
• 11.0-ocabot-merge-pr-870-by-pedrobaeza-bump-no
• 7.0
• 8.0
• 9.0
• 9.0-ocabot-merge-pr-808-by-pedrobaeza-bump-no
• revert-131-7.0-oca-fix_3264_use_parent_address
• revert-474-patch-3

Build # 4545

Build Type

push

travis-ci

Committed by OCA-git-bot

Commit Message

[FIX] web: stabilize sequence for new records on last page

Before this commit, the compute sequence was relying on the fact the ID was used
as a secondary order key to get the right result.

This is necessary when adding items between pages because we don't resequence
the following elements.

However this was not necessary when adding new elements on the last page since
there are no following elements to resesquence in that case.

PR: #27639

Run Details

6754 of 9526 relevant lines covered (70.9%)

1.8 hits per line