From 54674a6cd7327e9847763eac641447b64e9b3f61 Mon Sep 17 00:00:00 2001
From: elong <elong@jumpmind.com>
Date: Fri, 30 Mar 2018 10:36:01 -0400
Subject: [PATCH] 0003508: Purge should use nolock dirty reads for min max
 range

---
 .../java/org/jumpmind/symmetric/service/impl/PurgeService.java  | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/PurgeService.java b/symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/PurgeService.java
index 590bf74e99..3ef9f0a9c4 100644
--- a/symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/PurgeService.java
+++ b/symmetric-core/src/main/java/org/jumpmind/symmetric/service/impl/PurgeService.java
@@ -322,7 +322,7 @@ private int purgeByMinMax(long[] minMax, long minGapStartId, MinMaxDeleteSql ide
                 case STRANDED_DATA_EVENT:
                     deleteSql = getSql("deleteStrandedDataEvent");
                     args = new Object[] { minId, maxId, cutoffTime, minId, maxId };
-                    argTypes = new int[] { idSqlType, idSqlType, Types.TIMESTAMP };
+                    argTypes = new int[] { idSqlType, idSqlType, Types.TIMESTAMP, idSqlType, idSqlType };
                     break;
             }