This repository was archived by the owner on Jan 20, 2024. It is now read-only.
Avoid using SOQL subqueries for query locator error#8
Open
ninoish wants to merge 11 commits into
Open
Conversation
…ld obj fields" This reverts commit ca1c47b.
This file contains hidden or 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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
1 participant
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.
Record Clone has been using SOQL subqueries to fetch child relationship records so to simplify and minimize the SOQL executions. However when child records are too many , it causes Aggregate Query Error and Invalid Query Locator Error when trying to access the child data bypassing its parent data. In additions to the number of records, it has been reported that there are some odd cases causing the same error with small number of child records, which is not documented in any help page.
Taking the situations into account, using SOQL subqueries for obtaining child records is replaced with simple SOQLs executed for each sobject. It increases the number of SOQL executions, but it follows the rules of governor limits that makes it observable.