You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A SQL Query that is a subscription. SO if the results of the Query changes, then all Clients are told over HTTP ( maybe SSE ) or maybe actually NATS.
working out what mutation to the DB, effects what Queries is a tough one.
so maybe a brute force approach of having scored procedures. In other work all possible Queries are told to the system. In fact they could be stored in NATS, and also synced, but that another story.
The idea is that for each possible query, a backend taks just runs them every few seconds, with all possible params, and then tells clients when it's changed. It's nuts because the possible parmataters are infinite, but what is they were not ? For example a classic query of "give me all books by this author". The number of authors is know, because its also in the db.
what will not work is a query where the param is time or date based, like "give me all books by author X, where the book was published after 01-02-2024".
It interesting that NATS streams know the history of every possible query. Thats means the cardinality of possible queries is known. mhhh
The text was updated successfully, but these errors were encountered:
I dont think this does subscriptions ?
A SQL Query that is a subscription. SO if the results of the Query changes, then all Clients are told over HTTP ( maybe SSE ) or maybe actually NATS.
working out what mutation to the DB, effects what Queries is a tough one.
so maybe a brute force approach of having scored procedures. In other work all possible Queries are told to the system. In fact they could be stored in NATS, and also synced, but that another story.
The idea is that for each possible query, a backend taks just runs them every few seconds, with all possible params, and then tells clients when it's changed. It's nuts because the possible parmataters are infinite, but what is they were not ? For example a classic query of "give me all books by this author". The number of authors is know, because its also in the db.
what will not work is a query where the param is time or date based, like "give me all books by author X, where the book was published after 01-02-2024".
It interesting that NATS streams know the history of every possible query. Thats means the cardinality of possible queries is known. mhhh
The text was updated successfully, but these errors were encountered: