This repository has been archived by the owner on Aug 2, 2022. It is now read-only.
Allow multi_index primary key to be a name #1265
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Change Description
Using a
name
as a primary key in a table is such a common use case that even the core contracts do it extensively. Adding first class support for this use case to themulti_index
template is trivial, and allows contract code to be more expressive.API Changes
The
multi_index
API now supports usage of aname
as a table primary key, and implicitly casts it down to an int for indexing.Documentation Additions