tursodatabase / tursodatabase/libsql
Query timing?
Open
Nobody has claimed this yet.
enhancement
good first issue
help wanted
question
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
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
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
Start by locating the library's asynchronous query entry point and tracing how query completion is reported. Define what timing information the library should expose and where callers would receive it; the work is done when asynchronous queries provide a documented, usable duration signal.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- database
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100