If you actually ran your node with the botched "last_invoice_created_index" typo migration (fortunately, not release, just master) you can get a db with both the real "last_invoices_created_index" and the bad "last_invoice_created_index" entries. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
|---|---|---|
| .. | ||
| recklessrepo | ||
| commando_blacklist.sqlite3.xz | ||
| commando_listrunes.sqlite3.xz | ||
| dangling-peer.sqlite3.xz | ||
| dupe_lease_fee.sqlite3.xz | ||
| invoices_botched_waitindex_migrate.sqlite3.xz | ||
| invoices_pre_waitindex.sqlite3.xz | ||
| last_tx_closed.sqlite3.xz | ||
| last_tx_upgrade.sqlite3.xz | ||
| no-local-basepoints.sqlite3.xz | ||
| oldstyle-scids.sqlite3.xz | ||
| p2sh_wallet_hsm_secret | ||
| pubkey_regen_commitment_point.sqlite3.xz | ||
| pubkey_regen.sqlite.xz | ||
| upgrade_inflight.sqlite3.xz | ||
| v0.12.1-forward.sqlite3.xz | ||