chain-insights 0.56.2 → 0.56.3
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/package.json
CHANGED
|
@@ -302,6 +302,7 @@ The server serves five read-only catalog calls: `CALL db.labels()`, `CALL db.rel
|
|
|
302
302
|
- A reply holds at most 200 rows, whatever the `LIMIT`.
|
|
303
303
|
- A facts read has one relationship and no hop. For a walk, go to topology.
|
|
304
304
|
- A facts read takes no `ORDER BY`. Rows come in the server's own order. Sort the page yourself.
|
|
305
|
+
- A facts read aggregates with `count()` and `sum()` only, over the whole page: no grouping key, no `min()`, `max()` or `avg()` (`unsupported facts query shape`). Read the rows and compute the rest yourself.
|
|
305
306
|
- Every row and both endpoints carry `network`, the query's `network`. A filter on it is no anchor: it never replaces the pair and the day.
|
|
306
307
|
- Facts serves no kind. A read that names `:Account` or `:Contract` is refused with `facts_no_anchor`: ask `USE topology` for the kind, or `USE chain` for `is_contract` and `nonce`.
|
|
307
308
|
- A facts read covers one day. For more days, send one read for each day.
|