Preserve concurrent updates during Atomic table saves

michielbdejong commented

2026-10-19 16:39:26 +02:00

Owner

The in-memory Atomic adapter can lose an unrelated external update while awaiting field setters or a delayed persistence callback. Pass a synchronous preparation function to persistence, recheck membership/schema/edited-field baselines at application, and rebase only the validated patch onto the latest Resource. Overlapping edits and deletion reject while retaining the draft; retry remains available.

This fixes the defect from #54, whose original /atomic-reuse demo now lives at /atomic-reuse-memory. It does not change the separate real Atomic Server adapter now at /atomic-reuse; #45 has already been completed. Native commit actions are retained, but local preparation does not add a remote conditional-commit guarantee.

Updated against current main, including the move to experimental/. Also restores documentation repository URLs accidentally changed by that move.

Validation on the updated branch:

All 380 unit/integration tests pass, including deterministic setter/persistence interleavings and concurrent adapter cases.
All 12 Atomic in-memory browser regressions pass.
Atomic and runtime TypeScript checks pass.
Atomic app production build and git diff --check pass.

Closes #54.

The in-memory Atomic adapter can lose an unrelated external update while awaiting field setters or a delayed persistence callback. Pass a synchronous preparation function to persistence, recheck membership/schema/edited-field baselines at application, and rebase only the validated patch onto the latest Resource. Overlapping edits and deletion reject while retaining the draft; retry remains available. This fixes the defect from #54, whose original `/atomic-reuse` demo now lives at `/atomic-reuse-memory`. It does not change the separate real Atomic Server adapter now at `/atomic-reuse`; #45 has already been completed. Native commit actions are retained, but local preparation does not add a remote conditional-commit guarantee. Updated against current main, including the move to `experimental/`. Also restores documentation repository URLs accidentally changed by that move. Validation on the updated branch: - All 380 unit/integration tests pass, including deterministic setter/persistence interleavings and concurrent adapter cases. - All 12 Atomic in-memory browser regressions pass. - Atomic and runtime TypeScript checks pass. - Atomic app production build and git diff --check pass. Closes #54.

michielbdejong added 1 commit

2026-10-19 16:39:26 +02:00

Preserve concurrent Atomic table updates at the persistence boundary 8c437b9250

michielbdejong added 2 commits

2026-10-28 12:15:07 +01:00

Merge remote-tracking branch 'origin/main' into codex/finish-pr62 d0d7c2dd17

# Conflicts:
#	docs/atomic-data-mapping.md
#	tests/unit/atomic-table.test.ts

Refresh save-race documentation and restore repository links 0277c6c39d

michielbdejong merged commit 0426b86dd9 into main

2026-10-28 13:04:50 +01:00

michielbdejong referenced this pull request from a commit

2026-10-28 13:04:51 +01:00

Merge pull request 'Preserve concurrent updates during Atomic table saves' (#62) from codex/issue-54-atomic-save into main

Rows
Columns

Preserve concurrent updates during Atomic table saves #62