tursodatabase/libsql

Optimize `SELECT COUNT(*)` by keeping a counter

Open

#328 opened on Apr 27, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (490 forks)batch import
enhancementhelp wanted

Repository metrics

Stars
 (16,744 stars)
PR merge metrics
 (Avg merge 23h 19m) (1 merged PR in 30d)

Description

Some databases apparently optimize SELECT COUNT(*) by keeping a per-table counter. Let's look into if that's doable.

Contributor guide

Research direction
Investigate libSQL internals for a per table row count counter. Look into SQLite's metadata and B tree structure. Consider implementing a counter in the table schema and updating it on INSERT/DELETE. Ensure consistency with transactions.
Tech stack
csqlite
Domain
database
Issue type
Feature
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-2 days
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
CSQL
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40