tursodatabase/libsql

Query timing?

Open

#1,358 opened on Apr 29, 2024

View on GitHub
 (3 comments) (0 reactions) (0 assignees)C (16,744 stars) (490 forks)batch import
enhancementgood first issuehelp wantedquestion

Description

When you're executing a query asynchronously, it would be useful for the library itself to provide query timing information because it's hard to do that from the caller.

Contributor guide

Tech stack
csql
Domain
database
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
4
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
needs investigation
Prerequisites
C programmingFamiliarity with SQLite/libSQL internalsAsynchronous programming concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
20
Research direction
The issue requests adding query timing information. The contributor should first look for any existing timing mechanisms in the libSQL codebase, possibly in the query execution functions. They should also read the comments in the issue for any maintainer input. The scope needs clarification from maintainers regarding which queries (async only?) and what format the timing should be provided (e.g., callback, logging).