nginx+uwsgi, cache somewhere but I don't know where

[술욱]

Hello

I'm running (in production) and app that uses raw queries, something like:

query = """

select table1.field1, table2.field3 

from table1 left join table2 

   on test1.field1 = test2.field1 

   and test1.field2 = test2.field2 

where table1.field1 = %(param1)s

"""

cursor = connections['database'].cursor()

cursor.execute(query, {'param1': param1-value})

data = cursor.fetchall()

My problem is, somewhere, Django, uwsgi, or nginx, is caching this query. 

How do I find who's caching?

Thanks,

Norberto

[M Hashmi]

Reload Nginx and see if still its loading cached query.

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.
To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADut3oCG%2Bc%3D8CFm5Mf0YiBtK3RMa-0KrZZG6wb0_ihDwkDmqkQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

[술욱]

I forgot to say I reloaded (and restarted) nginx and uwsgi, but the query is still cached

Thanks anyway!

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CANoUts63A-mGo-KOYJHBFJtOut9gasWX3A8dso3%3Dv0myFwgAgg%40mail.gmail.com.

[Avraham Serour]

How do you know the query is cached?

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADut3oBoqHS7JCV8vs2o2Z%2BHDsr5LQeTDnGm34bdPTJbcOkhDg%40mail.gmail.com.

[Bill Freeman]

Cached in browser, maybe?

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6tKMSQ077%2BuRm-Kp1iGNS%2BUbGLcZihpE%3Dphwc69KNhJEVg%40mail.gmail.com.

[술욱]

Because this particular query runs in about 30 seconds and its result ends up in an excel file, which is generated with openpyxl from a template.

If I change the template, the file returned by django is this new file, but its contents, the query result, doesn't (and it executes immediately).

[Avraham Serour]

did you checked if it cached in the browser? does nginx gets the request? if so what does it answers?

On Tue, Aug 16, 2016 at 7:07 PM, 술욱 <nbe...@gmail.com> wrote:

Because this particular query runs in about 30 seconds and its result ends up in an excel file, which is generated with openpyxl from a template.

If I change the template, the file returned by django is this new file, but its contents, the query result, doesn't (and it executes immediately).

--
You received this message because you are subscribed to the Google Groups "Django users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to django-users+unsubscribe@googlegroups.com.
To post to this group, send email to django...@googlegroups.com.
Visit this group at https://groups.google.com/group/django-users.

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CADut3oBz1Yo6YJMT3u%3Dv6n%3DCsrgaizwT2cFJE2V4zcpu6soXmw%40mail.gmail.com.

[술욱]

I found the problem. 

We run our MySql in master-slave. Somehow, our slave was out of sync. We updated some tables but this app was reading our slave.

Thanks all!!

To view this discussion on the web visit https://groups.google.com/d/msgid/django-users/CAFWa6t%2BuJhCHQz54wRC%2B3q7swfxRf4qbXSZiGWvpngq1H7-tFg%40mail.gmail.com.