view gpp/messages/management/commands/purge_messages.py @ 552:9e42e6618168

For bitbucket issue #2, tweak the admin settings for the Post model to reduce slow queries. Define our own queryset() method so we can control the select_related(), and not have it cascade from post to topics to forums to categories. Removed 'topic' from list_display because MySQL still sucked with 2 inner joins. Now it seems to be tolerable with only one join to User.
author Brian Neal <bgneal@gmail.com>
date Wed, 25 Jan 2012 20:07:03 -0600
parents 5171a5e9353b
children
line wrap: on
line source
"""
purge_messages is a custom manage.py command for the messages application.
It is intended to be called from a cron job to purge messages that have been
deleted by both sender and receiver.
"""

from django.core.management.base import NoArgsCommand

from messages.models import Message


class Command(NoArgsCommand):
    help = "Delete messages that have been sent to the trash by both sender and receiver."

    def handle_noargs(self, **options):
        Message.objects.filter(sender_delete_date__isnull=False,
                receiver_delete_date__isnull=False).delete()