feat(query): support SQLite statement conflict policies #3
Loading…
Reference in a new issue
No description provided.
Delete branch "feat/sqlite-statement-conflicts"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
OpenSpec
Change:
sqlite-statement-conflicts(spec-driven). 7/7 tasks complete.Scope
.or("ABORT" | "FAIL" | "IGNORE" | "REPLACE")on INSERT and UPDATE, compatible with RETURNING and UPDATE WHERE. OR ROLLBACK and UPSERT excluded.Checkpoints
2d93d14implementation and tests.31155dcdocumentation and completed OpenSpec artifacts.ec5db98Merge parent branch transaction fix without history rewrite.389ea02Test statement conflict policies in nested transactions.Verification
bun run check: passed after parent fix.bun run lint: 0 errors, 14 existing warnings.bun test: 107 passed, 0 failed.openspec validate sqlite-statement-conflicts: passed; apply progress 7/7.git diff --check: passed.Cloudflare D1 behavior not independently exercised; SQLite runtime semantics tested with Bun.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.Merge
Merge the changes and update on Forgejo.Warning: The "Autodetect manual merge" setting is not enabled for this repository, you will have to mark this pull request as manually merged afterwards.