After refactoring on the site, four main entities were identified, in which common properties were identified, namely:
- Article - articles
- Comment - comments
- ForumTopic - Forum themes (questions)
- ForumPost - Answers to forum topics
Of course, and so it was clear that these entities can have the same data fields, the same methods, etc. But when developing this site, I myself simultaneously study Python and Django. Therefore, the project has the character of chaotic introduction of small ToDo with subsequent refactoring in the study of the best approaches. Therefore, after studying the inheritance capabilities of models in Django, one general abstract data model was identified, PostBase , which has four fields that are repeated in all the above modeled models.
There is one important point here: A model that is declared abstract will not create a table in the database.
To create an abstract model, you must set the abstract variable to True for the Meta class.
PostBase is a basic abstract model. In this abstract data model, four fields were identified that are common to the above models:
- author - Author of an article, comment, topic or answer;
- content - content;
- pub_date - Publication date;
moderation - Moderation, all content can have four possible options:
- SPAM - No comments;
- NOT_MODERATED - Unverified entry, in this case, articles of users with this status will not be available to other users before moderation;
- POST_MODERATED - approval after publishing an article user will be available to other users after publication, but it has not passed moderation;
- MODERATED - The record was moderated.
The declaration of this abstract model will be as follows:
# -*- coding: utf-8 -*- from django.db import models from django.contrib.auth.models import User from django.utils.translation import ugettext_lazy as _ from ckeditor_uploader.fields import RichTextUploadingField class PostBase(models.Model): class Meta: abstract = True # This field indicates that the class is abstract # and that it does not need to create a table for it SPAM = 'S' NOT_MODERATED = 'N' POST_MODERATED = 'P' MODERATED = 'M' MODERATION_CHOICES = ( (SPAM, 'SPAM'), (NOT_MODERATED, 'Not Moderated'), (POST_MODERATED, 'Post Moderated'), (MODERATED, 'Moderated') ) author = models.ForeignKey(User, verbose_name=_("Author")) content = models.TextField(_('Content'), blank=True) pub_date = models.DateTimeField(_('Publication date'), blank=True, null=True) moderation = models.CharField( _('Модерация'), max_length=1, choices=MODERATION_CHOICES, default=NOT_MODERATED )
Thus, it is possible to shorten the program code of the project and add the possibility of reusing duplicate code.
The structure of the model, for example, for comments, can now look like this:
class Comment(PostBase): class Meta: db_table = "comments" article = models.ForeignKey(Article)
The author, pub_date, content, and moderation fields are no longer required because they are present in the PostBase class. The main thing is not to enter into your model fields with the same names as in the PostBase model.
Also an obvious plus is that you can also exactly make one common for all classes setting the admin panel.
We will, for example, display fields, configure the search and filter content and the ability to set the status of moderation (that is, add the appropriate actions ).
class PostBaseAdmin(admin.ModelAdmin): list_display = ('content', 'author', 'pub_date') search_fields = ('content', 'author__username') list_filter = ('moderation',) actions = ['make_spam', 'make_not_moderated', 'make_post_moderated', 'make_moderated'] def moderate(self, request, rows_updated, choice_description): if rows_updated == 1: message_bit = "1 entry is marked as %s" % choice_description else: message_bit = "%s entries are marked as %s." % (rows_updated, choice_description) self.message_user(request, "%s" % message_bit) def make_spam(self, request, queryset): self.moderate( request=request, rows_updated=queryset.update(moderation=PostBase.SPAM), choice_description="SPAM" ) make_spam.short_description = "Mark selected as SPAM" def make_not_moderated(self, request, queryset): self.moderate( request=request, rows_updated=queryset.update(moderation=PostBase.NOT_MODERATED), choice_description="NOT_MODERATED" ) make_not_moderated.short_description = "Mark selected as NOT_MODERATED" def make_post_moderated(self, request, queryset): self.moderate( request=request, rows_updated=queryset.update(moderation=PostBase.POST_MODERATED), choice_description="POST_MODERATED" ) make_post_moderated.short_description = "Mark selected as POST_MODERATED" def make_moderated(self, request, queryset): self.moderate( request=request, rows_updated=queryset.update(moderation=PostBase.MODERATED), choice_description="MODERATED" ) make_moderated.short_description = "Mark selected as MODERATED"
If you want to extend the filter sheets or add actions for one of the models, you can inherit from PostBaseAdmin as follows:
class ArticleAdmin(PostBaseAdmin): # Or completely redefine the displayed fields or fields for search list_display = ('title', 'section', 'author', 'pub_date', 'views', 'moderation') search_fields = ('title', 'author__username', 'section__title') # Or add to the existing list the additional list list_filter = PostBaseAdmin.list_filter + ('status', 'section') # In the case of actions, such an announcement will simply add new actions to existing ones actions = ['publish', 'unpublish']
For Django I recommend VDS-server of Timeweb hoster .