Skip to content
This repository has been archived by the owner on Jun 7, 2023. It is now read-only.

Queries with ampersand must now be escaped beforehand #43

Open
StevenMMortimer opened this issue Jul 12, 2016 · 1 comment
Open

Queries with ampersand must now be escaped beforehand #43

StevenMMortimer opened this issue Jul 12, 2016 · 1 comment
Assignees

Comments

@StevenMMortimer
Copy link
Contributor

In commit 5381c78 curlEscape was removed from rforcecom.query function. Now queries with fail if they contain an ampersand (&). There's something different about how URLencode works compared to curlEscape. Not sure what exactly is different in those two functions, but noting the issue. The query below used to work before commit 5381c78. Now you need to use curlEscape before passing to the function.

query <- "SELECT Id, Name from Account where Name='Sanford & Son'"
rforcecom.query(session=session, soqlQuery=query)

Error in rforcecom.query(session = session, soqlQuery = query) : 
  MALFORMED_QUERY: A query string has to be specified
@hiratake55 hiratake55 self-assigned this Jul 13, 2016
@hiratake55
Copy link
Owner

@ReportMort Thanks for your report. Created a patch as 834ed51.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants