A cypher field failed to seal/open, or the keyring passed to open() is itself unusable.
table empty means the second case — the message drops the “of table” clause then.
A write carried an image whose bytes differ from the file already stored under the same content
hash. The address is a 64-bit FNV-1a, so two different images can collide; the engine refuses the
later one instead of letting it resolve to the earlier one’s bytes. physical_path is the file
name the two share.
The log file behind an open handle is no longer the file at its path: something outside this
engine unlinked or replaced it — a git checkout of a data directory kept under version
control, a restore from backup, a stray mv. An append would land in the orphaned inode and
vanish with it, so the engine refuses the write; the database has to be reopened to attach to
the file now at that path.
A record cannot be placed in a partition file: its partitionBy value cannot name one, or the
write would move an existing key out of the partition it already lives in.
A delete refused because an on_delete: 'restrict' relation still has a live record
referencing the key being deleted. referencing is the count of records found still pointing
at it — capped at the same sample the diagnostic report uses, never a full scan’s whole count.
A write refused because it broke an enforce: true relation — from.field’s new value has no
matching record on the to side. value is the offending value’s JSON text.