Summary

Automatically call evolve during extension installation

Review Request #1674 — Created June 18, 2010 and discarded

Information

Owner

mike_conley

Repository

Djblets

Branch

extensions

Bugs

Depends On

Reviewers

Groups

django-evolution, djblets

People

Description

This review relies on:
http://reviews.reviewboard.org/r/1648/
http://reviews.reviewboard.org/r/1633/

If an extension has been updated, and the table schema has changed, we want to run django-evolution to migrate the database forward.

As stated above, for this patch, I'm relying on revision 3 of http://reviews.reviewboard.org/r/1633/ .  It's still not clear how django-evolution should be changed to support this type of programmatic invocation.  This is my first go at it - let me know if you have any ideas.

Testing Done

Manual.  Works just fine.

djblets/extensions/base.py (Diff revision 1)

In order to prevent any possibility of collision with the django_evolution package, I'd prefer to just name this "evolution".

Change Summary:

Switched django_evolution to just evolution as requested.

Diff:

Revision 2 (+4 -1)

Show changes

djblets/extensions/base.py

Ship it!

```
Just one small comment:
```

djblets/extensions/base.py (Diff revision 2)

Looks to me like it's not a TODO anymore.

Change Summary:

Thanks for the review!  Removed TODO.

Diff:

Revision 3 (+5 -2)

Show changes

djblets/extensions/base.py

Patch available here: http://github.com/mikeconley/djblets/commits/rr1674_automatically_call_evolve