Make legacy migration atomic
This commit is contained in:
parent
ff84d85eb3
commit
c7e5f7a80d
6 changed files with 328 additions and 83 deletions
|
|
@ -13,6 +13,8 @@ Legacy `Consumer` rows map into:
|
|||
|
||||
Multiple legacy consumers can map into one circuit when they share normalized circuit identity.
|
||||
|
||||
For one circuit list, all new circuits, device rows, trace mappings and the migration report are committed in one SQLite transaction. A failed run therefore leaves none of those prepared migration writes behind.
|
||||
|
||||
## Grouping Strategy (`circuitNumber`)
|
||||
|
||||
Migration groups legacy rows by normalized `circuitNumber`:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue