Expose setting reserver_bytes via libsql and also in bindings

Open
#2,164 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 11 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
c, sqlite
Domain
databases

Research direction

Start by locating the existing reserved-bytes setting in libsql and the binding or SDK entry points that expose database configuration. Trace how an existing database is opened and uploaded, then verify that users can set reserver_bytes through libsql and the bindings for the environments described.

Written by the indexing model from the issue text.

Description

encryption at rest

For Turso Cloud encryption to work, the existing dbs need to have specific reserved bytes set and only then upload can work.

We need to expose this setting via libsql and also in SDKs, so that users can easily upload existing dbs in any environment (like opsqlite on devices)

Dominant language
C
Stars
17.3k
Forks
562
Avg merge
10d 15h
Merged PRs (30d)
1

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from tursodatabase/libsql

All issues in tursodatabase/libsql

Similar issues

More C issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.