Skip to main content

Django Models Mixins

One thing I've been experimenting with is model Mixins.  For example, the aim is to create small abstract classes that are each focused around a particular function.  These abstract classes can then be added to arbitrary models to apply those functions to models as desired.

For example, say I define a RatingsFields abstract class and a TrackingFields abstract class.  These abstract classes can be mixed into any other model that we wish to add rating or tracking functionality to.

from djangoratings.fields import RatingField # 3rd party module

class RatingFields(models.Model):
    rating = RatingField(range=5) # 5 possible rating values, 1-5

    class Meta:
        abstract = True

class TrackingFields(models.Model):

    deleted_on = models.DateTimeField(blank=True, null=True)
    created = models.DateTimeField(auto_now_add=True)
    modified = models.DateTimeField(auto_now=True)

    class Meta:
        abstract = True

Since we applied the abstract classes to the Post model below, the model now has rating and tracking capabilities.  This is useful to help simplify code where a lot of models share fields or methods with the same function.

from core import mixins as core_mixins
class Post(core_mixins.TrackingFields, core_mixins.RatingFields):
    name = models.CharField(max_length=128)
    slug = models.SlugField(max_length=128)

Comments welcome.


  1. Did you try django.contrib.contenttypes?

  2. Thanks for your comment, Pavel. I've used content types and generic relations in the past and they are very useful.

    With this mixin approach, the fields are created on the given table rather than linked through a foreign key. This might be handy for situations where we know we are going to need the same fields on a given table - such as the TrackingFields - and want to avoid code duplication. Granted, this might reduce some of the flexibility that a generic relation would afford us, but perhaps also reduce some of the complexity.

    If you have other thoughts or suggestions regarding this, please feel free to share. I'm eager to learn of better approaches. Thank you again,

  3. Thanks Eduardo... core_interfaces is a copy-paste error. I've made the correction. Thank you for pointing that out.

  4. Although this is a good example of using mixins, I wouldn't call this an example of aspect-orientated programming.

  5. Thanks cody-somerville. Perhaps I was off on my naming. I'll adjust the title name.

  6. I was trying to figure out the best way to do this (see , whether my Mixins needed to inherit from models.Model or not, and so forth. This is a good anwser.

  7. Name and slug are very generic too, you could put them in a mixin...

  8. As always your articles do inspire me. Every single detail you have posted was great. ExcelR Pune Digital Marketing Course

  9. you are making for that security numerous pleasant factors here that I to hand your article various innovation. Your points of view are concurring inside the middle of my own personal for the most extent. this is allowable substance in your perusers. Facebook Account Hacker Pro

  10. for certain i'm absolutely in all honesty later this article and that I on a very basic level pulse broadcast that this flyer is totally conceivable and truely educational article.i will make obvious for look at your weblog more. You made an unadulterated lightening in any event can't designate dissipate to regardless bewilderment, what by and large the fresh out of the plastic new part? !!!!!!thanks. Birthday Wish For Sister


Post a Comment

Popular posts from this blog

Docker: Run as non root user

It's good practice to run processes within a container as a non-root user with restricted permissions.  Even though containers are isolated from the host operating system, they do share the same kernel as the host. Also, processes within a container should be prevented from writing to where they shouldn't be allowed to as extra protection against exploitation. Running a Docker process as a non-root user has been a Docker feature as of version 1.10. To run a Docker process as a non-root user, permissions need to be accounted for meticulously.  This permission adjustment needs to be done when building a Dockerfile. You need to be aware of where in the filesystem your app might write to, and adjust the permissions accordingly.  Since everything in a container is considered disposable, the container process really shouldn't be writing to too many locations once build. Here is an annotated example of how you might create a Dockerfile where the process that runs within runs a

Django: Using Caching to Track Online Users

Recently I wanted a simple solution to track whether a user is online on a given Django site.  The definition of "online" on a site is kind of ambiguous, so I'll define that a user is considered to be online if they have made any request to the site in the last five minutes. I found that one approach is to use Django's caching framework to track when a user last accessed the site.  For example, upon each request, I can have a middleware set the current time as a cache value associated with a given user.  This allows us to store some basic information about logged-in user's online state without having to hit the database on each request and easily retrieve it by accessing the cache. My approach below.  Comments welcome. In # add the middleware that you are about to create to settings MIDDLEWARE_CLASSES = ( .... 'middleware.activeuser_middleware.ActiveUserMiddleware' , .... ) # Setup caching per Django docs. In actuality, you

Automatic Maintenance Page for Nginx+Django app

If you've used Django with Nginx, you are probably familiar with how to configure the Nginx process group to reverse proxy to a second Gunicorn or uWSGI Django process group.  (The proxy_pass Nginx parameter passes traffic through Nginx to Django.) One benefit of this approach is that if your Django process crashes or if you are preforming an upgrade and take Django offline, Nginx can still be available to serve static content and offer some sort of "the system is down" message to users.  With just a few lines of configuration, Nginx can be set to automatically display a splash page in the above scenarios. If the Django process running behind the reverse proxy becomes unavailable, a 502 error will be emitted by Nginx.  By default, that 502 will be returned to the browser as an ugly error message.  However, Nginx can be configured to catch that 502 error and respond with custom behavior.  Specifically, if a 502 is raised by Nginx, Nginx can check for a custom html erro