Original working file
reference/assignment-walkthrough.txt
Code and working example pages keep their original identifiers and sample text. The lesson and file guidance explain them in your language.
LOCAL JSON PRACTICE — FILLED EXAMPLE
Illustration, not a report of a test run for you: open practice/index.html. The source has IDs 1 and 2; the restore target is empty. Download its JSON backup, choose that file in the restore target and compare both IDs and complete note text. An invalid-backup.json attempt must leave the target unchanged.
Use Add to include ID 3, Restore check: turquoise notebook. Export again, clear only the disposable target with its supplied control and restore the new file: target IDs 1, 2 and 3 should match the source. Record your own actual results. recovery-plan.csv separates this local JSON exercise from the optional PostgreSQL table archive and from uploads, accounts and provider settings.
OPTIONAL POSTGRESQL EXTENSION
ILLUSTRATIVE WORKED WALKTHROUGH
These steps explain a complete approach. They are not a claim that this live provider/account test was performed for you. Use your own project and record your actual observations.
1. Seed the two known rows only in the source practice database. Export the named table, inspect the archive contents for its table/data/constraint entries and retain its hash privately. This export does not include other tables, roles, grants, auth or uploaded file bytes.
2. Restore into a different empty disposable database after checking its identity. Read ID 1 and the exact note 'Restore check: turquoise notebook', plus ID 2. Verify the source remains unchanged. A table-already-exists error is a reason to use another empty target, not to add destructive cleanup flags.
3. Add ID 3 with a new distinctive note, make a new archive and restore into another fresh target. Check all three exact rows. Complete the separate recovery plan for missing uploads/auth/permissions; do not claim that this one-table exercise recovered those systems.