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
hmm.. even that doesn't work well since it assumes we know the next issue id.
This would be ideal:
db.comments.filter({issueId: xxx});
but filter is currently not hoisted (hoisted = run by the backing data source). We need hoisted filters so we don't scan the entire source set.
We'll need to re-implement something like SourceExpressions from Aphrodite into Materialite so we can hoist operators to the provided backend (SQL, IndexedDB, memory, other).
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
While implementing Linearite I ran into this problem --
Deleting an issue requires deleting all comments. Displaying an issue requires displaying all comments.
The comments collection is sorted by
issueId
and thencreatedTime
which means we can quickly look up all issues for a comment.We, however, don't have a hoisted way to bound this.
We can do:
but we don't know the correct value for
y
since we don't know when the comments for the issue end.We need:
hmm.. even that doesn't work well since it assumes we know the next issue id.
This would be ideal:
but filter is currently not hoisted (hoisted = run by the backing data source). We need hoisted filters so we don't scan the entire source set.
We'll need to re-implement something like SourceExpressions from Aphrodite into Materialite so we can hoist operators to the provided backend (SQL, IndexedDB, memory, other).
Beta Was this translation helpful? Give feedback.
All reactions