Mercurial > public > sg101
annotate gpp/messages/management/commands/purge_messages.py @ 102:e67c4dd98db5
Forums: new topic form sprouts boolean fields for sticky and locking if the user has rights. Implemented the locked logic. Fixed a bug where topics where getting out of order (the view_count was bumping the update_date because of auto_now).
| author | Brian Neal <bgneal@gmail.com> |
|---|---|
| date | Wed, 16 Sep 2009 02:01:57 +0000 |
| parents | dbd703f7d63a |
| children | 5171a5e9353b |
| rev | line source |
|---|---|
| gremmie@1 | 1 """ |
| gremmie@1 | 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 |
| gremmie@1 | 19 |
| gremmie@1 | 20 # vim: ts=4 sw=4 |