mirror of
https://github.com/lightninglabs/lightning-terminal.git
synced 2026-08-13 12:33:36 +02:00
e955dc825b
Migrate KV firewall actions by traversing the global actions-index instead of iterating per-session buckets, so SQL action IDs follow the same global creation order as the legacy KV store. Also stabilize SQL action listing by ordering on created_at and id, using id as a deterministic tie-breaker when multiple actions share the same timestamp. This is needed because KV actions have a real global sequence in actions-index, while the old migration assigned SQL IDs based on bucket traversal order. That could reorder legacy actions during migration. Separately, ordering by created_at alone was not stable for equal timestamps, so action queries could return different orders for the same data. NOTE: This commit explicitly edits the previous migration instead of adding a new one. This is ok as SQL dbs are not yet supported in production, so there are no live deployments to worry about. |
||
|---|---|---|
| .. | ||
| migsets | ||
| sqlc | ||
| sqlcmig6 | ||
| tombstone | ||
| interfaces.go | ||
| log.go | ||
| migrations.go | ||
| postgres.go | ||
| postgres_fixture.go | ||
| schemas.go | ||
| sqlerrors.go | ||
| sqlite.go | ||