Handling escape sequence in query params in rails app server with Postgres
0
query_string = params[:q]
model.where("name ILIKE ? ", "#{query_string}").limit(10)
In the controller I have the above lines
params[:q] is the user input.
Whenever the user input ends with , say police , Postgres throws this error:
ActionView::Template::Error (PG::InvalidEscapeSequence: ERROR: LIKE pattern must not end with escape character.
How can we gracefully handle such cases?
ruby-on-rails postgresql sql-like
asked Nov 13 '18 at 6:44
SuryaSurya
327111
add a comment |
0
query_string = params[:q]
model.where("name ILIKE ? ", "#{query_string}").limit(10)
In the controller I have the above lines
params[:q] is the user input.
Whenever the user input ends with , say police , Postgres throws this error:
ActionView::Template::Error (PG::InvalidEscapeSequence: ERROR: LIKE pattern must not end with escape character.
How can we gracefully handle such cases?
ruby-on-rails postgresql sql-like
asked Nov 13 '18 at 6:44
SuryaSurya
327111
add a comment |
0
0
0
query_string = params[:q]
model.where("name ILIKE ? ", "#{query_string}").limit(10)
In the controller I have the above lines
params[:q] is the user input.
Whenever the user input ends with , say police , Postgres throws this error:
ActionView::Template::Error (PG::InvalidEscapeSequence: ERROR: LIKE pattern must not end with escape character.
How can we gracefully handle such cases?
ruby-on-rails postgresql sql-like
asked Nov 13 '18 at 6:44
SuryaSurya
327111
query_string = params[:q]
model.where("name ILIKE ? ", "#{query_string}").limit(10)
In the controller I have the above lines
params[:q] is the user input.
Whenever the user input ends with , say police , Postgres throws this error:
ActionView::Template::Error (PG::InvalidEscapeSequence: ERROR: LIKE pattern must not end with escape character.
How can we gracefully handle such cases?
ruby-on-rails postgresql sql-like
ruby-on-rails postgresql sql-like
asked Nov 13 '18 at 6:44
SuryaSurya
327111
asked Nov 13 '18 at 6:44
SuryaSurya
327111
edited Nov 13 '18 at 7:04
Surya
asked Nov 13 '18 at 6:44
SuryaSurya
327111
asked Nov 13 '18 at 6:44
SuryaSurya
327111
asked Nov 13 '18 at 6:44
SuryaSurya
327111
327111
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
1
Use a different escape character, for example:
WHERE name ILIKE 'pattern' ESCAPE '/'
If you have no safe escape character, you can double it:
WHERE nane ILIKE replace('pattern', '', '\')
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
1
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
|
show 2 more comments
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
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%2f53275243%2fhandling-escape-sequence-in-query-params-in-rails-app-server-with-postgres%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
1
Use a different escape character, for example:
WHERE name ILIKE 'pattern' ESCAPE '/'
If you have no safe escape character, you can double it:
WHERE nane ILIKE replace('pattern', '', '\')
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
1
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
|
show 2 more comments
1
Use a different escape character, for example:
WHERE name ILIKE 'pattern' ESCAPE '/'
If you have no safe escape character, you can double it:
WHERE nane ILIKE replace('pattern', '', '\')
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
1
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
|
show 2 more comments
1
1
1
Use a different escape character, for example:
WHERE name ILIKE 'pattern' ESCAPE '/'
If you have no safe escape character, you can double it:
WHERE nane ILIKE replace('pattern', '', '\')
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
Use a different escape character, for example:
WHERE name ILIKE 'pattern' ESCAPE '/'
If you have no safe escape character, you can double it:
WHERE nane ILIKE replace('pattern', '', '\')
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
edited Nov 13 '18 at 7:06
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
answered Nov 13 '18 at 6:55
Laurenz AlbeLaurenz Albe
44.6k102746
44.6k102746
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
1
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
|
show 2 more comments
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
1
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
Nope then if the user enters 'Police /' I will be getting the same error right? params[:q] is a user input.
– Surya
Nov 13 '18 at 6:59
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
how can gracefully handle all such cases?
– Surya
Nov 13 '18 at 7:01
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
Double the escape character as indicated in the extended answer.
– Laurenz Albe
Nov 13 '18 at 7:07
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
if I use replace then in valid cases like 'police a ' it will get queried as 'police \a' isn't it? Isn't that not desirable?? But chances that I get input like 'police a ' is minimal so I might as well use this, but still wondering..
– Surya
Nov 13 '18 at 7:14
1
1
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
Well, if the backslash sometimes is an escape character and sometimes not, you need to have additional information. There is no way to guess which is meant.
– Laurenz Albe
Nov 13 '18 at 7:17
|
show 2 more comments
draft saved
draft discarded
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.
draft saved
draft discarded
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%2f53275243%2fhandling-escape-sequence-in-query-params-in-rails-app-server-with-postgres%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
