2007/4/22, Honza Král <[EMAIL PROTECTED]>:
> On 4/22/07, aaloy <[EMAIL PROTECTED]> wrote:
> >
> > Hello All!
> Hello,
>
> >
> > I have a view like
> >
> > def record(request, id, type):
> >  # some database code here
> >  # some log code here
> > record=cache_page(record,60)
> >
> > If I have correctly understood the documentation, if I maque a request
> > to that view with the same parameters the view shoud'nt hit the
> > database neither get logs. Should it?
> > At this moment it hits! So I don't understand what I'm doing wrong.
>
> I am afraid that's not enough information, do you have correct
> CACHE_BACKEND configured?
Yes, I have tried with different backends in fact. . Actually I have
configured a file cache backend so I can see the caches just making an
ls. I have a template that uses the cache low level api to get the
contents and it works. My impression is that the decorator is not
working when you have some parameters in the view.
If I use the @ decorators syntax in the view I get an error when the
view has parameters. So I think they coud be related issues.

> next time please post questions about using django to django-users
> list, this list is for discussing development of Django itself. You
> will have better chances of someone replying...
>
Yes, I know. But this is so strange that it seems more development/bug
related. So I thought this is was the right place. I don't  mind to
continue the disscussion in the other list, but I think this is not a
"how to do it question".

-- 
Antoni Aloy López
Binissalem - Mallorca
http://www.trespams.com
Soci de Bulma - http://www.bulma.cat

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to