I was thinking on good practices when creating the persistence using the multi-index API, more specifically regarding future updates to the table model (ie. adding new members to the struct). All the options presented on https://developers.eos.io/manuals/eosio.cdt/latest/best-practices/data-design-and-migration didn't seem like a nice solution for me.

I saw that some contracts use JSON as a flexible persistence on their tables, but I also saw that they need to include a parser for it to work, seems like a big addition to the CPU processing time, not to mention the huge code base a JSON parser has.

Is there any known reason not to use std:map inside a table? If not why would people prefer to use JSON?


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.