202e65e408
According to the docs at https://www.sqlite.org/lang_altertable.html doing the steps 1. Rename old table 2. Create new table 3. Copy data 4. Drop old table is incorrect and should be 1. Create new table 2. Copy data 3. Drop old table 4. Rename new into old Additionally, each step was being run in a different transaction, which could cause permanent failures if a problem happened during the migration. Avoid both of those problems by changing up some previous migrations that ran in this way. Since they are semantically identical, it's fine to change up these old migrations. It will help make newer nodes coming up for the first time more robust. Change-Id: I43fb004fa1b6cb2fe2554f9920925420da28fb4a |
||
---|---|---|
.. | ||
storagenodedbtest | ||
testdata | ||
bandwidthdb.go | ||
database.go | ||
db_container.go | ||
deprecatedinfo.go | ||
heldamount.go | ||
migrations_test.go | ||
notifications.go | ||
orders.go | ||
pieceexpiration.go | ||
pieceinfo.go | ||
piecespaceused.go | ||
pricing.go | ||
reputation.go | ||
satellites.go | ||
schema.go | ||
schemagen.go | ||
storageusage.go | ||
usedserials.go |