rbygrave f51f2269fb #2377 - Wrong order in batch save, fix transaction depth ...

The guts of this fix is in DefaultPersister.saveAssocOne() with the change to use the new transaction.depthDecrement() method. For our failing test cases this changes the depth from -1, 0 to be 0, 1.

We can see the impact of this change in the batch ordering via the logging of:
 io.ebean.SUM - txn[1001] BatchControl flush ...

2021-09-17 17:58:20 +12:00

..

ebean

Changes post-merge

2021-09-13 13:33:20 +02:00

ebeaninternal

#2377 - Wrong order in batch save, fix transaction depth

2021-09-17 17:58:20 +12:00

ebeanservice/docstore/api/support

#2361 - Tidy tests only, organise imports

2021-09-09 11:29:05 +12:00