-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How many subscriptions? #4
Comments
Each template could be seen as a rule: Having a single query would mean having spare columns and reusing these spares across sibling templates (not sibling components: really sibling templates). With two queries we would have Derivation could leverage the nesting: derivation of the second query should not return retractions that are a consequence of the item being retracted, only retractions due to a change in title or status. Thus when the row for a component is retracted we don't get retractions for its children which is not useful. |
Another point to keep in mind: multiple queries -> multiple subscriptions -> multiple handlers It's not good. We must have 1 tx -> 1 ui transact -> 1 render. And/or we must be careful to not trigger on ui transacts. |
It will be one query per template. |
(todo list example)
If each component has its own query then for a todo-list of N items we get at least N+1 subscriptions (1 for the list and N for each item).
Having 2 queries sounds better; is it even doable to have only 1 query?
The text was updated successfully, but these errors were encountered: