Commit message (Collapse) | Author | Age | |
---|---|---|---|
* | Use the ChildrenFetchedRole | Christian Mollekopf | 2015-11-30 |
| | |||
* | Provide status information about children fetch state | Christian Mollekopf | 2015-11-30 |
| | | | | The fetch state is per parent. | ||
* | Test model signals | Christian Mollekopf | 2015-11-30 |
| | |||
* | Debug output | Christian Mollekopf | 2015-11-30 |
| | |||
* | Only install the headers we need. | Christian Mollekopf | 2015-11-30 |
| | | | | We go rid of large parts of the header entanglements. | ||
* | ModelResult hasChildren, cleanup | Christian Mollekopf | 2015-11-30 |
| | |||
* | Cleanup | Christian Mollekopf | 2015-11-28 |
| | |||
* | Cleanup | Christian Mollekopf | 2015-11-28 |
| | |||
* | Removed most uses of SyncListResult and brought back the | Christian Mollekopf | 2015-11-28 |
| | | | | dummyresourcetest | ||
* | list and count options for non-gui operations | Christian Mollekopf | 2015-11-27 |
| | |||
* | 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. | ||
* | Use the new model api in the benchmark and split tests up. | Christian Mollekopf | 2015-11-26 |
| | | | | This way it's possible to i.e. repeatedly only run the reading part. | ||
* | Avoid repeatedly opening the name db. | Christian Mollekopf | 2015-11-26 |
| | | | | | Although, the benchmarks say it doesn't really have an impact on performance. | ||
* | Separate the default index updater from other generic indexers | Christian Mollekopf | 2015-11-25 |
| | |||
* | Fixed modifications. | Christian Mollekopf | 2015-11-25 |
| | | | | Without this modifications are ignored also in incremental queries. | ||
* | Only use the parent index when it's available | Christian Mollekopf | 2015-11-25 |
| | |||
* | Less noise | Christian Mollekopf | 2015-11-25 |
| | |||
* | Optimize findLast | Christian Mollekopf | 2015-11-25 |
| | | | | | This just gave a 700% boost to query performance from ~2k to 14k reads per second... | ||
* | Use Query::parentProperty to express tree queries | Christian Mollekopf | 2015-11-24 |
| | | | | | That way we don't have to hardcode the parent property, and we can use the property to express non-tree queries as well. | ||
* | Separated DomainTypeAdaptorFactoryInterface | Christian Mollekopf | 2015-11-21 |
| | |||
* | Don't try to fetch more once the parent is fetched. | Christian Mollekopf | 2015-11-21 |
| | | | | We're not doing partial fetches yet | ||
* | Fixed build | Christian Mollekopf | 2015-11-21 |
| | |||
* | Moved facade implementation to cpp file | Christian Mollekopf | 2015-11-19 |
| | |||
* | Move implementations to the cpp file. | Christian Mollekopf | 2015-11-19 |
| | | | | | | | | I finally figured out how to do that with cpp files. It requires instantiating the code with all expected classes, but that's not a big problem since we know all types. This will hopefully greatly reduce the compiletimes... | ||
* | The parent is always an object, so we might as well make that explicit | Christian Mollekopf | 2015-11-19 |
| | |||
* | Loading data with the new model for the test client | Christian Mollekopf | 2015-11-19 |
| | |||
* | Use the new modelresult in the dummyclient | Christian Mollekopf | 2015-11-19 |
| | |||
* | fixup | Christian Mollekopf | 2015-11-18 |
| | |||
* | Don't use a smart pointer for the result provider | Christian Mollekopf | 2015-11-18 |
| | | | | We're not doing any lifetime management anyways. | ||
* | Facade cleanup | Christian Mollekopf | 2015-11-17 |
| | |||
* | Cleanup | Christian Mollekopf | 2015-11-15 |
| | |||
* | Working folder tree query | Christian Mollekopf | 2015-11-15 |
| | |||
* | Fixed clientapitest | Christian Mollekopf | 2015-11-15 |
| | |||
* | Query test adjustments | Christian Mollekopf | 2015-11-14 |
| | |||
* | DummyResourceTest and QueryTest are passing | Christian Mollekopf | 2015-11-13 |
| | | | | sync has been removed from the query code and is now a separate step | ||
* | It's starting to work | Christian Mollekopf | 2015-11-13 |
| | |||
* | A result model | Christian Mollekopf | 2015-11-10 |
| | | | | | The result model drives the data retrieval and provides the interace for consumers | ||
* | Cleanups | Christian Mollekopf | 2015-11-10 |
| | |||
* | Added a folder type | Christian Mollekopf | 2015-11-09 |
| | |||
* | Docs | Christian Mollekopf | 2015-11-08 |
| | |||
* | Fixed warnings | Christian Mollekopf | 2015-11-08 |
| | |||
* | Implemented removeIndex | Christian Mollekopf | 2015-11-05 |
| | |||
* | Fixed shutdown and synchronize commands | Christian Mollekopf | 2015-10-31 |
| | |||
* | docs | Christian Mollekopf | 2015-10-30 |
| | |||
* | Updated the index on modifications and removals. | Christian Mollekopf | 2015-10-29 |
| | | | | Misses tests. | ||
* | Merge branch 'feature/preprocessor' into develop | Christian Mollekopf | 2015-10-29 |
|\ | |||
| * | Cleanup changereplay, and replay revision 1 as the first | Christian Mollekopf | 2015-10-28 |
| | | |||
| * | Correctly execute modifications and removals | Christian Mollekopf | 2015-10-28 |
| | | | | | | | | ... also if there are intermediate revisions. | ||
| * | Reuse the existing transaction | Christian Mollekopf | 2015-10-28 |
| | | |||
| * | Made pipeline preprocessing synchronous. | Christian Mollekopf | 2015-10-28 |
|/ | | | | | | | | | | | | | | | | Instead of having the asynchronous preprocessor concept with different pipelines for new/modify/delete we have a single pipeline with synchronous preprocessors that act upon new/modify/delete. This keeps the code simpler due to lack of asynchronity and keeps the new/modify/delete operations together (which at least for the indexing makes a lot of sense). Not supporting asynchronity is ok because the tasks done in preprocessing are not cpu intensive (if they were we had a problem since they are directly involved in the round-trip time), and the main cost comes from i/o, meaning we don't gain much by doing multithreading. Costly tasks (such as full-text indexing) should rather be implemented as post-processing, since that doesn't increase the round-trip time directly, and eventually consistent is typically good enough for that. |