Mercurial > public > sg101
annotate 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 |
| rev | line source |
|---|---|
| gremmie@1 | 1 """ |
| bgneal@518 | 2 purge_messages is a custom manage.py command for the messages application. |
| gremmie@1 | 3 It is intended to be called from a cron job to purge messages that have been |
| gremmie@1 | 4 deleted by both sender and receiver. |
| gremmie@1 | 5 """ |
| gremmie@1 | 6 |
| gremmie@1 | 7 from django.core.management.base import NoArgsCommand |
| gremmie@1 | 8 |
| gremmie@1 | 9 from messages.models import Message |
| gremmie@1 | 10 |
| gremmie@1 | 11 |
| gremmie@1 | 12 class Command(NoArgsCommand): |
| gremmie@1 | 13 help = "Delete messages that have been sent to the trash by both sender and receiver." |
| gremmie@1 | 14 |
| gremmie@1 | 15 def handle_noargs(self, **options): |
| gremmie@1 | 16 Message.objects.filter(sender_delete_date__isnull=False, |
| gremmie@1 | 17 receiver_delete_date__isnull=False).delete() |
| gremmie@1 | 18 |