tursodatabase/turso

Feature: per-connection memory allocator configuration

Open

#523 opened on Dec 20, 2024

View on GitHub
 (5 comments) (2 reactions) (0 assignees)Rust (1,001 forks)github user discovery
enhancementhelp wantedimprovements

Repository metrics

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

Description

I have a use case where I want to specify a custom allocator per connection. (The general form of the use case is to specify an arena allocator for an object that opens its own connection. This occurs in a process that is long lived [an application in my case] and that may spawn multiple concurrent instances/connections.)

In SQLite you can configure a custom allocator at the process level, but not per connection.

Contributor guide

Research direction
Study the SQLite per process allocator interface and design a per connection allocator trait. Identify where connections are created and how to pass an allocator. Consider using Box<dyn Allocator> or generic parameter.
Tech stack
rust
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.
3-5 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
RustMemory Allocation
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40