Recovering from a loss of data integrity / support for transactions about stream-django HOT 3 OPEN

unfortunately Django does not expose transactions callbacks (only 1.9 does it) so it is fairly hard for the integration library to detect rollbacks / execute only after the transaction is commited out of the box. One way to do this is to disable the default behavior and manually perform activity inserts/deletes in your own app. Feel free to add some code from your app o add more description of your use case.

from stream-django.

Not sure manually inserting/deleting is really the best way to go since it adds a lot of complication and editing code gets a lot more involved.

Actually, what you mentioned about the transaction callbacks being exposed in 1.9 helped me stumble across a library that provides transaction commit callbacks for Django 1.6+, so thanks for that :) https://django-transaction-hooks.readthedocs.org/en/latest/.

from stream-django.

Here's one example of what I mean (in regards to cleaning up). I've set up a manual signal handler that creates notifications only. Something like this:

@receiver(post_save, sender=ConversationMessage)
def send_message_notification(instance, created, **kwargs):
    if created:
        recipients = instance.conversation.users.exclude(pk=instance.author_id)
        feeds = ["notification:%d" % u.id for u in recipients]
        stream_client.add_to_many({
            'actor': create_reference(instance.author),
            'verb': 'message',
            'object': create_reference(instance.conversation),
            'message': create_reference(instance),
            'time': instance.created_at,
            'foreign_id': create_reference(instance),
        }, feeds)

How would I write the other side of this handler, i.e. the post_delete signal? Because the notifications are not bound to a source feed.

from stream-django.