Skip to content

fix(migrations): keep a deleted principal's versions - #66

Merged
TheGreatAxios merged 1 commit into
cl-9427-memory-purge-and-forget-must-remove-or-redact-the-rawfrom
cl-9426-memory-deleting-a-principal-must-not-delete-the-memory
Sep 27, 2026
Merged

TheGreatAxios merged 1 commit into
cl-9427-memory-purge-and-forget-must-remove-or-redact-the-rawfrom
cl-9426-memory-deleting-a-principal-must-not-delete-the-memory

Conversation

@TheGreatAxios

Copy link
Copy Markdown
Contributor

Closes CL-9426

The version author foreign key cascaded, so deleting a principal deleted every version they wrote and left empty documents. Migration 0010 switches it to ON DELETE SET NULL only while it still cascades, so a replay is a no-op. e2e covers the delete.

The version author foreign key cascaded, so deleting a principal deleted every version they wrote and left empty documents. Migration 0010 switches it to ON DELETE SET NULL while it still cascades, so a replay is a no-op.
@TheGreatAxios
TheGreatAxios added this pull request to stack #69 September 27, 2026 18:34
@TheGreatAxios
TheGreatAxios merged commit a1c1f40 into main Sep 27, 2026
2 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant