change to true DB migration (away from synchronize that breaks in production) #68
Conversation
This file contains 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
|
This is very interesting. My gut tells me that this migration logic should be part of the |
|
@simonas-notcat perhaps you can share some wisdom here :) |
|
taking initial steps to promote migrations instead of |
|
Issue moved to uport-project/veramo #676 via ZenHub |
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.
See 'synchronize' explanation here: https://github.com/typeorm/typeorm/blob/master/docs/connection-options.md
Everything else appears to work in real apps (as long as decentralized-identity/veramo#480 is included for mobile), so adding this will save people heartburn as they create their apps.