Faster way to access prefix IDs for associated models #84
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.
We started to bump up against performance issues when rendering lots of prefix IDs for subordinate objects in API responses. For example:
This causes an N+1 to fetch the account just to render it's prefix ID.
This also causes issues when we go to create a project with a prefix ID. Consider this:
This fails unless we override the
account_id
setter method on Project so that it first finds the Account and then uses the found account's underlying ID like: