From 1c19d4cf7e69ed5e69a9eba0b69ba78e36610df0 Mon Sep 17 00:00:00 2001 From: Rob Bygrave Date: Mon, 26 Feb 2018 13:20:49 +1300 Subject: [PATCH] #1278 - Multi-tenant delete by id ... doesn't return 0 when no rows deleted Where -1 (jdbc batch) is returned as true as per current behaviour --- src/main/java/io/ebeaninternal/server/core/DefaultServer.java | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/main/java/io/ebeaninternal/server/core/DefaultServer.java b/src/main/java/io/ebeaninternal/server/core/DefaultServer.java index 90c78b0dc..927620ae9 100644 --- a/src/main/java/io/ebeaninternal/server/core/DefaultServer.java +++ b/src/main/java/io/ebeaninternal/server/core/DefaultServer.java @@ -1758,7 +1758,7 @@ public final class DefaultServer implements SpiServer, SpiEbeanServer { @Override public boolean delete(Object bean, Transaction t) throws OptimisticLockException { // this should really return an int where -1 means jdbc batch/unknown - return persister.delete(checkEntityBean(bean), t, false) == 1; + return persister.delete(checkEntityBean(bean), t, false) != 0; } @Override @@ -1769,7 +1769,7 @@ public final class DefaultServer implements SpiServer, SpiEbeanServer { @Override public boolean deletePermanent(Object bean, Transaction t) throws OptimisticLockException { // this should really return an int where -1 means jdbc batch/unknown - return persister.delete(checkEntityBean(bean), t, true) == 1; + return persister.delete(checkEntityBean(bean), t, true) != 0; } @Override