Adding new options in order to avoid DROP statements generation#306
Open
romaint2b wants to merge 3 commits intofordfrog:developfrom
Open
Adding new options in order to avoid DROP statements generation#306romaint2b wants to merge 3 commits intofordfrog:developfrom
romaint2b wants to merge 3 commits intofordfrog:developfrom
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
In many case you should want to avoid drop statements when generating delta's. reason is that the new schema is not the full schema of your db but only a module schema.
I add many options to disable drop statements (one for each item type).
I also add a --disableDrop options to avoid all drop statements.
Tested on several dump that i used.