Everybody knows about permalink, but it's usually used only in get_absolute_url. I prefer to use it for all related model urls.
class Event(models.Model):
# ...
@models.permalink
def edit_url(self):
return ('event_edit', (self.pk, ))And then in template:
Редактировать событиеSubscribe for the news and updates
Earlier in our previous article "Improve efficiency of your SELECT queries" we discussed ways to profile and optimize the performance of SELECT queries. However, to write complex yet efficient SQL queries, there is a thing to remember about.
This article is aimed for beginners, who are trying to choose between Ruby on Rails and Django. Let’s see which is fastest and why.
Quite often we have to write paginated or filtered blocks of information on page. I created a decorator that would automate this process.
When we use css-sprites it's important to make browser cache them for longest period possible. On other hand, we need to refresh them when they are updated. This is especially visible when all icons are stored in single sprite. When it's outdated - entire site becomes ugly.
As you know, model managers can be overriden in Django. It's convenient to add custom filtration method.
In my current project I had a task to use twitter API. Twitter uses OAuth for authentication, which is pretty dreary. To avoid fiddling with it all the time, I've moved authentication to decorator. If key is available - nothing happens, just view is launched as usual. It's convenient that there's no need for additional twitter settings in user profile. Code is in article.