mirror of
https://github.com/lightninglabs/lightning-terminal.git
synced 2026-08-13 12:33:36 +02:00
68718a5c59
As the SQL migrations prior to the kvdb to SQL migration was never live in production, we can safely assume that the sql database is empty prior to the kvdb to sql migration. Therefore, it is not necessary that we create an backup of the sqlite database for every migration that exists for the time being. As the sqldb/v2 intentionally doesn't delete the backup file when a migration has been completed (as this is intentional behaviour for tapd) and the package so far doesn't support any option to delete the backup file, this otherwise creates multiple unnecessary backup files for users. Once the sqldb/v2 does support making deletion of the backup file possible, or once we add another sql migration, we need to toggle the backup behaviour for the sql migrations on again. |
||
|---|---|---|
| .. | ||
| migsets | ||
| sqlc | ||
| sqlcmig6 | ||
| tombstone | ||
| interfaces.go | ||
| log.go | ||
| migrations.go | ||
| postgres.go | ||
| postgres_fixture.go | ||
| schemas.go | ||
| sqlerrors.go | ||
| sqlite.go | ||