Django - Tutorial 039. Adding private messages and chats on the site - Part 2 (Dialogue and chat counter with unread messages)

django, сообщение, Python, чат

Gave free time to correct private messages on the site. This functionality is not used very often, so I do not make great efforts to improve it, although it is time to bring this functionality to adequate work.

Previously, there was a very big flaw, which was that the dialogue counter with unread messages was not shown, which led to the fact that the users who were sent the message simply did not pay attention to it, because they did not know about it.

Now I finally fixed this flaw. And in the framework of the previous code I will show which corrections were added.

I thought about two options for organizing unread messages counters. Rather, one of the options and its more advanced version.

• For each request, check all chats, select the latest messages from them and check whether the author is the authorized user for whom you want to check this message. If he is not the author, then we check if the message has been read, if not, then we consider this dialogue unread for this user. The number of such dialogs will be considered the number of unread dialogs.
• А второй вариант, на котором я остановился предполагает ту же самую логику, только диалог или чат должен иметь внешний ключ на самое последнее сообщение, которое было в него добавлено. Данный ключ будет обновляться при каждом новом сообщении. Тогда отпадает необходимость выборки сообщений по чату и их сортировки, чтобы получить самое последнее сообщение. Что, по-моему мнению может вылиться в большие накладные расходы для базы данных, если диалогов будет очень много.

Implementation

models.py

Add a foreign key to the last message, as well as the ChatManager chat manager.

# -*- coding: utf-8 -*-
 
#... Code from the previous part
 
 
class ChatManager(models.Manager):
    use_for_related_fields = True
 
    # The method accepts the user for which the sample should be made.
    # If the user is not added, all dialogs will be returned,
    # in which at least one message is not read
    def unreaded(self, user=None):
        qs = self.get_queryset().exclude(last_message__isnull=True).filter(last_message__is_readed=False)
        return qs.exclude(last_message__author=user) if user else qs
 
 
class Chat(models.Model):
    #... Code from the previous part
 
    # foreign key to the last message,
    # The important point is that the name of the Message class is written in the usual string,
    # because at the time of reading the Chat class the Python interpreter knows nothing about the Message class
    # You also need to add related_name, the name through which the selection of this message from the database will be associated
    last_message = models.ForeignKey('Message', related_name='last_message', null=True, blank=True, on_delete=models.SET_NULL)
 
    objects = ChatManager()
 
    @models.permalink
    def get_absolute_url(self):
        return 'users:messages', (), {'chat_id': self.pk }
 
 
class Message(models.Model):
    #... Code from the previous part

receivers.py

This is the first time I've been writing such a Python file in a project on Django. Its essence is that signal handlers from the model will be declared there. The fact is that in Django, while saving the model object, some signals are emitted that can be processed. This allows you to put some uniform logic in a separate file and make the rest of the project code a bit cleaner. The downside is that this code may not be obvious, since there will be no references to this code in other parts of the project.

# -*- coding: utf-8 -*-
 
from django.db.models.signals import post_save
from django.dispatch import receiver
 
from users.models import Message
 
 
# message object save handler
@receiver(post_save, sender=Message)
def post_save_comment(sender, instance, created, **kwargs):
    # if the object was created
    if created:
        # we indicate to the chat room where this message is located, that this is the last message
        instance.chat.last_message = instance
        # and update this foreign chat key
        instance.chat.save(update_fields=['last_message'])

But just this code will not work, because this file also needs to be loaded into the interpreter.

This can be done in the apps.py file when the application is initialized.

apps.py

This is done in the ready method

# -*- coding: utf-8 -*-
 
from django.apps import AppConfig
from django.utils.translation import ugettext_lazy as _
 
 
class UsersConfig(AppConfig):
    name = 'users'
    verbose_name = _('Users')
 
    def ready(self):
        import users.receivers

Using

Now that you have everything you need to get the number of conversations with unread messages, you can add this information to the context for rendering the template.

context['unreaded_dialogs_counter'] = user.chat_set.unreaded(user=user).count()

How to fix the old dialogues

It remains only to correct the old dialogues that already have messages. This can be done through the admin panel, if you add the appropriate action.

admin.py

# -*- coding: utf-8 -*-
 
from django.contrib import admin
 
from users import models
 
 
class ChatAdmin(admin.ModelAdmin):
    autocomplete_fields = ['members']
    search_fields = ('members',)
    actions = ['fix_last_messages']
 
    def fix_last_messages(self, request, queryset):
        for chat in queryset.all():
            chat.last_message = chat.message_set.all().order_by('-pub_date').first()
            chat.save(update_fields=['last_message'])
 
    fix_last_messages.short_description = "Fix last messages"
 
 
class MessageAdmin(admin.ModelAdmin):
    autocomplete_fields = ['chat', 'author']
    list_display = ('chat', 'author', 'message', 'pub_date', 'is_readed')
 
 
admin.site.register(models.Chat, ChatAdmin)
admin.site.register(models.Message, MessageAdmin)