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
{{ message }}
This repository has been archived by the owner on Nov 2, 2020. It is now read-only.
I'm concerned about the need for the fields to be ordered just like they exists in the blockchain.db and if you join with system table like often used in the examples like "transactions" if Lisk team decide to add a new field in "transactions" every dapps which updates the SDK breaks.
The text was updated successfully, but these errors were encountered:
I'm concerned about the need for the fields to be ordered just like they exists in the blockchain.db and if you join with system table like often used in the examples like "transactions" if Lisk team decide to add a new field in "transactions" every dapps which updates the SDK breaks.
The text was updated successfully, but these errors were encountered: