tursodatabase/turso

Support `VACUUM INTO` to create an encrypted db

Open

#5.852 geöffnet am 11. März 2026

Auf GitHub ansehen
 (2 Kommentare) (0 Reaktionen) (0 zugewiesene Personen)Rust (1.001 Forks)github user discovery
encryptiongood first issue

Repository-Metriken

Stars
 (19.103 Stars)
PR-Merge-Metriken
 (PR-Metriken ausstehend)

Beschreibung

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

Contributor Guide