Skip to content

Commit 2748967

Browse files
committed
tweaks
1 parent 4c9d8eb commit 2748967

1 file changed

Lines changed: 2 additions & 1 deletion

File tree

src/blog/tanstack-db-0.5-query-driven-sync.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -18,6 +18,7 @@ const { data: projectTodos } = useLiveQuery((q) =>
1818
.from({ todos })
1919
.join({ projects }, (t, p) => eq(t.projectId, p.id))
2020
.where(({ todos }) => eq(todos.status, 'active'))
21+
.where(({ projects }) => eq(projects.id, 123))
2122
)
2223

2324
// ...becomes these precise API calls automatically:
@@ -76,7 +77,7 @@ This isn't just fast filtering. It's **live queries** that incrementally maintai
7677

7778
Since [we released TanStack DB 0.1](/blog/tanstack-db-0.1) in July, we've gotten the same question over and over:
7879

79-
> "This looks great for loading normalized data once, but what if my `users` table has 100,000 rows? I can't load everything."
80+
> This looks great for loading normalized data once, but what if my `users` table has 100,000 rows? I can't load everything.
8081
8182
They're right. Before 0.5, collections loaded their entire dataset upfront. That works beautifully for many apps with datasets in the thousands of rows, but it's not a one-size-fits-all solution.
8283

0 commit comments

Comments
 (0)