Data design and migration

ARISEN based blockchains allow developers to easily update their smart contract code. However, a few things need to be considered when it comes to data update and/or migration. The main structure for storing data in ARISEN based blockchains is the multi index table. Once a multi index table has been created with a first version of a smart contract, it has some limitations when it comes to changing its structure. Below you will find a few possible approaches which you can consider when you design your smart contract data and its migration.

How to modify the structure of a multi index table

Modifying a multi-index table structure that has already been deployed to an ARISEN-based blockchain may be done by selecting one of the different strategies outlined below, depending on your requirements:

1. If you don't mind losing the existing data

If you don't mind losing the data from the initial table you can follow these two steps:

1.Erase all records from first table
2.Deploy a new contract with modified table structure

2. If you want to keep the existing data

If you want to keep the existing data there are two ways to do it:

2.1. Using binary extentions

To learn how to modify the structure using ABI variants read this tutorial.

2.3. Migrate the existing data to a second table

2.3.1. Migration without downtime, but slower

Create the new version of your multi index table alongside the old one;

  • Transfer data from the old table to the new one. You may do so as part of your normal access pattern, first checking the new table to see if the entry you seek is present and if not, check the original table, and if it's present, migrate it while adding the data for the new field, then remove it from the original table to save RAM costs.
  • You must retain both versions of your multi index table until you have completed this migration, at which point you may update your contract to remove the original version of your multi index table.

2.3.2. Migration with downtime, but faster

If you prefer less code complexity and can accept downtime for your application:

1.Deploy a version of your contract solely for migration purposes, and run migration transactions on every row of your table until complete. If the first table is big, e.g. has a large number of rows, the transaction time limit could be reached while running the migration transactions. To mitigate this implement the migrate function to move a limited number of rows each time it runs;
2.Deploy a new contract using only the new version of the table, at which point, your migration and downtime is complete.


Both of the above migration methods require some pre-planning (like the ability to put your contract into a maintenance mode for user feedback)