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.
Consolidates our rather long list of migrations from ~32 -> 5. Although this PR is intended to be deployed on a fresh database, operators can redeploy with this version and then manually update their existing deployments by going into the db and running
update schema_migrations set version = 5
. This will allow future migrations (which will now start at06_...
to properly apply to the database.Functionally, this PR is mostly a no-op, with two exceptions:
chain.blocks.metadata
was removed because it was not being used. It was likely an artifact from years ago.history.staking_events
table; it has been granted properly as of this PR.Validation:
Comparison of the dumped database schema (using
pg_dump -s
) for main branch / feature branch: