-
Notifications
You must be signed in to change notification settings - Fork 32
New issue
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
Tables with name
typed primary key not supported
#97
Labels
Comments
2 tasks
Hi... Is there anything I can do to help this issue move through triage and get my patch reviewed? It would be a big help for logistics on my end if this were resolved upstream so I don't have to maintain my own fork downstream. |
nathanielhourt
added a commit
to dapp-protocols/leap-cdt
that referenced
this issue
Mar 20, 2023
Create a unit test for a table with a name primary key. The new test fails to build before the commits in PReq AntelopeIO#98, but passes when those commits are included.
ScottBailey
added a commit
that referenced
this issue
Mar 20, 2023
Resolve #97: Allow `name` typed primary keys
dimas1185
pushed a commit
that referenced
this issue
Jun 8, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I have contracts which use
name
as the type of the primary key in several of their tables. This exact use case is historically the cause for thename
type to have been envisioned and created in the first place. Even the EOSIO core contracts made extensive use of this pattern, albeit, by bending over backward to protect the CDT templates from the true type of the key...Well that's just a bunch of silliness! Updating the templates to handle
name
typed primary keys is trivial, so why not just solve the problem once and have it go away, rather than adding complexity to every other contract?The text was updated successfully, but these errors were encountered: