Initialize migration history on archive DB creation #18008
Conversation
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
glyh
force-pushed
the
lyh/create-schema-archive-to-match-upgrade-script
branch
from
c641353 to
e6ecfdd
Compare
Member
Author
|
!ci-build-me |
dkijania
reviewed
Nov 3, 2025
| CREATE INDEX idx_blocks_zkapp_commands_zkapp_command_id ON blocks_zkapp_commands(zkapp_command_id); | ||
| CREATE INDEX idx_blocks_zkapp_commands_sequence_no ON blocks_zkapp_commands(sequence_no); | ||
|
|
||
| CREATE TYPE migration_status AS ENUM ('starting', 'applied', 'failed'); |
Member
There was a problem hiding this comment.
Hm, that change looks useful also for compatible/master. In develop we should only bump currenet_protocol_version
Member
Author
There was a problem hiding this comment.
We will have more HFs in the future, so having this in db in the 1st place should be useful, I think
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is so the behavior on a fresh develop DB would match that of one upgrading from compatible with upgrade to mesa script.