sink - A data access layer handling synchronization, caching and indexing

	Commit message (Collapse)	Author	Age
*	Use KAsync::Job as abstraction for the threading implementation	Christian Mollekopf	2015-12-27
\|
*	Threaded query runner implementation	Christian Mollekopf	2015-12-27
\| \| \| \| \| \| \| \| \|	All database access is now implemented in threads, to avoid blocking the main thread. The resource communication still resides in the main thread to keep the coordination simple. With it comes a test that ensures we don't block the main thread for too long.
*	Don't crash without metadata.	Christian Mollekopf	2015-12-22
\| \| \| \|	Used in tests.
*	Only load the properties we need.	Christian Mollekopf	2015-12-22
\| \| \| \|	...and adjust the test accordingly with what we expect.
*	The generator should produce values one by one.	Christian Mollekopf	2015-12-20
\| \| \| \| \|	k ...not all at once.
*	Avoid starting resources on non-live queries.	Christian Mollekopf	2015-12-19
\|
*	If we know what we want, we can get directly that.	Christian Mollekopf	2015-12-17
\|
*	Make queries by id work	Christian Mollekopf	2015-12-17
\|
*	Debug output	Christian Mollekopf	2015-12-17
\|
*	Fixed some warnings	Christian Mollekopf	2015-11-30
\|
*	Provide status information about children fetch state	Christian Mollekopf	2015-11-30
\| \| \| \|	The fetch state is per parent.
*	Debug output	Christian Mollekopf	2015-11-30
\|
*	Cleanup	Christian Mollekopf	2015-11-28
\|
*	Introduced a QueryRunner object	Christian Mollekopf	2015-11-27
	The QueryRunner object lives for the duration of the query (so just for the initial query for non-live queries, and for the lifetime of the result model for live queries). It's supposed to handle all the threading internally and decouple the lifetime of the facade.