What you're doing is saying "any _new_ results returned from this view are 
uncacheable", but that doesn't impact the results that are in the cache 
already.

Read up on this section to see how to "invalidate" the existing cache:

https://docs.djangoproject.com/en/1.4/topics/cache/#cache-versioning


On Monday, December 17, 2012 7:26:45 PM UTC-8, Dwayne Ghant wrote:
>
> Thanks Chris,
>
> That's exactly what I thought I was doing. Can you please tell me what 
> missed? How, exactly do unclear the cache; if that's not what I'm currently 
> doing?
>
> On Monday, December 17, 2012, Chris Cogdon wrote:
>
>> You'll need to clear the cache. Remember, once the view is cached, django 
>> wont go down to the view until the cache thinks the content has expired.
>>
>>
>> On Monday, December 17, 2012 5:14:56 PM UTC-8, Dwayne Ghant wrote:
>>>
>>> Hello All: 
>>>
>>> I have a python view that I'm building but the for some strange reason 
>>> the view keeps caching.  Just to give an example: 
>>>
>>> @api_view(['POST'])
>>> @parser_classes((XMLParser,))
>>> @cache_page(0)
>>> @cache_control(private=True)
>>> def test_view(request, format=None):
>>>     return Response({'received data TESTING2': 'testing'})
>>>
>>> Doesn't return "received data TESTING2': testing ." Instead, it keep 
>>> returning the old cached information. Can some please tell me how to 
>>> explicitly turn off caching while I'm still developing?  It a pain!! I I 
>>> have listed the references below that I used to trouble shoot: 
>>>
>>> https://docs.djangoproject.**com/en/dev/topics/cache/?from=**
>>> olddocs#the-per-view-cache<https://docs.djangoproject.com/en/dev/topics/cache/?from=olddocs#the-per-view-cache>
>>> https://docs.djangoproject.**com/en/dev/ref/settings/#std:**
>>> setting-CACHES<https://docs.djangoproject.com/en/dev/ref/settings/#std:setting-CACHES>
>>> https://docs.djangoproject.**com/en/dev/topics/cache/<https://docs.djangoproject.com/en/dev/topics/cache/>
>>>
>>>
>>> Any help would be deeply appreciated. 
>>>
>>> Thanx
>>>
>>>  -- 
>> You received this message because you are subscribed to the Google Groups 
>> "Django users" group.
>> To view this discussion on the web visit 
>> https://groups.google.com/d/msg/django-users/-/ImrvggfbaEkJ.
>> To post to this group, send email to django-users@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> django-users+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/django-users?hl=en.
>>
>

-- 
You received this message because you are subscribed to the Google Groups 
"Django users" group.
To view this discussion on the web visit 
https://groups.google.com/d/msg/django-users/-/S1uc6ADIzBAJ.
To post to this group, send email to django-users@googlegroups.com.
To unsubscribe from this group, send email to 
django-users+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/django-users?hl=en.

Reply via email to