Fix inserted_at for seniority to Utc::now() #890
Merged
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.
I do no think we need to fix current DB as this does not seem to impact much things.
fetch_latest
does not care aboutinserted_at
.fetch_seniority
is the only place whereinserted_at
is used to order seniority records. If we update the old fields we might alter the result or previous rewards run better leave the DB alone there IMO.The proto does not care about
inserted_at
anywhere I could find