You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Retire IMPLEMENTATION_BUGS_AND_RESOLUTIONS.md or fold it into the conformance statement #169
IMPLEMENTATION_BUGS_AND_RESOLUTIONS.md is a bug-by-bug narrative from the design phase. It still names the project turso-java and describes intermediate states that later PRs changed (for example the transaction lifecycle was rewritten in #99/#152 and now lives in AGENTS.md §2 and the conformance divergences).
Its still-valuable content — the why behind the remote-model compromises (one-shot close, lazy begin, baton rotation, no hidden session stream) — is already largely captured in AGENTS.md and upstream-xerial_sqlite-jdbc.manifest. What remains unique is a handful of performance notes (Jackson databind vs. DirectHranaJsonCodec, column-lookup hashing, parameter storage).
Proposed change
Fold the still-relevant divergence rationale into the canonical conformance statement (see the conformance-statement subissue) and delete the rest. Alternatively retitle and trim it to a short "design rationale" document. Recommend folding plus deleting.
Acceptance criteria
The document no longer references turso-java.
Its surviving rationale lives in exactly one canonical place, not duplicated across three documents.
Activity
magnusp commentedon Oct 24, 2026
Implemented in #180 (consolidated into the conformance statement by #181), merged to main in fc3f819.