Use a queryrunner to execute queries.

The queryrunner is responsible for running queries and keeping them
up to date. This is required for self-updating queries.

To get this to work properly the ResultProvider/emitter had to be fixed.
The emitter now only lives as long as the client holds a reference to
it, allowing the provider to detect when it is no longer necessary to
keep the query alive (because noone is listening).

In the process various lifetime issues have been fixed, that we're
caused by lambdas capturing smartpointers, that then extended the
lifetime of the associated objects unpredictably.

1 files changed, 1 insertions, 0 deletions

diff --git a/common/CMakeLists.txt b/common/CMakeLists.txt
index b06718f..a97c7f9 100644
--- a/common/CMakeLists.txt
+++ b/common/CMakeLists.txt
@@ -29,6 +29,7 @@ set(command_SRCS
     clientapi.cpp
     commands.cpp
     console.cpp
+    facade.cpp
     pipeline.cpp
     domainadaptor.cpp
     resource.cpp