summaryrefslogtreecommitdiff
path: root/databases/py-django-transaction-hooks (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Remove ${PORTSDIR}/ from dependencies, categories d, e, f, and g.Mathieu Arnold2016-04-011-1/+1
| | | | | | | | With hat: portmgr Sponsored by: Absolight Notes: svn path=/head/; revision=412346
* - Switch forgotten ports over to py-django18Martin Wilke2016-01-161-1/+2
| | | | | | | | | - Fix PYTHON_PKGNAMEPREFIX Reported by: antoinebot Notes: svn path=/head/; revision=406208
* - Update MAINTAINER: use @FreeBSD.orgSunpoet Po-Chuan Hsieh2015-12-251-1/+1
| | | | Notes: svn path=/head/; revision=404403
* A better alternative to the native transaction signals of Django.Rene Ladan2015-12-083-0/+38
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/ Notes: svn path=/head/; revision=403346