Django model mixins and utilities.
Install from PyPI with easy_install or pip:
pip install django-model-utils
or get the in-development version:
pip install django-model-utils==tip
To use django-model-utils in your Django project, just import the utility classes described below; there is no need to modify your INSTALLED_APPS setting.
django-model-utils requires Django 1.0 or later.
ChoiceEnum makes setting choices on a Django model field way too easy:
from model_utils import ChoiceEnum class Article(models.Model): STATUS = ChoiceEnum('draft', 'published') # ... status = models.PositiveIntegerField(choices=STATUS, default=STATUS.draft) def status_desc(self): return self.STATUS[self.status]
A ChoiceEnum object is initialized with any number of choices, which should be strings. It assigns a sequential id to each choice. The numerical id for a choice is available through attribute access (STATUS.draft), and the text name for a choice can be obtained by indexing with the numerical id (self.STATUS[self.status]). If iterated over, a ChoiceEnum object yields a tuple of two-tuples linking id to text names, the format expected by the choices attribute of Django models.
Be careful not to add new choices in the middle of the list, as that will change the numerical ids for all subsequent choices, which could impact existing data.
A TextField subclass that automatically pulls an excerpt out of its content (based on a "split here" marker or a default number of initial paragraphs) and stores both its content and excerpt values in the database.
A SplitField is easy to add to any model definition:
from django.db import models from model_utils.fields import SplitField class Article(models.Model): title = models.CharField(max_length=100) body = SplitField()
SplitField automatically creates an extra non-editable field _body_excerpt to store the excerpt. This field doesn't need to be accessed directly; see below.
Accessing a SplitField on a model
When accessing an attribute of a model that was declared as a SplitField, a SplitText object is returned. The SplitText object has three attributes:
- The full field contents.
- The excerpt of content (read-only).
- True if the excerpt and content are the same, False otherwise.
This object also has a __unicode__ method that returns the full content, allowing SplitField attributes to appear in templates without having to access content directly.
Assuming the Article model above:
>>> a = Article.objects.all() >>> a.body.content u'some text\n\n<!-- split -->\n\nmore text' >>> a.body.excerpt u'some text\n' >>> unicode(a.body) u'some text\n\n<!-- split -->\n\nmore text'
Assignment to a.body is equivalent to assignment to a.body.content.
a.body.excerpt is only updated when a.save() is called
By default, SplitField looks for the marker <!-- split --> alone on a line and takes everything before that marker as the excerpt. This marker can be customized by setting the SPLIT_MARKER setting.
If no marker is found in the content, the first two paragraphs (where paragraphs are blocks of text separated by a blank line) are taken to be the excerpt. This number can be customized by setting the SPLIT_DEFAULT_PARAGRAPHS setting.
This abstract base class can be inherited by the root (parent) model in a model-inheritance tree. It allows each model in the tree to "know" what type it is (via an automatically-set foreign key to ContentType), allowing for automatic casting of a parent instance to its proper leaf (child) type.
For instance, if you have a Place model with subclasses Restaurant and Bar, you may want to query all Places:
nearby_places = Place.objects.filter(location='here')
But when you iterate over nearby_places, you'll get only Place instances back, even for objects that are "really" Restaurant or Bar. If you have Place inherit from InheritanceCastModel, you can just call the cast() method on each Place and it will return an instance of the proper subtype, Restaurant or Bar:
from model_utils.models import InheritanceCastModel class Place(InheritanceCastModel): ... class Restaurant(Place): ... nearby_places = Place.objects.filter(location='here') for place in nearby_places: restaurant_or_bar = place.cast() ...
This is inefficient for large querysets, as it results in n queries to the subtype tables. It would be possible to write a QuerySet subclass that could reduce this to k queries, where there are k subtypes in the inheritance tree.
This abstract base class just provides self-updating created and modified fields on any model that inherits it.
Many custom model managers do nothing more than return a QuerySet that is filtered in some way. QueryManager allows you to express this pattern with a minimum of boilerplate:
from django.db import models from model_utils.managers import QueryManager class Post(models.Model): ... published = models.BooleanField() pub_date = models.DateField() ... objects = models.Manager() public = QueryManager(published=True).order_by('-pub_date')
The kwargs passed to QueryManager will be passed as-is to the QuerySet.filter() method. You can also pass a Q object to QueryManager to express more complex conditions. Note that you can set the ordering of the QuerySet returned by the QueryManager by chaining a call to .order_by() on the QueryManager (this is not required).