[WIP] Fix wrong inputs due to mutable contract outputs#588
Open
[WIP] Fix wrong inputs due to mutable contract outputs#588
Conversation
tdroxler
force-pushed
the
fix-input-update-query
branch
from
968bc33 to
be27313
Compare
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
1 participant
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.
Still need to redo a final test with the prod DB. I already migrated some data during the development and my DB is not anymore in prod state.
The ultimate goal is still to use the rich-blocks endpoints, but we anyway need to fix the current data with a migration and make sure we don't insert new incorrect data.