[feat][WIP] : add pgsql migration support #57
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
…a.table notation)
|
When might we see this functionality or something like it in the main branch??? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR includes breaking changes (update the package name to a more generic format
<vendor>/<package>rather thanpackagenamespace)This is a rough but working migration of the existing MySQL's migration generator to PgSQL
Currently, migration works and supports multi schema migration generation
known issue serial, character varying, timestamps definition generated incorrectly
currently, there are many that need work on this like
Tests
Update README for breaking changes and new configuration
Table View support