33👍
If you use Django 1.1+, just use F expressions:
from django.db.models import F
...
MyModel.objects.filter(id=...).update(hit_count=F('hit_count')+1)
This will perform a single atomic database query.
As gerdemb says, you should consider putting this in a middleware to make it easily reusable so it doesn’t clutter up all your views.
4👍
As gerdemb says, you should write it into a middleware to make it really reusable. Or (simpler) write a function decorator. In fact, there are adaptors to use a middleware as a decorator and viceversa.
But if you’re worried about performance and want to keep the DB queries per page hit low, you can use memcached’s atomic increment operation. of course, in this case, you have to take care of persistence yourself.
0👍
The model conventions won’t be atomic; write it by hand:
BEGIN
SELECT * FROM table WHERE id=3 FOR UPDATE
UPDATE table SET hit_count=hit_count+1 WHERE id=3
COMMIT
- Django CSRF cookie not set correctly
- Customizing django admin ChangeForm template / adding custom content
- Django logging – django.request logger and extra context
- Why is Django's Meta an old-style class?
- How do I construct a Django form with model objects in a Select widget?
0👍
I would start by looking at the documentation for middleware. Ignacio’s comment about the lack of atomic transactions is true, but this is a problem with the entire Django framework. Unless you’re concerned about having a 100% accurate counter I wouldn’t worry about it.
- Pylint (pylint_django) does not work when –django-settings-module flag is specified
- How do I use perform_create to set a field automatically in Django Rest Framework?
- Django HTML E-mail template doesn't load css in the e-mail
- Django template {%for%} tag add li every 4th element