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.
Fully functional concept of possible fix for #111. It saves the queryset from export page and use it when export performed later in a job.
I don't know better way to save/restore queryset between initial request and celery job, too many points in django where queryset can be dynamically modified.
In case of python or django upgrade, if serialized with pickle query breaks it can be re-created from saved
queryString
.Select/unselect fields to be exported are not supported, all fields will be exported in current implementation but this feature can be added.
django-import-export
anddjango-import-export-celery
select resources differently, some work needs to be done for unification and better integration of feature.Trigger of
run_export_job.delay
needs to be updated and separated from creation and scheduling task execution to be able to create job without scheduling it automatically, to set non default values forSite of origin:
andSend me an email when this export job is complete
and than schedule job after that.See also #130