autocreate schema if it does not exist during migration/update #53
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
| Can one of the admins verify this patch? To accept patch and trigger a build add comment ".ok\W+to\W+test." |
aol-nnov force-pushed the master branch 2 times, most recently from 2bd3cb4 to 58b3bc1 Compare raymondfeng added a commit that referenced this pull request Jan 23, 2015
autocreate schema if it does not exist during migration/update
raymondfeng pushed a commit that referenced this pull request Jan 23, 2015
1.4.0 * Remove the usage of `CREATE SCHEMA IF NOT EXISTS' for compatibility (Raymond Feng) * one-line fix for #51 (Andrey Loukhnov) * basic tests for PR #53 (Andrey Loukhnov) * basic tests for PR #54 (Andrey Loukhnov) * provide database column default values via Loopback model description (Andrey Loukhnov) * autocreate schema if it does not exist during migration/update (Andrey Loukhnov) * Use connection pooling from the driver (Raymond Feng)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
4 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.
Hi!
My models span across several schemas in Postgresql and I've found it handy if schemas are created automatically too during migration process.