Repository navigation
Query and Scan: a TableName outside the pattern beside Limit 0 answers the table name, where DynamoDB answers the Limit fault #905
Description
What ExtendDB does
The table name gate of #830 runs first in authorize_request (crates/server/src/table_name_gate.rs), before the handler checks Limit. A request with both faults gets the table name fault.
Measured on 2026-11-06 at the head of #830 (ccdae81), SQLite and PostgreSQL:
| Request | ExtendDB |
|---|---|
Scan, TableName: "a b", Limit: 0 |
1 validation error detected: Value 'a b' at 'tableName' failed to satisfy constraint: Member must satisfy regular expression pattern: [a-zA-Z0-9_.-]+ |
Query, TableName: "a b", Limit: 0, a key condition |
the same sentence |
The #830 review reports that the merge base (25ee109) answered the Scan request with ResourceNotFoundException.
What DynamoDB does
Measured in us-east-1 on 2026-11-06, with SDK parameter validation off. Both requests answer the Limit fault, the same sentence as Limit: 0 on an existing table:
1 validation error detected: Value at 'Limit' failed to satisfy constraint: Member must have value greater than or equal to 1
Suggested fix
For Query and Scan, check Limit before the table name pattern, or let the gate pass a request whose Limit is below 1 on to the handler. Which other members DynamoDB checks before the table name was not measured. #563 covers the two text forms of the Limit sentence and #778 covers Limit beside an ExpressionAttributeValues fault.
Activity