# Live, deleted and history in an append-only file Writing the same key again edits it, writing the key with _apagado: true deletes it, and the history of every change stays in the file. November 13, 2026 · jsonW 1.3.11 · https://jsonw.org/en/newsroom/live-deleted-history ## The problem In CSV and JSON, editing a record means rewriting the file, and the old value is lost. To know who changed what, you need a separate audit table. ## How jsonW solves it A .jsw file only appends. An edit is the same key written again; a deletion is the key written with _apagado: true. Compacting rewrites only what is current into a new file and leaves the history in the original. ``` $ wjsw ver dup.jsw {id:1,nome:"a",_apagado:null} {id:2,nome:"b",_apagado:null} {id:1,nome:"a2",_apagado:null} {id:2,nome:null,_apagado:true} ``` Real output: record 1 was edited from "a" to "a2" and record 2 was deleted. The history shows up as it is, row after row. ## Where it is Writing with _apagado works today. The "current only" view by key and compaction exist in the core, but in version 1.3.11 they have no command in wjsw and no function in the public ABI. Read the full section in the paper: https://jsonw.org/paper/en#ciclo