We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
https://www.hackdapp.com/archives/eosdev_datastorage_historyaction.html
在开发EOS DApp智能合约时，我们都知道可以使用multi\\_index\_来对合约数据的存储与查询，但合约的存储是需要消耗一定的资源的，而且随着用户的增长往往会导业务数据会越来越大，从而导致合约需要更多的资源来支撑其数据增长。那么是否有一种更好的方式来降低某些场景的资源消耗呢？那么，今天将为你分享一种数据存储方案： 借用EOS链提供的history_api_action\_插件、内部合约Action调用来完成对业务数据的存储与查询。HackDApp愿与你分享！
multi\\_index\_
history_api_action\_
内部合约Action调用
The text was updated successfully, but these errors were encountered:
No branches or pull requests
https://www.hackdapp.com/archives/eosdev_datastorage_historyaction.html
在开发EOS DApp智能合约时，我们都知道可以使用
multi\\_index\_来对合约数据的存储与查询，但合约的存储是需要消耗一定的资源的，而且随着用户的增长往往会导业务数据会越来越大，从而导致合约需要更多的资源来支撑其数据增长。那么是否有一种更好的方式来降低某些场景的资源消耗呢？那么，今天将为你分享一种数据存储方案： 借用EOS链提供的history_api_action\_插件、内部合约Action调用来完成对业务数据的存储与查询。HackDApp愿与你分享！The text was updated successfully, but these errors were encountered: