Wrong limit using setMaxRows on delete between calls

[AntoineDuComptoirDesPharmacies]

Expected behavior

When limiting the number of rows in delete query, if the limit change between call, the query should adapt and only delete the good number of items.

Actual behavior

When calling the same method with different limit, the limit is taken into account only on first call and then reused between calls.

Steps to reproduce

DB.find(ShoppingCart.class)
                    .where()
                    [...]
                    .setMaxRows(nbProcessed)
                    .delete();

First call with nbProcessed = 20 :

application-akka.actor.default-dispatcher-31 - [info] - service.MaidService - nbProcessed : 20
application-akka.actor.default-dispatcher-31 - [debug] - io.ebean.SQL - txn[] select sc.id from shopping_cart sc where [...] limit 20; --bind(2023-07-22 13:09:10.837) --micros(4�187)
application-akka.actor.default-dispatcher-31 - [debug] - io.ebean.SQL - txn[] delete from shopping_cart where id  = any(?); -- bind(Array[20]={12032,12035,12042,12044,12057,12059,12060,...}) rows(20)
application-akka.actor.default-dispatcher-31 - [info] - service.JobService - cleanOrphanShoppingCart: 20 Rows cleaned

Second call with nbProcessed = 18 :

application-akka.actor.default-dispatcher-32 - [info] - service.MaidService - nbProcessed : 18
application-akka.actor.default-dispatcher-32 - [debug] - io.ebean.SQL - txn[] select sc.id from shopping_cart sc where [...] limit 20; --bind(2023-07-22 13:09:15.76) --micros(3�541)
application-akka.actor.default-dispatcher-32 - [debug] - io.ebean.SQL - txn[] delete from shopping_cart where id  = any(?); -- bind(Array[20]={12409,12427,12447,12448,12454,12467,12469,...}) rows(20)
application-akka.actor.default-dispatcher-32 - [info] - service.JobService - cleanOrphanShoppingCart: 20 Rows cleaned

Yours faithfully,
LCDP