tursodatabase/turso

Cached prepare statements don't work with concurrency

Open

#4,597 opened on Jan 11, 2026

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Rust (1,001 forks)github user discovery
bughelp wanted

Repository metrics

Stars
 (19,103 stars)
PR merge metrics
 (PR metrics pending)

Description

A cached prepared statement created with Connection::prepare_cached() returns BusySnapshot error if another concurrent connection modifies the database, essentially making it impossible to reuse a connection in a connect pool.

Contributor guide

Research direction
Investigate the `Connection::prepare cached()` method to understand how it caches prepared statements and why it fails under concurrent modifications. Look for interactions with the snapshot isolation or locking mechanisms.
Tech stack
rust
Domain
database
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
RustSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35