| Commit message (Collapse) | Author | Age |
|---|
| | |
|
| |
|
|
|
| |
...we used to accidentally move external blobs after the property was
lost when storing the modificatoin in the queue.
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Test Plan: cmake configure passes without a hard error.
Reviewers: cmollekopf, #kde_pim
Reviewed By: cmollekopf, #kde_pim
Subscribers: dvratil, cmollekopf
Differential Revision: https://phabricator.kde.org/D4443
|
| | |
|
| |
|
|
| |
initial fetch.
|
| |
|
|
|
| |
We often let removal updates through and expect the model to deal with
superfluous updates, this now actually implements that.
|
| |
|
|
|
|
| |
Some filters need to maintain state between runs in order to be able to
emit only what has changed. This now also make reduction work for live
queries.
|
| | |
|
| |
|
|
|
| |
The uid is not existing for the mail and the threading requires a
messageId.
|
| | |
|
| |
|
|
| |
threads.
|
| |
|
|
| |
After the initial bloom, it should turn into a regular filter.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
| |
To have hierarchical debug output we have to pass around something at
run-time, there is no reasonable alternative. Log::Context provides the
identifier to do just that and largely replaces the debug component
idea.
|
| |
|
|
| |
... so we can use that information in fetchMore.
|
| | |
|
| |
|
|
|
|
| |
Instead we make it part of the plugin.
This ensure we also have access to the proper capabilities when creating
a resource via sinksh.
|
| | |
|
| |
|
|
| |
...to properly wrap references.
|
| | |
|
| |
|
|
|
|
|
|
| |
This allows us to make sure that references are not taken out of
context (the resource).
Because we need to use the type-specific accessors more we also ran into
a problem that we cannot "downcast" a reference with the change
recording still working, for that we have the cast<T>() operator now.
|
| |
|
|
|
| |
We cant take the identifier from the entity where we just cleared the
identifier.
|
| |
|
|
|
|
| |
When moving an entity to another resource we have to move the blob
properties to a temporary directory first, and that requires that we are
able to distinguish blob properties from the rest at runtime.
|
| | |
|
| | |
|
| |
|
|
|
| |
... because we really just enqueue the request and then wait for the
notification.
|
| | |
|
| |
|
|
|
|
|
| |
Instead of trying to actually flush queues, we send a special command
through the same queues as the other commands and can thus guarantee
that the respective commands have been processed without blocking
anything.
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| | |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This is the initial refactoring to improve how we deal with the storage.
It does a couple of things:
* Rename Sink::Storage to Sink::Storage::DataStore to free up the
Sink::Storage namespace
* Introduce a Sink::ResourceContext to have a single object that can be
passed around containing everything that is necessary to operate on a
resource. This is a lot better than the multiple separate parameters
that we used to pass around all over the place, while still allowing
for dependency injection for tests.
* Tie storage access together using the new EntityStore that directly
works with ApplicationDomainTypes. This gives us a central place where
main storage, indexes and buffer adaptors are tied together, which
will also give us a place to implement external indexes, such as a
fulltextindex using xapian.
* Use ApplicationDomainTypes as the default way to pass around entities.
Instead of using various ways to pass around entities (buffers,
buffer adaptors, ApplicationDomainTypes), only use a single way.
The old approach was confusing, and was only done as:
* optimization; really shouldn't be necessary and otherwise I'm sure
we can find better ways to optimize ApplicationDomainType itself.
* a way to account for entities that have multiple buffers, a concept
that I no longer deem relevant.
While this commit does the bulk of the work to get there, the following
commits will refactor more stuff to get things back to normal.
|
| | |
|
| | |
|
| | |
|
| | |
|
