Open
Conversation
|
Context The more I think about structure of the data in socialdb, the more I lean towards serializing as much as possible into JSON object and then store it as a string instead of sub-objects. This way it's still easy to read (so long as you always read the whole object) and easier to replace, since you don't need to cleanup recursively. If the fields of the bounty don't have to be used independently by other contracts, then it should be a large serialized object instead. Also think about updates to the bounties, and whether they are more like posts (replaced), or more like profiles (persistent in latest state). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
starting point for discussion, based on examples