Root / Assembly / ARCCore / AREnumType / DocumentationOnlyEnum / ARConcepts / _Member / AdHocQuery



DescriptionThe concept of a Client doing an ad-hoc query against (normally) a ArmDB.
Background: Ordinarily, Subscription are 'permanently' on-going, and ad-hoc queries are done in-memory locally by each client, but since there is just some small differences conceptually in doing ad-hoc queries over a TCP/IP connection, AgoRapide implements also this mechanism.

AdHocQuery is most relevant against an ArmDB storing its data in a PRich, (The query itself is sent as a collection of Subscription elements, and when server answers with IsAtEndOfStream the client can close the query connection)

TODO: Not implemented as of May 2020.
TODO: Clarify difference between ClientUpdatePosition and FromTime / ToTime.

Note that there would be little meaning in doing an ad-hoc query against a CoreDB because the core only stores single PropertyStream-lines, meaning it would have to read through the whole database from start to end in order to ensure that all data is found (the query would be an O(n) one instead of O(1)).

Hint: If you are concerned about the risk of having to do O(n) queries, you are recommended to use an established key-value storage (like AWS DynamoDB or Azure Cosmos DB) as your main database, and sync AgoRapide to that database.
See ARCSync for more information about this.

TOOD: Could potentially be deleted as ARConcept when a Query-metod is implemented somewhere.

3 items

Generated 2020-10-13 11:11:01.032 UTC