-
Notifications
You must be signed in to change notification settings - Fork 25
Rewrite XML Parsing for Query Recordsets #31
Conversation
Change the internal behavior of rforcecom.query to handle nested queries, obey global options setting for stringsAsFactors, and increase speed.
Fix code to loop through each list column because there might be a list for each foreign object that's being referenced
Change the internal behavior of rforcecom.query to handle nested queries, obey global options setting for stringsAsFactors, and increase speed.
Fix code to loop through each list column because there might be a list for each foreign object that's being referenced
We're seeing the same issue -- would be great if this pull request could be integrated asap. |
Rewrite XML Parsing for Query Recordsets
@ReportMort
Is there an easy fix for this? |
@nelsonauner The patch merged but it is not on the CRAN now. Please try the code from github or please wait just a few days, I will upload the current head version to CRAN. |
@hiratake55 |
@nelsonauner Could you add some more detail and we'll go from there? Thanks. |
@ReportMort @hiratake55 |
This request changes the package to use one function called
query_parser
when parsing the results returned by Salesforce from SOQL queries. This was done to better handle foreign object and child-parent nested relationships that SOQL queries can return.I believe this methodology or another methodology should be deployed soon in order to quickly resolve the backlog of issues described in #23
Link to
query_parser
code:https://github.com/ReportMort/RForcecom/blob/query-refactor/R/rforcecom.utils.R