#5099: Provide the ability to update database to reflect changes in model
definitions (i.e., schema evolution)
----------------------------------------------------+-----------------------
Reporter: Derek Anderson <[EMAIL PROTECTED]> | Owner:
nobody
Status: new | Component:
Core framework
Version: SVN | Resolution:
Keywords: schema evolution feature ALTER TABLE | Stage:
Accepted
Has_patch: 0 | Needs_docs: 0
Needs_tests: 0 | Needs_better_patch: 0
----------------------------------------------------+-----------------------
Changes (by russellm):
* 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)
* version: other branch => SVN
* keywords: schema evolution feature => schema evolution feature ALTER
TABLE
* has_patch: 1 => 0
* stage: Unreviewed => Accepted
Old description:
> http://code.djangoproject.com/wiki/SchemaEvolutionDocumentation
>
> i want to make it clear i'm *not* advocating doing this immediately. for
> now, this is simply a place to submit patches for others who do not wish
> to export the full branch. (for example, if they have their own custom
> branch they're maintaining)
New description:
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.
Comment:
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.
--
Ticket URL: <http://code.djangoproject.com/ticket/5099#comment:5>
Django Code <http://code.djangoproject.com/>
The web framework for perfectionists with deadlines
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-updates?hl=en
-~----------~----~----~----~------~----~------~--~---
