This repository was archived by the owner on Jun 7, 2023. It is now read-only.
Solves issue #69. #70
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
…ted characters in queries. I couldn't perform queries with accented characters (such as SELECT var FROM table WHERE var = 'Córdoba') so I changed the method from curlEscape to CurlPercentEncode.
# for free
to subscribe to this conversation on GitHub.
Already have an account?
#.
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.
As I said in the issue there were some problems with the use of accented characters in soqlQuery. I was able to solve it by changing the method curlEscape() to curlPercentEncode() and by adding the encoding "UTF-8" to the node xmlParse() inside xmlToList2().