Mercurial > public > sg101
view forums/signals.py @ 1037:7e0c3cbd3cda
Fix bad select_related call.
In Django 1.8, select_related now throws an error if you give it an invalid
field. This was happening. Fix that query.
Also noticed an extra query generated in the display_post template. Fixed.
author | Brian Neal <bgneal@gmail.com> |
---|---|
date | Tue, 29 Dec 2015 22:21:42 -0600 |
parents | 5902dc5e58a3 |
children |
line wrap: on
line source
""" Signals for the forums application. """ import django.dispatch # This signal is sent when a topic has had its textual content (title) changed. # The provided arguments are: # sender - the topic model instance # created - True if the topic is new, False if updated topic_content_update = django.dispatch.Signal(providing_args=['created']) # This signal is sent when a post has had its textual content (body) changed. # The provided arguments are: # sender - the post model instance # created - True if the post is new, False if updated post_content_update = django.dispatch.Signal(providing_args=['created']) def notify_new_topic(topic): """ Sends the topic_content_update signal for a new topic instance. """ topic_content_update.send_robust(topic, created=True) def notify_updated_topic(topic): """ Sends the topic_content_update signal for an updated topic instance. """ topic_content_update.send_robust(topic, created=False) def notify_new_post(post): """ Sends the post_content_update signal for a new post instance. """ post_content_update.send_robust(post, created=True) def notify_updated_post(post): """ Sends the post_content_update signal for an updated post instance. """ post_content_update.send_robust(post, created=False)