diff options
author | rene <rene@FreeBSD.org> | 2015-12-09 04:21:14 +0800 |
---|---|---|
committer | rene <rene@FreeBSD.org> | 2015-12-09 04:21:14 +0800 |
commit | 90fa57e7ba775589f0d376bd0779c9885ea2f2c8 (patch) | |
tree | 9d4ee3be131377ae85709461e4d9fd80fee85719 /mail/milter-greylist-devel | |
parent | 1ae40d389f43e50c3c7f9b4ea642644bbe70886e (diff) | |
download | freebsd-ports-gnome-90fa57e7ba775589f0d376bd0779c9885ea2f2c8.tar.gz freebsd-ports-gnome-90fa57e7ba775589f0d376bd0779c9885ea2f2c8.tar.zst freebsd-ports-gnome-90fa57e7ba775589f0d376bd0779c9885ea2f2c8.zip |
A better alternative to the native transaction signals of Django.
Sometimes you need to fire off an action related to the current database
transaction, but only if the transaction successfully commits. Examples:
a Celery task, an email notification, or a cache invalidation.
Doing this correctly while accounting for savepoints that might be
individually rolled back, closed/dropped connections, and idiosyncrasies of
various databases, is non-trivial. Transaction signals just make it easier
to do it wrong.
django-transaction-hooks does the heavy lifting so you don't have to.
WWW: https://github.com/arljm/django-transaction-hooks/
Diffstat (limited to 'mail/milter-greylist-devel')
0 files changed, 0 insertions, 0 deletions