#24632: PostgreSQL table inheritance
-------------------------------------+-------------------------------------
Reporter: Yennick Schepers | Owner: (none)
Type: New feature | Status: closed
Component: contrib.postgres | Version: dev
Severity: Normal | Resolution: wontfix
Keywords: orm postgresql | Triage Stage: Accepted
table-inheritance inheritance |
object-relational |
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------------+-------------------------------------
Changes (by Simon Charette):
* resolution: => wontfix
* status: new => closed
Comment:
This was brought up [https://forum.djangoproject.com/t/postgresql-table-
inheritance-and-orm/39047/2 on the forum recently] which made me dig a bit
more in the latest stage of things.
Now that Postgres partitioning is done natively, which is what inheritance
was mainly recommended for prior to that,
[https://wiki.postgresql.org/wiki/Don't_Do_This#Don.27t_use_table_inheritance
they recommend against using table inheritance] which I believe is a
strong enough motive to won't-fix this stagnant decade old new feature
request given how invasive such a change would be.
--
Ticket URL: <https://code.djangoproject.com/ticket/24632#comment:8>
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 visit
https://groups.google.com/d/msgid/django-updates/0107019538dd1ad7-ea22d8f9-54e6-4624-88e4-27e700bfffee-000000%40eu-central-1.amazonses.com.
