Opened 17 years ago

Last modified 16 years ago

#5099 closed

Provide the ability to update database to reflect changes in model definitions (i.e., schema evolution) — at Version 5

Reported by: Derek Anderson <public@…> 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 Russell Keith-Magee)

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.

Change History (6)

by Derek Anderson <public@…>, 17 years ago

patch against trunk/HEAD (current as of 5821)

comment:1 by cheshire, 17 years ago

Patch doesn't work against HEAD revision. Current trunk does not have management.py file.

comment:2 by Simon G. <dev@…>, 17 years ago

Summary: merge the schema-evolution branch into trunk[schema-evolution] merge the schema-evolution branch into trunk
Version: SVNother branch

comment:3 by Philippe Raoult, 17 years ago

Keywords: feature added

comment:4 by anonymous, 17 years ago

Cc: DXpublica@… added

comment:5 by Russell Keith-Magee, 17 years ago

Description: modified (diff)
Has patch: unset
Keywords: ALTER TABLE added
Summary: [schema-evolution] merge the schema-evolution branch into trunkProvide the ability to update database to reflect changes in model definitions (i.e., schema evolution)
Triage Stage: UnreviewedAccepted
Version: other branchSVN

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.

Note: See TracTickets for help on using tickets.
Back to Top