Thank you for taking time to present these easy-to-understand walk-throughs. They are very helpful.
The HyperBee queries, I am trying to understand if they work more like a
one time query & response paradigm, or
like a filtered partial sync stream?
To illustrate what I mean, say you have database of numbers 1 to 10. Then you make a query for the even numbers from that core/db.
Then you get the response [2, 4, 6, 8, 10].
Typically, underneath these numbers/blocks are downloaded locally (partial sync).
Now, you append few more numbers to the remote database 11 to 20, say. Then what happens?
Would I have to run the query again to get these updates? if so would it get all the numbers starting from 2, 4, 6 etc. again or only the latest ones, starting from 12, 14, 16 etc.?
or does it keep syncing the updates forever (ala replicate but with filtering based on the query) and streaming the results, like a continuous change log?
If filtered partial sync stream is the way it works, then it is indeed a very powerful feature, since essentially it is providing a selective view of the database with continuous change log
Thank you for taking time to present these easy-to-understand walk-throughs. They are very helpful.
The
HyperBeequeries, I am trying to understand if they work more like aTo illustrate what I mean, say you have database of numbers 1 to 10. Then you make a query for the even numbers from that core/db.
Typically, underneath these numbers/blocks are downloaded locally (partial sync).
Now, you append few more numbers to the remote database 11 to 20, say. Then what happens?
Would I have to run the query again to get these updates? if so would it get all the numbers starting from 2, 4, 6 etc. again or only the latest ones, starting from 12, 14, 16 etc.?
or does it keep syncing the updates forever (ala
replicatebut withfilteringbased on the query) and streaming the results, like a continuous change log?If
filtered partial sync streamis the way it works, then it is indeed a very powerful feature, since essentially it is providing aselective viewof the database withcontinuous change log