Opened 13 years ago
Closed 13 years ago
#4155 closed (duplicate)
[enhancement] Allow Subclassing Models in ORM
| Reported by: | Owned by: | Adrian Holovaty | |
|---|---|---|---|
| Component: | Database layer (models, ORM) | Version: | 0.96 |
| Severity: | 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 ORM is following subclassed models to their base classes.
In theory, this would create the new table (based on all of the old models structure) with syncdb, which it does. You would then be able to access this new model just like the old one, but the data would be in the new table.
However, it is not doing so, it is accessing data from the "Spell" table in this example, when calling any of the ORM functions for TmpSpell
Change History (3)
comment:1 Changed 13 years ago by
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 Changed 13 years ago by
| Resolution: | invalid |
|---|---|
| Status: | closed → reopened |
| Summary: | Subclassing Models ORM issues → [enhancement] Allow Subclassing Models in ORM |
Note: See
TracTickets for help on using
tickets.
Model subclassing is not currently supported in Django; no guarantees are made that subclassing will or will not work.