I just found out that orand andare defined for QuerySet. This means that to do queries union or intersection, you can do:
User.objects.filter(...) | User.objects.filter(...)
User.objects.filter(...) & User.objects.filter(...)Subscribe for the news and updates
The article highlights common test case mistakes, offers ways to fix them, and provides practical tips to improve and optimize test cases.
In this article we'll review general approach to working with the best kind of projects - the ones with old untested and undocumented spaghetti code and a tight schedule. We'll review anger management techniques, coping mechanisms and some refactoring tips that might come in handy.
In this article we will write a small library for pulling metadata and creating a preview for a site just like Slack does.
In this article I will tell you how to create an interactive interface with a widely customized visual look and different filtering to view reports.
For any project there may be a need to use a database full-text search. We expect high speed and relevant results from this search. When we face such problem, we usually think about Solr, ElasticSearch, Sphinx, AWS CloudSearch, etc. But in this article we will talk about PostgreSQL. Starting from version 8.3, a full-text search support in PostgreSQL is available. Let's look at how it is implemented in the DBMS itself.
It appears that not everyone knows that in python you can create classes dynamically without metaclasses. I'll show an example of how to do it.So we've learned how to use custom QuerySet to chain requests:Article.objects.old().public()Now we need to make it work for related objects:user.articles.old().public()This is done using use_for_related_fields, but it needs a little trick.