Add a semantically meaningful way to open a PostgreSQL console. #49
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
Kloadut
added a commit
that referenced
this pull request
Aug 18, 2014
Add a semantically meaningful way to open a PostgreSQL console.
|
Thanks ! |
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 PR adds the ability to open a
psqlconsole to the specified database container with the commandI was looking for a way to do this and for a while I would just manually connect with
psql -h 172.17.42.1 -p 49153 -U root db. Then, I saw that thepostgresql:restorecommand does exactly that when you don't provide the dump file with< dump_file.sql.Since this didn't feel very correct in a semantic way, I added the feature to achieve this with the
consolecommand mentioned above.The README has been updated as well to show the newly added command.