@lotics/app-sdk 0.126.0 → 0.126.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/docs/data_fetching.md +3 -3
- package/docs/queries.md +2 -2
- package/package.json +1 -1
package/docs/data_fetching.md
CHANGED
|
@@ -247,8 +247,8 @@ Reads paginate two different ways, and the difference is load-bearing:
|
|
|
247
247
|
matters — **never skips or duplicates a row as the set shifts** under concurrent inserts/deletes.
|
|
248
248
|
The cursor is internal: the hook sends it and reads the next one back; you never see it. The
|
|
249
249
|
server keysets the sort's column keys (the runtime `sort`, else the template's own order on the
|
|
250
|
-
columns it projects,
|
|
251
|
-
key it can't seek. So an infinite feed needs **no
|
|
250
|
+
columns it projects), breaking their ties by when each row was made, then by the record id, and
|
|
251
|
+
falls back to offset transparently for a `first` key it can't seek. So an infinite feed needs **no
|
|
252
252
|
dedupe** — key rows by `__source_record_id` for stable React keys, not to guard against repeats.
|
|
253
253
|
- **`page`, `limit`, `queryAll` and manual `rpc("query", { limit, offset })` use offset
|
|
254
254
|
pagination** — count `offset` rows, skip them, return the next page. Two consequences a keyset
|
|
@@ -261,7 +261,7 @@ Shared by both:
|
|
|
261
261
|
says the cap cut the result, so a screen can say so instead of quietly under-reporting.
|
|
262
262
|
- **Always give a paginated query a deterministic order.** With no `ORDER BY` (neither in the
|
|
263
263
|
template nor runtime `sort`), row order is unspecified — offset pages may overlap or skip rows
|
|
264
|
-
even without concurrent writes, and keyset falls back to the
|
|
264
|
+
even without concurrent writes, and keyset falls back to the order the rows were made in. Sort by a stable
|
|
265
265
|
column (unique where possible).
|
|
266
266
|
|
|
267
267
|
Offset-only (`page`, `limit`, and manual `rpc`):
|
package/docs/queries.md
CHANGED
|
@@ -640,8 +640,8 @@ index that is:
|
|
|
640
640
|
|
|
641
641
|
- **diacritics- and case-insensitive** (`"da nang"` matches `"Đà Nẵng"`),
|
|
642
642
|
- **trigram-indexed** (scales to large tables — unlike `contains`, which scans),
|
|
643
|
-
- **near-total field coverage** — indexes text, number, date (ISO plus `MM/dd/yyyy
|
|
644
|
-
`dd/MM/yyyy` forms), select option labels, member names, link display text, and
|
|
643
|
+
- **near-total field coverage** — indexes text, number, date (ISO plus `MM/dd/yyyy`,
|
|
644
|
+
`dd/MM/yyyy` and `15 Jan 2026` forms), select option labels, member names, link display text, and
|
|
645
645
|
formula/rollup/lookup values; boolean and files cells are not indexed,
|
|
646
646
|
- multi-term: the query splits on whitespace (max 10 terms), all terms must match (AND).
|
|
647
647
|
|
package/package.json
CHANGED