connection to database with password containing dollar signs and exclamation marks
up vote
1
down vote
favorite
I am trying to open a connection using psql
to a database.
The connection string looked like this
psql -A -t -c "sql query" postgresql://$1@$2/$3
Where I passed as first parameter
$1 = login:password
$2 = localhost:5432
$3 = dbname
It worked fined when login and password was pretty much standard like 123 and so on.
But when I try to connect using a password like 123412@15!12$
it fails with the incorrect password.
How to escape it property?
bash git-bash
add a comment |
up vote
1
down vote
favorite
I am trying to open a connection using psql
to a database.
The connection string looked like this
psql -A -t -c "sql query" postgresql://$1@$2/$3
Where I passed as first parameter
$1 = login:password
$2 = localhost:5432
$3 = dbname
It worked fined when login and password was pretty much standard like 123 and so on.
But when I try to connect using a password like 123412@15!12$
it fails with the incorrect password.
How to escape it property?
bash git-bash
add a comment |
up vote
1
down vote
favorite
up vote
1
down vote
favorite
I am trying to open a connection using psql
to a database.
The connection string looked like this
psql -A -t -c "sql query" postgresql://$1@$2/$3
Where I passed as first parameter
$1 = login:password
$2 = localhost:5432
$3 = dbname
It worked fined when login and password was pretty much standard like 123 and so on.
But when I try to connect using a password like 123412@15!12$
it fails with the incorrect password.
How to escape it property?
bash git-bash
I am trying to open a connection using psql
to a database.
The connection string looked like this
psql -A -t -c "sql query" postgresql://$1@$2/$3
Where I passed as first parameter
$1 = login:password
$2 = localhost:5432
$3 = dbname
It worked fined when login and password was pretty much standard like 123 and so on.
But when I try to connect using a password like 123412@15!12$
it fails with the incorrect password.
How to escape it property?
bash git-bash
bash git-bash
asked Nov 22 at 9:58
lapots
3,5411258125
3,5411258125
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
1
down vote
accepted
I would use safer variable placing:
psql -A -t -c "sql query" "postgresql://${1}@${2}/${3}"
In addition parameters $1, $2, $3 should be passed as:
script.sh 'login:password' 'localhost:5432' 'dbname'
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
1
down vote
accepted
I would use safer variable placing:
psql -A -t -c "sql query" "postgresql://${1}@${2}/${3}"
In addition parameters $1, $2, $3 should be passed as:
script.sh 'login:password' 'localhost:5432' 'dbname'
add a comment |
up vote
1
down vote
accepted
I would use safer variable placing:
psql -A -t -c "sql query" "postgresql://${1}@${2}/${3}"
In addition parameters $1, $2, $3 should be passed as:
script.sh 'login:password' 'localhost:5432' 'dbname'
add a comment |
up vote
1
down vote
accepted
up vote
1
down vote
accepted
I would use safer variable placing:
psql -A -t -c "sql query" "postgresql://${1}@${2}/${3}"
In addition parameters $1, $2, $3 should be passed as:
script.sh 'login:password' 'localhost:5432' 'dbname'
I would use safer variable placing:
psql -A -t -c "sql query" "postgresql://${1}@${2}/${3}"
In addition parameters $1, $2, $3 should be passed as:
script.sh 'login:password' 'localhost:5432' 'dbname'
answered Nov 22 at 10:14
Kubator
5078
5078
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53428293%2fconnection-to-database-with-password-containing-dollar-signs-and-exclamation-mar%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown