Add disable option to avoid creating migration table on getting db map#199
Merged
rubenv merged 1 commit intorubenv:masterfrom Oct 23, 2021
Merged
Add disable option to avoid creating migration table on getting db map#199rubenv merged 1 commit intorubenv:masterfrom
rubenv merged 1 commit intorubenv:masterfrom
Conversation
|
Hi @rubenv, any news regarding this PR ? |
Owner
|
Not a big fan of tons and tons of options, but your use-case sounds valid (for a certain kind of disfunctional organization 😅). I'll allow it! Thanks for submitting this! |
Owner
|
Oh and a big sorry for the delay, things have been hectic around here. |
|
@rubenv |
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
3 participants
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.
We want to use your package as a data migration tool, the problem is that our postgresql user has only INSERT, UPDATE and DELETE right. Another team, is responsible database schema and won't handle the data queries.
The only issue with the package is the creation of the migration table before any migration.
So I added a switch to avoid the migration table querie before executing the migration.