What happens
reference/database/transaction.md documents delete_audit_logs_before with an example body that includes a table parameter:
{
"operation": "delete_audit_logs_before",
"schema": "dev",
"table": "dog",
"timestamp": 1598290282817
}
On the default storage engine (RocksDB) that request errors. dataLayer/harperBridge/ResourceBridge.ts rejects a table-scoped audit/transaction-log deletion on RocksDB with a 400: all tables in a database share one transaction log, so the operation cannot be scoped to one table. A reader who copies the documented example gets a failure.
What is already correct
The same section already carries a v5.2.0 version badge stating that the operation is unsupported with table on RocksDB. So the warning landed; the example immediately below it was never updated to match. The fix is to drop the table line from the example body (and, if the surrounding prose implies table scoping, adjust that too), not to add a new warning.
Verified
HarperFast/documentation origin/main at 677ad213d (2026-08-31) — badge present, example still shows "table": "dog".
HarperFast/harper origin/main — the RocksDB guard that makes the example fail is live and unchanged.
Searched the documentation tracker for delete_audit_logs_before, table RocksDB transaction log, and audit log across all states: no existing issue covers this.
Found by exploratory QA (finding F-310); triaged 2026-09-02.
What happens
reference/database/transaction.mddocumentsdelete_audit_logs_beforewith an example body that includes atableparameter:{ "operation": "delete_audit_logs_before", "schema": "dev", "table": "dog", "timestamp": 1598290282817 }On the default storage engine (RocksDB) that request errors.
dataLayer/harperBridge/ResourceBridge.tsrejects a table-scoped audit/transaction-log deletion on RocksDB with a 400: all tables in a database share one transaction log, so the operation cannot be scoped to one table. A reader who copies the documented example gets a failure.What is already correct
The same section already carries a
v5.2.0version badge stating that the operation is unsupported withtableon RocksDB. So the warning landed; the example immediately below it was never updated to match. The fix is to drop thetableline from the example body (and, if the surrounding prose implies table scoping, adjust that too), not to add a new warning.Verified
HarperFast/documentationorigin/mainat677ad213d(2026-08-31) — badge present, example still shows"table": "dog".HarperFast/harperorigin/main— the RocksDB guard that makes the example fail is live and unchanged.Searched the documentation tracker for
delete_audit_logs_before,table RocksDB transaction log, andaudit logacross all states: no existing issue covers this.Found by exploratory QA (finding F-310); triaged 2026-09-02.