tursodatabase / tursodatabase/libsql
Invalidate baton and rollback transactions on transport error
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
If we execute a SQL statement on server side, but there's a transport error (serialization or network failure), the server just keeps going. We should look into adopting Postgres-style semantics where server faults terminate the connection and rollback active transactions. For us, that would mean invalidating the baton and rolling back transactions.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files or tests. Start by tracing server-side SQL execution, transport and serialization error handling, and the lifecycle of the baton and active transactions. Done means the specified failures invalidate the baton and roll back active transactions, with behavior matching the intended Postgres-style semantics.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- postgres, sql
- Domain
- backend, databases, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100