Fix for empty cancelled write transactions leaving scheduled updates

gitlab #15

Change-Id: I844dab6a59df56f2097a507bcd6b6d3ec75124b1
(cherry picked from commit 4b3689543c26ac085970dd200218a9a6c122467b)

diff --git a/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java b/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java
index 70e2cb10dd603122da7737bab85a2ea88bdc631a..52a508b6f417f2c8e3cccee30dc867c01c0dd5b8 100644 (file)
--- a/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java
+++ b/bundles/org.simantics.db.procore/src/fi/vtt/simantics/procore/internal/State.java
@@ -296,6 +296,9 @@ class State {
                     }
                     // This will send and accept the reverse change set.
                     transactionToken.cancelEnd(session.writeSupport, null, session.clusterStream);
+                } else {
+                    queryProvider.performDirtyUpdates(graph);
+                    queryProvider.performScheduledUpdates(graph);
                 }
             }
             session.writeSupport.clearMetadata();