#7674 closed (invalid)
simple SchemaEvolution
| Reported by: | tmbdev | Owned by: | nobody |
|---|---|---|---|
| Component: | Uncategorized | Version: | dev |
| 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
I read the discussion of SchemaEvolution in the wiki. General automatic SchemaEvolution is hard, but that doesn't mean that the simple cases can't be handled.
In particular, I think syncdb should handle:
- add a column (including adding a new foreign key)
- remove a column
- change the type of a column (fails if the types aren't convertible)
This would probably cover 99% of the schema evolution needs people have.
Change History (2)
comment:1 by , 16 years ago
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
comment:2 by , 16 years ago
Also see other tickets like #5934, which has been accepted as a long-term nice-to-have. I don't believe the core devs will be interested in spending much effort on a partial solution in the interim. The most productive way to get schema evolution into Django is to work with one of the existing external projects and help get it to the point where it might be considered as an addition to core.
Note:
See TracTickets
for help on using tickets.
This isn't really a bug report. It's just a feature wish and design proposals should be on the django-dev mailing list. More specifically, see django-evolution and the many threads on the mailing lists about when/if this will become part of contrib one day.