Opened 9 years ago
Closed 9 years ago
#25669 closed New feature (needsinfo)
Adding postgresql publish/subscribe mechanism to django postgres contrib module
| Reported by: | Asif Saifuddin Auvi | Owned by: | Asif Saifuddin Auvi |
|---|---|---|---|
| Component: | contrib.postgres | Version: | dev |
| Severity: | Normal | Keywords: | postgres, pubsub |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
It will be great to have postgresql's pub/sub mechanism in django.contrib.postgres
Change History (5)
comment:1 by , 9 years ago
| Owner: | set to |
|---|---|
| Status: | new → assigned |
comment:2 by , 9 years ago
| Description: | modified (diff) |
|---|
comment:3 by , 9 years ago
comment:4 by , 9 years ago
Hi,
based on the works here https://bitbucket.org/btubbs/pgpubsub/overview and postgres built in pub/sub mechanism wouldn't it good to have implemented in model based pub/sub functionality in contrib.postgres?
comment:5 by , 9 years ago
| Resolution: | → needsinfo |
|---|---|
| Status: | assigned → closed |
Could you please detail the API you have in mind and raise it on the DevelopersMailingList to get consensus on the idea?
Note:
See TracTickets
for help on using tickets.
How would you envisage this working? Can you describe a use case that would make sense for Django?
I can probably think of a couple once/if Andrew Godwin finishes off his work with Channels: https://www.aeracode.org/2015/6/17/beyond-request-response/
But I can't think of any use cases that would be tied to the regular request/response cycle. This would probably be something better implemented as a third party library in any case, or as a backend for something like django-celery.