Repository navigation
The Google Drive migration is numbered 9006 in the fork until upstream takes it - #29
Merged
Merged
Conversation
…m takes it Signed-off-by: Bogdan Szabo <bogdan@re-cinq.com>
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
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.
#28 brought the Google Drive source in with upstream's migration number 0120, but RE-CINQ.md numbers fork-only migrations from 9000 so a production database never applies a number upstream might still change. This renames it to 9006 with the same idempotent SQL (now also in deeplethe#1386). Checked on a fresh database: it migrates twice cleanly, and adding the upstream 0120 copy beside it later is harmless, like 9001 and 0115. Needed before v0.1.0-re.18.