Update created_contract_code_indexed_at on transaction import conflict #2375
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.
Solves a problem describe in a #2105 comment.
Motivation
The problem is that a transaction's
created_contract_code_indexed_at
gets ignored during a conflicting update, so it is not updated.In particular it is not reset to NULL and this has been source of errors.
Changelog
Bug Fixes
Add
created_contract_code_indexed_at
as a field to check and update during an import with conflict.Checklist for your PR
CHANGELOG.md
with this PR