Fixed the lost update scenario

If we get a fetchMore right between when the revision was updated and
the incrementalQuery actually running, we ended up loosing the update
because the result provider ended up with a too recent revision after
the additional initial query.

1 files changed, 14 insertions, 1 deletions

diff --git a/common/queryrunner.h b/common/queryrunner.h
index e449570..52b5e2d 100644
--- a/common/queryrunner.h
+++ b/common/queryrunner.h
@@ -35,6 +35,16 @@ class QueryRunnerBase : public QObject
 public:
     typedef std::function<void(Sink::ApplicationDomain::ApplicationDomainType &domainObject)> ResultTransformation;
 
+    /// Disable query updates on revision change. Used for testing only.
+    void ignoreRevisionChanges(bool ignore) {
+        mIgnoreRevisionChanges = ignore;
+    }
+
+    /// Manually triger a revision change. Used for testing only.
+    void triggerRevisionChange() {
+        revisionChanged();
+    }
+
 protected:
     typedef std::function<KAsync::Job<void>()> QueryFunction;
 
@@ -52,7 +62,9 @@ protected slots:
      */
     void revisionChanged()
     {
-        run().exec();
+        if (!mIgnoreRevisionChanges) {
+            run().exec();
+        }
     }
 
 private:
@@ -65,6 +77,7 @@ private:
     }
 
     QueryFunction queryFunction;
+    bool mIgnoreRevisionChanges{false};
 };
 
 /**