pettiInvestigate SQLite bug reports without editing the evidence
A database attached to a bug report can explain what a screenshot cannot. Keep the source intact while narrowing the problem to a specific record and a repeatable query.
Establish what the file represents
Record the app version, export or capture time and reproduction steps supplied with the file. Confirm it is SQLite; a .db suffix alone is not sufficient. If the report came from a running application, ask for its supported backup or export rather than an isolated main file that may omit committed WAL content.
Inspect in a predictable order
- Open in Petti with the lock closed and inspect Database Info.
- Choose the relevant table and inspect Structure before assuming column meanings.
- Search for a known record or add a precise column filter.
- Write a small SELECT query that reproduces the observation.
- If you have suitable before-and-after captures, compare supported tables and include any partial-result notices.
Keep the report useful
Include expected versus observed behavior, the relevant table and key, the exact SQL and the number of matching records. A result of zero rows means the query found no match under those conditions; it does not establish that the event never occurred. Record filters and date interpretation so another person can repeat the check.
For a focused table extract, use Filtered Result or Selected Rows when exporting instead of Entire Table. Inspect the output before sharing. Export scope does not automatically remove private columns, anonymize identities or scrub JSON payloads.
Know what inspection cannot establish
A snapshot comparison is not a forensic audit trail, and an SQL query cannot recover an action that was never persisted. Read-only access prevents writes through Petti but does not stop another process from changing the source. Work from a stable SQLite-aware capture when repeatability matters.
This workflow uses free viewing and query features. If testing a repair requires editing, use a separate disposable copy and an editing license. First try the query exercise and comparison exercise.
Updated