Opened 2 years ago
Closed 2 years ago
#34269 closed New feature (wontfix)
Add Unnest PostgreSQL ORM function
| Reported by: | Niccolò Mineo | Owned by: | nobody |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 4.1 |
| Severity: | Normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | yes | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
I'd like to suggest adding this one to the PostgreSQL-specific set of functions.
Change History (3)
comment:1 by , 2 years ago
| Description: | modified (diff) |
|---|
comment:2 by , 2 years ago
| Component: | Uncategorized → Database layer (models, ORM) |
|---|
comment:3 by , 2 years ago
| Resolution: | → wontfix |
|---|---|
| Status: | new → closed |
| Type: | Uncategorized → New feature |
Note:
See TracTickets
for help on using tickets.
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 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 the guidelines with regards to requesting features.