Make changes in models automatic

[patrick.lauber@…]

Don't just create a skeleton. Try to determine and then to write them in a new migration file.

with a wizard you could even ask if there where any renames

[andrew]

Yes, this is verging on django-evolution, and exactly what we're probably going to head towards as we discuss merging features from all three.

[amccurdy]

The startmigration command tries to cover common use cases for migration file generation. Currently, it covers the following use cases:

• Creating an "initial" file that generates creates for all objects syncdb would create.
• Creating a new table(s) with the --model option.

We'll also be adding a --field option for adding a field to an existing model, since that seems like a pretty common use case.

If you have a use case that isn't covered, and feel it's common, please let us know.

[andrew]

Closing this, as it's unlikely we'll write a model history tracker in the near future, and django-evolution does this well - no need to reinvent the wheel in that area.

[andrew]

Reopening! This feature is now made possible by the ORM Freezer, and so it will exist in a form at least as capable as django-evolution's in 0.5.

[andrew]

Closing this, as the essence of it is done.