r the same
view multiple times, they are served synchronously. I don't know if
it's due to the server or django. I can't find anything like that on
the documentation. If anyone knows, I would be really interested to
understand that last part.
--
Ashe
--
You received this mes
te('test')
return render_to_response("test.html", {
}, context_instance=RequestContext(request))
If I open two terminals, I have no issue reading and writing in redis.
So I really don't understand why I'm not able to use the cache in
views.
Regards,
st))
The result of this code is very strange for me.
If I open two tabs of that view, the first view counts until 20 before
its template is displayed, then the second view starts counting. I was
expecting the second view to print just 'Already locked'.
I don't understand what I
On Feb 3, 11:55 pm, akaariai wrote:
> On Feb 4, 9:10 am, Ashe wrote:
>
> > Is there a better solution to modify only the specified field on a
> > table than :
> > self.__class__.objects.filter(id=self.id).update(myfield='new awesome
> > value')
>
at ( https://code.djangoproject.com/ticket/4102
).
If it is the best solution, is there any drawback with that solution ?
I suppose there is a read on the database because of the
objects.filter(). And we lose the possibility to use save() and
clean() before update, which I usually enjoy to override.
Regards,
--
Ash
zone,
> but as the default is UTC there is nothing to worry :) In fact, once
> 1.4 is out, it will no longer run SET TIME ZONE at all, as 1.4 is able
> to recognize that the time zone is already correct for the connection!
Thank you very much, that's perfect.
--
Ashe
--
You receive
On Jan 30, 4:54 am, Ramiro Morales wrote:
> On Mon, Jan 30, 2012 at 6:21 AM, Ashe wrote:
> > Could you help me make this modification working in the 1.3.1 ? I
> > looked at the file modified in the changeset 17128, but it looks like
> > it changed a lot between the relea
nk version on production.
Will it be in the 1.4 ? I wasn't able to tell from the changeset page.
Regards,
Ashe
--
You received this message because you are subscribed to the Google Groups
"Django users" group.
To post to this group, send email to django-users@googlegroups.com.
8 matches
Mail list logo
