pickling query bug (ticket #27159)
77 views
Skip to first unread message
Dávid Főző
Sep 7, 2016, 7:50:08 AM9/7/16
to Django developers (Contributions to Django itself)
Hello guys,
It seems that this bug is too big for me to handle. What seems to happen is that when you pickle a query. RelatedIn pickle the whole sub QuerySet, which it is not supposed to do. I guess the solution requires to change it's behavior, which I have no clue how to do.
It seems that this bug is too big for me to handle. What seems to happen is that when you pickle a query. RelatedIn pickle the whole sub QuerySet, which it is not supposed to do. I guess the solution requires to change it's behavior, which I have no clue how to do.
Dávid Főző
Sep 7, 2016, 4:39:58 PM9/7/16
to Django developers (Contributions to Django itself)
I think I can do this. I will define a variable in QuerySet showing that it's a subquery, so it won't populate its cache when pickled.
Now, I just need to find the shortest path between RelatedIn and instantiating its QuerySet, the variable will cascade through this path.
Now, I just need to find the shortest path between RelatedIn and instantiating its QuerySet, the variable will cascade through this path.
Reply all
Reply to author
Forward
0 new messages