svn commit: r403346 - in head/databases: . py-django-transaction-hooks

[Rene Ladan]

Author: rene
Date: Tue Dec  8 20:21:14 2015
New Revision: 403346
URL: https://svnweb.freebsd.org/changeset/ports/403346

Log:
  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/

Added:
  head/databases/py-django-transaction-hooks/
  head/databases/py-django-transaction-hooks/Makefile   (contents, props changed)
  head/databases/py-django-transaction-hooks/distinfo   (contents, props changed)
  head/databases/py-django-transaction-hooks/pkg-descr   (contents, props changed)
Modified:
  head/databases/Makefile

Modified: head/databases/Makefile
==============================================================================
--- head/databases/Makefile	Tue Dec  8 19:45:21 2015	(r403345)
+++ head/databases/Makefile	Tue Dec  8 20:21:14 2015	(r403346)
@@ -698,6 +698,7 @@
     SUBDIR += puredb
     SUBDIR += pxlib
     SUBDIR += pxtools
+    SUBDIR += py-django-transaction-hooks
     SUBDIR += py-Elixir
     SUBDIR += py-MySQLdb
     SUBDIR += py-MySQLdb55

Added: head/databases/py-django-transaction-hooks/Makefile
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/databases/py-django-transaction-hooks/Makefile	Tue Dec  8 20:21:14 2015	(r403346)
@@ -0,0 +1,22 @@
+# Created by: René Ladan <rene at freebsd.org>
+# $FreeBSD$
+
+PORTNAME=	django-transaction-hooks
+PORTVERSION=	0.2
+CATEGORIES=	databases python
+MASTER_SITES=	CHEESESHOP
+PKGNAMEPREFIX=	${PYTHON_PKGNAMEPREFIX}
+
+MAINTAINER=	rene at freebsd.org
+COMMENT=	Django database backends to register transaction-commit hooks
+
+LICENSE=	BSD3CLAUSE
+
+RUN_DEPENDS=	${PYTHON_PKGNAMEPREFIX}django>=1.6.1:${PORTSDIR}/www/py-django
+
+NO_ARCH=	yes
+
+USES=		python
+USE_PYTHON=	autoplist distutils
+
+.include <bsd.port.mk>

Added: head/databases/py-django-transaction-hooks/distinfo
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/databases/py-django-transaction-hooks/distinfo	Tue Dec  8 20:21:14 2015	(r403346)
@@ -0,0 +1,2 @@
+SHA256 (django-transaction-hooks-0.2.tar.gz) = 51bab09547fab673a24d6c59f1df560183b3a49f24a7a5bf35e7eb34ef939e79
+SIZE (django-transaction-hooks-0.2.tar.gz) = 7527

Added: head/databases/py-django-transaction-hooks/pkg-descr
==============================================================================
--- /dev/null	00:00:00 1970	(empty, because file is newly added)
+++ head/databases/py-django-transaction-hooks/pkg-descr	Tue Dec  8 20:21:14 2015	(r403346)
@@ -0,0 +1,14 @@
+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/