-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Runing import without passing it through ID fetcher #636
Comments
Ok, agree, how about to add |
Or an option is also fine by me |
I like the method idea. I'll poke at it today and send a PR with a POC. |
Actually maybe a bit of both, to keep the same structure with the |
Closed in #753 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Given code like this:
The import will end performing one extra query to load
some_association
per instance ofMyModel
in the scope, instead of using the included data.This happens because both
import_scope
here andimport_objects
here re-run a select, regardless of what I pass in. For a more complex index, this can translate to a bunch of queries per instance that I want to import.The only way I can do this right now is by skipping any sort of external API, and just doing an import directly:
I would really prefer not to have to resort to something like this, so would it be possible to introduce either a key that skips the re-import, or some way to customize the default_scope used when re-loading the data to be imported?
The text was updated successfully, but these errors were encountered: