Add support for reflective lookups #1
Merged
Conversation
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
To achieve this, I kept a track of unresolved reflective lookups (where the record and relatedTo SObjectTypes are the same, the the relatedTo doesn't yet have an Id). If any of the records being inserted have a reflective reference to anoth er record being inserted in the same commit, then I perform an update immediatel y after the insert to "Backfill" the lookups with the Ids of the newly inserted records. The tradeoff is clear and calculable. SObjects with unresolved relationships incur 2xDML rows. I like this better than trying to order the inserting of SObjects and incur and undetermined number of DML statements.
loganm
added a commit
that referenced
this pull request
Jul 2, 2015
Add support for reflective lookups
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
To achieve this, I kept a track of unresolved reflective lookups (where
the record and relatedTo SObjectTypes are the same, the the relatedTo
doesn't yet have an Id). If any of the records being inserted have a
reflective reference to anoth
er record being inserted in the same commit, then I perform an update
immediatel
y after the insert to "Backfill" the lookups with the Ids of the newly
inserted
records.
The tradeoff is clear and calculable. SObjects with unresolved
relationships incur 2xDML rows. I like this better than trying to order
the inserting of SObjects and incur and undetermined number of DML
statements.