Code

Opened 7 years ago

Closed 6 years ago

#5099 closed (duplicate)

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

Reported by: Derek Anderson <public@…> Owned by: nobody
Component: Core (Other) Version: master
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: UI/UX:

Description (last modified by russellm)

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)

django_schema_evolution-SVN5821-patch.txt (87.5 KB) - added by Derek Anderson <public@…> 7 years ago.
patch against trunk/HEAD (current as of 5821)

Download all attachments as: .zip

Change History (7)

Changed 7 years ago by Derek Anderson <public@…>

patch against trunk/HEAD (current as of 5821)

comment:1 Changed 7 years ago by cheshire

  • Needs documentation unset
  • Needs tests unset
  • Patch needs improvement unset

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

comment:2 Changed 7 years ago by Simon G. <dev@…>

  • Summary changed from merge the schema-evolution branch into trunk to [schema-evolution] merge the schema-evolution branch into trunk
  • Version changed from SVN to other branch

comment:3 Changed 7 years ago by PhiR

  • Keywords feature added

comment:4 Changed 7 years ago by anonymous

  • Cc DXpublica@… added

comment:5 Changed 7 years ago by russellm

  • Description modified (diff)
  • Has patch unset
  • Keywords ALTER TABLE added
  • Summary changed from [schema-evolution] merge the schema-evolution branch into trunk to Provide the ability to update database to reflect changes in model definitions (i.e., schema evolution)
  • Triage Stage changed from Unreviewed to Accepted
  • Version changed from other branch to 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 Changed 6 years ago by jacob

  • Resolution set to duplicate
  • Status changed from new to closed

See #5934 -- it rounds up the existing options, and is a nice placeholder until we can get a best-of-breed merged in.

Add Comment

Modify Ticket

Change Properties
<Author field>
Action
as closed
as The resolution will be set. Next status will be 'closed'
The resolution will be deleted. Next status will be 'new'
Author


E-mail address and user name can be saved in the Preferences.

 
Note: See TracTickets for help on using tickets.