#33238: Implement PostgreSQL Multi Range data types
-------------------------------------+-------------------------------------
Reporter: Andrew Chen Wang | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: 3.2
Severity: Normal | Resolution: wontfix
Keywords: | Triage Stage:
postgresql,multirange,multi | Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Mariusz Felisiak):
* status: new => closed
* resolution: => wontfix
Comment:
Thanks for this proposition, however it looks niche and can be hard to
maintain (tricky update, custom operators, probably new database
functions, etc.). Personally, I would add a related table with a `range`
field instead of a `multirange` field. It sounds like a third-party
package is the best way to proceed.
You can start a discussion on DevelopersMailingList if you don't agree,
[https://docs.djangoproject.com/en/stable/internals/contributing/triaging-
tickets/#closing-tickets following triaging guidelines with regards to
wontfix tickets].
--
Ticket URL: <https://code.djangoproject.com/ticket/33238#comment:1>
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/074.a99f62ee7d1cca18f454599180cdab7a%40djangoproject.com.
