tursodatabase/turso

Support `VACUUM INTO` to create an encrypted db

Open

#5.852 aberto em 11 de mar. de 2026

Ver no GitHub
 (2 comments) (0 reactions) (0 assignees)Rust (1.001 forks)github user discovery
encryptiongood first issue

Métricas do repositório

Stars
 (19.103 stars)
Métricas de merge de PR
 (Métricas PR pendentes)

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

Guia do colaborador