#1918 closed defect (fixed)
Current documentation for subclassing a model fails to mention it doesn't work anymore
| Reported by: | Owned by: | Jacob | |
|---|---|---|---|
| Component: | Documentation | Version: | |
| Severity: | normal | Keywords: | |
| Cc: | Triage Stage: | Unreviewed | |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description
The URL at http://www.djangoproject.com/documentation/models/subclassing/ implies that model subclassing is ready for use, when many messages on django-users (and good amount of personal frustration) would seem to indicate that it's not. This page should be update to clearly state that subclassing models *will eventually* be a usable feature, but is currently to be avoided, ideally, describing alternate approaches (one-to-one relationships?).
Change History (2)
comment:1 by , 18 years ago
comment:2 by , 18 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Fixed; I removed the docs temporarily.
Note:
See TracTickets
for help on using tickets.
(in addition, maybe the docs that haven't been updated since before the m-r merge could also be marked as such)