tursodatabase/turso

Support `VACUUM INTO` to create an encrypted db

Open

#5 852 ouverte le 11 mars 2026

Voir sur GitHub
 (2 commentaires) (0 réactions) (0 assignés)Rust (1 001 forks)github user discovery
encryptiongood first issue

Métriques du dépôt

Stars
 (19 103 stars)
Métriques de merge PR
 (Métriques PR en attente)

Description

The source db can be either encrypted or non encrypted. If the destination URI mentions encryption params, then it should produce an encrypted db. The tests also should make sure that db hash matches post vacuum.

If the source is already encrypted, then we should also that we are able to vacuum into another encrypted db but with different cipher settings.

The URI params should be like existing one: ?cipher=aegis256&hexkey=b1bbfda4f589dc9daaf004fe21111e00dc00c98237102f5c7002a5669fc76327

Guide contributeur