Philipinho 89ee3714ac feat(base): add /bases/rows/count with estimate and capped-exact modes ...

Row-count display on a filtered view shouldn't force a full COUNT(*) on
every list fetch. New endpoint returns either an EXPLAIN-plan estimate
(default, ~1ms, no execution) or a LIMIT-capped exact count that short-
circuits to `{ capped: true }` once the match set passes EXACT_COUNT_CAP.
Clients call it in parallel with the rows query so the grid still paints
at its own pace.

- DTO + repo.countEstimate/countExact reusing the list predicate shape
- service picks the mode; controller mirrors the list Read ability check
- client hook keyed by filter/search/exact so a "show exact" toggle
  doesn't clobber the estimate cache

2026-04-24 12:11:29 +01:00

..

client

feat(base): add /bases/rows/count with estimate and capped-exact modes

2026-04-24 12:11:29 +01:00

server

feat(base): add /bases/rows/count with estimate and capped-exact modes

2026-04-24 12:11:29 +01:00