db-rowcap
Row cap
shipped
The sections below are generated from the CLI (methodology 0.3-draft, CLI 0.3.0); the same text is printed by sealmark explain db-rowcap.
- pack
db- weight
- scored
- scope
- server
- decided by
- response
- since
- 0.2-draft (methodology 0.3-draft)
- replaces
cap-timeout(retired id)- config keys
checks.db-rowcap.enabledchecks.db-rowcap.row_capchecks.db-rowcap.severity
Probes
big-tableSELECT id, payload FROM big_table ORDER BY id
Settings and thresholds
Every check also takes checks.db-rowcap.enabled and checks.db-rowcap.severity; they are described once in the configuration reference.
| Threshold | Default | Set with | Standard |
|---|---|---|---|
row_cap | 10000 | checks.db-rowcap.row_cap | locked |
| Key | Default | Standard | Meaning |
|---|---|---|---|
checks.db-rowcap.row_cap | 10000 | locked | Rows a single response may return before db-rowcap fails (standard 10000). |
How the verdict is established
- Scoring. scored: pass = 1 point, part = 0.5, fail = 0. A fail lowers the pack's percentage but never caps the letter.
What to fix
Enforce a maximum number of returned rows in the server (a LIMIT it adds, or a fetch that stops at the cap) and say in the response when the result was truncated.
False positives
A response the harness cannot receive at all (the connection drops) is counted as no confirmed cap. A server that refuses the probe without a recognizable limit message is not measured, not failed.
False negatives
A cap is judged on one query against a 200 000-row table.