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.
--
You received this
Hey,
I'm picking up this thread again--sorry for reviving a sleeper.
We're looking into doing this again for some much needed performance
improvements.
After looking at the feedback it looks like we would be able to deal with
the created flag using the query status.
https://www.postgresql.org
This list is for discussing the development of Django itself, please ask
usage questions on django-users.
On Wednesday, September 7, 2016 at 12:44:57 PM UTC-4, Asad ur Rehman wrote:
>
> Here is my view.py
>
> import os.path
> import commands
>
> def call_report(request):
>
> a = commands.g
Here is my view.py
import os.path
import commands
def call_report(request):
a = commands.getstatusoutput('/usr/local/freeswitch/bin/fs_cli -x "show
calls"')
return HttpResponse(a)
When i run this command it gives output which you can see...
0uuid,direction,created,created_epoch,nam
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.
--
You received
