Fixes: generating a migration using the --sequence flag #39
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
It seemed that GetExtension had postgresql as a driver name and not postgres, which resulted having the sequence number always set to 0000001 for driver postgres. Also I needed to add the driver to the filepath upon finding the sequelNumber, else it failed to generate.
koox00
changed the title
koox00
changed the title
koox00
changed the title
yep, I'm on it |
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.
It seemed that
GetExtensionhadpostgresqlas a driver name and notpostgres, which resulted having the sequence number always set to0000001for driverpostgres.Also I needed to add the driver to the filepath upon finding the
sequelNumber, else it failed to generate, for both postgres, and mysql drivers.