You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The first 4 tables can be derived from the data available in the on-chain database, so we don't need to serialize them into the snapshot.
However, we need to write code and workers who will initialise these tables based on the on-chain data.
The data from the last 2 tables is not recoverable, so we need to serialise them into the snapshot file.
These tables should be migrate in the same way what is used for on-chain migration.
pubenumColumn{/// The column of the table that stores `true` if `owner` owns `Coin` with `coin_id`OwnedCoins = 1,/// The column of the table of all `owner`'s transactionsTransactionsByOwnerBlockIdx = 3,/// The column of the table that stores `true` if `owner` owns `Message` with `message_id`OwnedMessageIds = 4,/// See [`blocks::FuelBlockIdsToHeights`]FuelBlockIdsToHeights = 6,/// Transaction id to current statusTransactionStatus = 2,/// The column of the table that stores statistic about the blockchain.Statistic = 5,}
The text was updated successfully, but these errors were encountered:
The first 4 tables can be derived from the data available in the on-chain database, so we don't need to serialize them into the snapshot.
However, we need to write code and workers who will initialise these tables based on the on-chain data.
The data from the last 2 tables is not recoverable, so we need to serialise them into the snapshot file.
These tables should be migrate in the same way what is used for on-chain migration.
The text was updated successfully, but these errors were encountered: