Opened 17 years ago
Closed 16 years ago
#5099 closed (duplicate)
Provide the ability to update database to reflect changes in model definitions (i.e., schema evolution)
| Reported by: | Owned by: | nobody | |
|---|---|---|---|
| Component: | Core (Other) | Version: | dev |
| Severity: | Keywords: | schema evolution feature ALTER TABLE | |
| Cc: | DXpublica@… | Triage Stage: | Accepted |
| Has patch: | no | Needs documentation: | no |
| Needs tests: | no | Patch needs improvement: | no |
| Easy pickings: | no | UI/UX: | no |
Description (last modified by )
Django needs to provide the ability to evolve database schema - i.e., to update the database representation of project to reflect changes in the model definitions.
The design issues have been discussed here:
http://code.djangoproject.com/wiki/SchemaEvolution
A previous attempt at this feature exists in the form of the schema-evolution branch. This implementation is discussed here:
http://code.djangoproject.com/wiki/SchemaEvolutionDocumentation
However, this design has been rejected by the core developers.
Attachments (1)
Change History (7)
by , 17 years ago
| Attachment: | django_schema_evolution-SVN5821-patch.txt added |
|---|
comment:1 by , 17 years ago
Patch doesn't work against HEAD revision. Current trunk does not have management.py file.
comment:2 by , 17 years ago
| Summary: | merge the schema-evolution branch into trunk → [schema-evolution] merge the schema-evolution branch into trunk |
|---|---|
| Version: | SVN → other branch |
comment:3 by , 17 years ago
| Keywords: | feature added |
|---|
comment:4 by , 17 years ago
| Cc: | added |
|---|
comment:5 by , 17 years ago
| Description: | modified (diff) |
|---|---|
| Has patch: | unset |
| Keywords: | ALTER TABLE added |
| Summary: | [schema-evolution] merge the schema-evolution branch into trunk → Provide the ability to update database to reflect changes in model definitions (i.e., schema evolution) |
| Triage Stage: | Unreviewed → Accepted |
| Version: | other branch → SVN |
For the benefit of anyone interested in this feature; the schema-evolution branch will *not* be merged as it currently stands. The design implemented by this branch has been discussed and rejected by the core developers. Feel free to use the patch and/or branch if you find it useful, but it will *not* become the official Django schema evolution implementation.
However, the underlying feature - providing a mechanism for evolving schema - *is* of interest. I've changed the subject, description and status of this ticket to reflect this.
comment:6 by , 16 years ago
| Resolution: | → duplicate |
|---|---|
| Status: | new → closed |
See #5934 -- it rounds up the existing options, and is a nice placeholder until we can get a best-of-breed merged in.
patch against trunk/HEAD (current as of 5821)