[Django] #34269: Add Unnest PostgreSQL ORM function

[Django]

#34269: Add Unnest PostgreSQL ORM function
-----------------------------------------+------------------------
Reporter: Niccolò Mineo | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 4.1
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 1
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
I'd like to suggest adding this one to the PostgreSQL-specific set of
functions.

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

[Django]

#34269: Add Unnest PostgreSQL ORM function

-------------------------------+--------------------------------------

Reporter: Niccolò Mineo | Owner: nobody
Type: Uncategorized | Status: new
Component: Uncategorized | Version: 4.1

Severity: Normal | Resolution:

Keywords: | Triage Stage: Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-------------------------------+--------------------------------------
Description changed by Niccolò Mineo:

Old description:

> I'd like to suggest adding this one to the PostgreSQL-specific set of
> functions.

New description:

I'd like to suggest adding this one to the PostgreSQL-specific set of
functions.

https://github.com/django/django/pull/16479

--

--
Ticket URL: <https://code.djangoproject.com/ticket/34269#comment:1>

[Django]

#34269: Add Unnest PostgreSQL ORM function

-------------------------------------+-------------------------------------

Reporter: Niccolò Mineo | Owner: nobody
Type: Uncategorized | Status: new

Component: Database layer | Version: 4.1
(models, ORM) |

Severity: Normal | Resolution:
Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0

-------------------------------------+-------------------------------------
Changes (by Niccolò Mineo):

* component: Uncategorized => Database layer (models, ORM)

--
Ticket URL: <https://code.djangoproject.com/ticket/34269#comment:2>

[Django]

#34269: Add Unnest PostgreSQL ORM function
-------------------------------------+-------------------------------------
Reporter: Niccolò Mineo | Owner: nobody

Type: New feature | Status: closed

Component: Database layer | Version: 4.1
(models, ORM) |

Severity: Normal | Resolution: wontfix

Keywords: | Triage Stage:
| Unreviewed
Has patch: 1 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------

Changes (by Mariusz Felisiak):

* status: new => closed
* type: Uncategorized => New feature
* resolution: => wontfix

Comment:

As far as I'm aware, after implementing #28643 we don't want to add more
functions to the core unless they are common and supported by all
backends. The current thread is to keep Django a core framework, not
providing every utility which might be useful.

If you don't agree than first start a discussion on the
DevelopersMailingList, where you'll reach a wider audience and see what
other think, and
​[https://docs.djangoproject.com/en/stable/internals/contributing
/triaging-tickets/#closing-tickets follow triaging guidelines with regards
to wontfix tickets].

PS. It's a bit sad that I have to repeat myself. I'm afraid that you're
going to open tickets for more database functions without taking into
account [https://docs.djangoproject.com/en/stable/internals/contributing
/bugs-and-features/#requesting-features the guidelines with regards to
requesting features].

--
Ticket URL: <https://code.djangoproject.com/ticket/34269#comment:3>