#33665: Add support for Postgres multirange
----------------------------------+------------------------------------
Reporter: Tom Carrick | Owner: (none)
Type: New feature | Status: new
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution:
Keywords: | Triage Stage: Accepted
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
----------------------------------+------------------------------------
Comment (by Tom Carrick):
I just found https://code.djangoproject.com/ticket/33238 for this issue
but closed as wontfix. I didn't find it the first time because I searched
for "multirange" rather than "multi range".
Anyway I do think this can be implemented without too much of a
maintenance burden. I have some ideas on the implementation but I haven't
thought about it too closely.
I just wanted to add this because I didn't see the original ticket so I'm
not sure if this one should be closed as well.
--
Ticket URL: <https://code.djangoproject.com/ticket/33665#comment:3>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/01070180840c5f45-9a12cf40-6ce5-4dda-bc54-45b6be89617c-000000%40eu-central-1.amazonses.com.
