[Django] #33238: Implement PostgreSQL Multi Range data types

[Django]

#33238: Implement PostgreSQL Multi Range data types
-------------------------------------+-------------------------------------
Reporter: Andrew | Owner: (none)
Chen Wang |
Type: New | Status: new
feature |
Component: | Version: 3.2
contrib.postgres | Keywords:
Severity: Normal | postgresql,multirange,multi
Triage Stage: | Has patch: 0
Unreviewed |
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-------------------------------------+-------------------------------------
PostgreSQL v14 was released on Sep 30th and includes multi range data
types. An example can be seen here: https://blog.crunchydata.com/blog
/better-range-types-in-postgres-14-turning-100-lines-of-sql-into-3. A
multi range data type simply prepends "multi" to "range" in the name of
the data type. For instance, tstzrange becomes tstzmultirange which looks
like an array with tstzranges. The benefit of having this is to avoid
large SQL statements and "precomputing availability on large systems".

--
Ticket URL: <https://code.djangoproject.com/ticket/33238>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.

[Django]

#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>