Is DB.saveAll respecting list order

[AntoineDuComptoirDesPharmacies]

Hi Ebean,

When calling DB.saveAll(beans);, if beans is a classic Java ArrayList which of beans sorted by id field.
Is Ebean ensuring that the rows gonna be updated (and so locked) in the same order as the list or it can be mixed ?

Thanks in advance for your help.
Yours faithfully,
LCDP

[rbygrave]

Perhaps you need to update the wording or add some background to this question to explain the issue?

DB.saveAll(beans)

Is taking a Collection and iterating on the collection, so the save for each bean is executed in the order that the collection iterator provides and that will always be the case.

[AntoineDuComptoirDesPharmacies]

O.K i understand that it is missing a bit of context.

The use case is the following, there is currently two thread T1, T2 running in parallel :
T1 :
Is doing DB.saveAll() with a list [A, B, C]

T2 :
Is doing DB.saveAll() with a list [A, B, C]

As both lists are in the same order, is there any risks that the two concurrent DB.saveAll may result in a DB deadlock ?
Note : I know that it will not avoiding any OptimistickLockException.

Thank you !

[rbygrave]

may result in a DB deadlock ?

I believe we are all good - no deadlock expected for this case [because yes, as long as the ordering is consistent then one of them will end up waiting etc so yes I think we are good with this]

[AntoineDuComptoirDesPharmacies]

Perfect, thank you for your response ! ❤️