Bug: Batch ordering

[nPraml]

Hello @rob-bygrave,

we are currently in the process of updating from ebean 13 to 14 and we encountered a bug, see the test case.

The entity Contact has a @ManyToOne property (without cascadeType) ContactGroup.

In a transaction we store some elements using DB.insertAll(). Then we save a contact (without a group), we create a group with a certain id, we save it and then we put the group in the contact.

With transaction flush, however, the order in the queue is not correct: contact (with group) is saved first, but group does not yet exist in the DB.

What we discovered during debugging: after DB.insertAll(), txn.batchMode = true is set (this was not the case with ebean 13) and during flush the objects contact and group are in the wrong order in the queue.

With ebean 13 you have to explicitly call txn.setBatchMode(true) for the test to fail.

Could you please take a look and help us fix this?

Cheers,
Noemi

@rPraml FYI

[nPraml]

if I modify insertAll on the same way as saveAll:

it fixes the test, but the test case fails if I use instead insertAll a trx.setBatchMode(true)