I don't go to a lot of tech conferences - family life tends to make getting away for any length of time fairly difficult. So originally I ignored the banners advertising the Stack Overflow DevDays, thinking I wouldn't be able to make it anyway. But when my employer arbitrarily ...
read moreThere are comments.
I previously wrote about a thread-safety bug I encountered in writing a middleware object. I recently found a very similar situation in a class-based view I was modifying, and thought it was worth writing up what the problem was and how I solved it. Interestingly, there's a discussion going ...
read moreThere are comments.
This blog is built using Kevin Fricovsky's excellent django-mingus project, which is mainly a set of standard pre-existing reusable apps with some templates and a bit of glue to hold it together.
Although it's quite usable out of the box, I found - inveterate hacker that I am - that ...
read moreThere are comments.
This is intended to be primarily a technical blog, so I was keen to get the presentation of code snippets correct. I'm a - shall we say - fairly frequent answerer on StackOverflow, and I've got used to their Markdown-enabled edit box. Luckily, the Mingus basic-blog application allows a choice ...
read moreThere are comments.
I love Django's aggregation framework. It very successfully abstracts the common aggregration tasks into a Pythonic syntax that sits extremely well with the rest of the ORM, and the documentation explains it all without a single reference to SQL.
But sometimes that very abstraction gets in the way of ...
read moreThere are comments.
One of the main sources of unnecessary database queries in Django applications is reverse relations.
By default, Django doesn't do anything to follow relations across models. This means that unless you're careful, any relationship can lead to extra hits on the database. For instance, assuming MyModel has a ...
read moreThere are comments.
I've previously talked about how to make reverse lookups more efficient using a simple dictionary trick. Today I want to write about how this can be extended to generic relations.
At its heart, a generic relationship is defined by two elements: a foreign key to the ContentType table, to ...
read moreThere are comments.
My last post talked about how to follow reverse generic relations efficiently. However, there's a further potential inefficiency in using generic relations, and that's the forward relationship.
If once again we take the example of an Asset model with a GenericForeignKey used to point at Articles and Galleries ...
read moreThere are comments.
Page 1 / 3 »