/ doc / DocFrag / ARCCore.ARConcepts.AdHocQuery / Description

Description

Edit keys at this level only

= The concept of a -Client- doing an ad-hoc query against (normally) a -ArmDB-.0x000D0x000ABackground: 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.0x000D0x000A0x000D0x000A-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)0x000D0x000A0x000D0x000ATODO: Not implemented as of May 2020.0x000D0x000ATODO: Clarify difference between -ClientUpdatePosition- and -FromTime- / -ToTime-.0x000D0x000A0x000D0x000ANote 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)).0x000D0x000A0x000D0x000AHint: 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 Apache Kafka, AWS DynamoDB or Azure Cosmos DB) as your main database, and sync AgoRapide to that database.0x000D0x000ASee -ARCSync- for more information about this.0x000D0x000A0x000D0x000ATOOD: Could potentially be deleted as ARConcept when a Query-metod is implemented somewhere.

Edit keys at all sub levels.
NOTE: Edits are always additive. Use 'Invalid' in order to delete keys.

Generated 2025-08-25 23:29:59.622 UTC