Skip to main content

A ReverseUnique field implementation for Django

Project description

Build Status Coverage Status

A ReverseUnique model field implementation for Django

The ReverseUnique field can be used to access single model instances from the reverse side of ForeignKey. Essentially, ReverseUnique can be used to generate OneToOneField like behaviour in the reverse direction of a normal ForeignKey. The idea is to add an unique filter condition when traversing the foreign key to reverse direction.

To be able to use reverse unique, you will need a unique constraint for the reverse side or otherwise know that only one instance on the reverse side can match.

Example

It is always nice to see actual use cases. We will model employees with time dependent salaries in this example. This use case could be modelled as:

class Employee(models.Model):
    name = models.TextField()

class EmployeeSalary(models.Model):
    employee = models.ForeignKey(Employee, related_name='employee_salaries')
    salary = models.IntegerField()
    valid_from = models.DateField()
    valid_until = models.DateField(null=True)

It is possible to save data like “Anssi has salary of 10€ from 2000-1-1 to 2010-1-1, and salary of 11€ from 2010-1-1 to infinity (modelled as None in the models).

Unfortunately when using these models it isn’t trivial to just fetch the employee and his salary to display to the user. It would be possible to do so by looping through all salaries of an employee and checking which of the EmployeeSalaries is currently in effect. However, this approach has a couple of drawbacks:

  • It doesn’t perform well in list views

  • Most of all It is impossible to execute queries that refer the employee’s current salary. For example, getting the top 10 best paid employees or the average salary of employees is impossible to achieve in single query.

Django-reverse-unique to the rescue! Lets change the Employee model to:

from datetime import datetime
class Employee(models.Model):
    name = models.TextField()
    current_salary = models.ReverseUnique(
        "EmployeeSalary",
        filter=Q(valid_from__gte=datetime.now) &
               (Q(valid_until__isnull=True) | Q(valid_until__lte=datetime.now))
    )

Now we can simply issue a query like:

Employee.objects.order_by('current_salary__salary')[0:10]

or:

Employee.objects.aggregate(avg_salary=Avg('current_salary__salary'))

What did happen there? We added a ReverseUnique field. This field is the reverse of the EmployeeSalary.employee foreign key with an additional restriction that the relation must be valid at the moment the query is executed. The first “EmployeeSalary” argument refers to the EmployeeSalary model (we have to use string as the EmployeeSalary model is defined after the Employee model). The filter argument is a Q-object which can refer to the fields of the remote model.

Another common problem for Django applications is how to store model translations. The storage problem can be solved with django-reverse-unique. Here is a complete example for that use case:

from django.db import models
from reverse_unique import ReverseUnique
from django.utils.translation import get_language, activate

class Article(models.Model):
    active_translation = ReverseUnique("ArticleTranslation",
                                       filters=Q(lang=get_language))

class ArticleTranslation(models.Model):
    article = models.ForeignKey(Article)
    lang = models.CharField(max_length=2)
    title = models.CharField(max_length=100)
    body = models.TextField()

    class Meta:
        unique_together = ('article', 'lang')

activate("fi")
objs = Article.objects.filter(
    active_translation__title__icontains="foo"
).select_related('active_translation')
# Generated query is
#    select article.*, article_translation.*
#      from article
#      join article_translation on article_translation.article_id = article.id
#                               and article_translation.lang = 'fi'
# If you activate "en" instead, the lang is changed.
# Now you can access objs[0].active_translation without generating more
# queries.

Similarly one could fetch current active reservation for a hotel room etc.

Installation

The requirement for ReverseUnique is Django 1.6+. You will need to place the reverse_unique directory in Python path, then just use it like done in above example. The tests (reverse_unique/tests.py) contain a couple more examples. Easiest way to install is:

pip install -e git://github.com/akaariai/django-reverse-unique.git#egg=reverse_unique

Testing

You’ll need to have a supported version of Django installed. Go to testproject directory and run:

python manage.py test reverse_unique

Project details


Release history Release notifications | RSS feed

This version

1.0

Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

django-reverse-unique-1.0.tar.gz (5.9 kB view details)

Uploaded Source

Built Distribution

django_reverse_unique-1.0-py2.py3-none-any.whl (8.9 kB view details)

Uploaded Python 2 Python 3

File details

Details for the file django-reverse-unique-1.0.tar.gz.

File metadata

File hashes

Hashes for django-reverse-unique-1.0.tar.gz
Algorithm Hash digest
SHA256 3eb5fda7d79aa15bdaae564ebfae4e9c5fde6fd8c7bcf0079a06c03e393455f9
MD5 7e24ca83d113bc2cb7fec521f1122a1f
BLAKE2b-256 628f76c1a9959b3bfa70c482a5460516f71f0041341ef29ea80ea4658630a78a

See more details on using hashes here.

File details

Details for the file django_reverse_unique-1.0-py2.py3-none-any.whl.

File metadata

File hashes

Hashes for django_reverse_unique-1.0-py2.py3-none-any.whl
Algorithm Hash digest
SHA256 f2dbbfee2467bf6d43285d80e6c0c5dbf3169943b81777e1fbeeeff8e936253f
MD5 cf39f2253c9ec6d77f268b115dd77a20
BLAKE2b-256 5d4f7e483a8d3dcca5d2f4b651d2f935df94e56d6862072bca8ca3a5c202e2d6

See more details on using hashes here.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page