#34489: feature: Support for PostgreSQL table partitioning
-------------------------------------+-------------------------------------
Reporter: Anuj Sharma | Owner: nobody
Type: New feature | Status: closed
Component: Database layer | Version: 4.2
(models, ORM) |
Severity: Normal | Resolution: needsinfo
Keywords: postgresql, table- | Triage Stage:
partitioning, composite primary | Unreviewed
key |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Natalia Bidart):
* status: new => closed
* resolution: => needsinfo
Comment:
Composite primary keys feature is being tracked in ticket #373 and in
MultipleColumnPrimaryKeys, and it has been discussed in the developer
mailing list multiple times (at least in [[https://groups.google.com/g
/django-developers/c/SyNwoGUtkTU/m/_RNCGnLKRCMJ|2008]],
[[https://groups.google.com/g/django-
developers/c/OeA7PcK87to/m/oAY7epAgBwAJ|2020]] and
[[https://groups.google.com/g/django-developer|2021]]).
I think that the specific feature that is being requested should be first
discussed and agreed on the developers mailing list, since I couldn't find
an existing post or ticket about it. Setting this ticket as `needsinfo`
since agreement and some high-level design is needed before accepting this
as a new feature.
--
Ticket URL: <https://code.djangoproject.com/ticket/34489#comment:2>
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/010701877f7a12b2-7468e8a6-b444-4bf4-9700-1b541b572467-000000%40eu-central-1.amazonses.com.
