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
Right now we are using emplace, modify, and erase for the manipulation of rows in multi_index tables.
Since we are expecting multi_index to be used in a similar way to a database within smart contracts, it would be easier for developers to get started with Antelope if our nomenclature mimicked that of other databases they are familiar with (like MySQL, Postgre, MongoDB, SQLite, etc) and had alias support for:
Insert
Update
Delete
I think that the understandability and memorability of our language would improve for anyone who doesn't come from C++, Rust, or D.
Right now we are using
emplace
,modify
, anderase
for the manipulation of rows inmulti_index
tables.Since we are expecting
multi_index
to be used in a similar way to a database within smart contracts, it would be easier for developers to get started with Antelope if our nomenclature mimicked that of other databases they are familiar with (like MySQL, Postgre, MongoDB, SQLite, etc) and had alias support for:I think that the understandability and memorability of our language would improve for anyone who doesn't come from C++, Rust, or D.
The text was updated successfully, but these errors were encountered: