OrderColumn doesn't actually work, index is always 0 across transactions

Description

Following the discussion and fix of HHH-8083, I never got OrderColumn to work but other priorities forced me to abandon this, but I spent some time on it now and found that the OrderColumn fix doesn't actually work. While the original testcase passes, if you add multiple items to the collection across flushes, newly added item will all be added with index 0. Any collection retrieval will then just contain the one item.

I've modified the original test case to prove this

Environment

None

Status

Assignee

Brett Meyer

Reporter

Marc Schipperheyn

Fix versions

Labels

None

backPortable

None

Suitable for new contributors

None

Requires Release Note

None

Pull Request

None

backportDecision

None

Affects versions

4.3.4
4.2.11

Priority

Major