document how to use super_user #44
Open
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
karenc
requested changes
Sep 5, 2017
| ---------- | ||
|
|
||
| Note the template for migrations mentions a second cursor context manager available for running steps as a | ||
| database superuser, be default `postgres`. This is useful if you want to use a less priviliged user for most |
| By seperating into two migrations, the function created by the super_user connection is | ||
| available to the less priviliged user to create the trigger on the table owned by them. | ||
|
|
||
| If you wish to combine these into a single migration, it is necessary to call `commit` |
There was a problem hiding this comment.
It was not necessary for me. See #43 (comment)
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.
This explains the two-cursor-two-connection problem, I hope.