#24632: PostgreSQL table inheritance
-------------------------------------+-------------------------------------
Reporter: yennicks | Owner:
Type: New feature | Status: new
Component: contrib.postgres | Version: master
Severity: Normal | Resolution:
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
-------------------------------------+-------------------------------------
Comment (by mjtamlyn):
For the record, I did actually consider this when working out which
features to include in contrib.postgres and ultimately rejected it as I'm
really not sure how we can handle it. I also spoke to some postgres people
who suggested that in most cases the way Django does inheritance is better
anyway. This is of course all up for discussion, but I don't intend to try
to implement this myself.
--
Ticket URL: <https://code.djangoproject.com/ticket/24632#comment:3>
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 post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/066.69946ba88e5dc126b016b7755f9dec06%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
