Django Evolution 0.7 is released

[Christian Hammond]

Hi everyone,

Django Evolution 0.7 is out. This release supports Django 1.4 through 1.6, and brings a lot of new additions and major performance enhancements:

* Database operations are now heavily optimized, minimizing the amount of ALTER TABLE statements that needs to be done when applying several related evolutions at once. There should now be one ALTER TABLE per table, instead of potentially one (or more!) per field mutation.

* Evolutions that result in no-ops are filtered out. For example, applying two evolutions at once, one which adds a field and another which removes it. This occurs within any evolutions being applied together when evolving the database.

* Evolution operations are also merged. For example, adding a column in an evolution and then renaming or changing the column in another will now simply add with the new name or changes. Like above, this applies only to evolutions being applied together.

* Added support for evolving `unique_together` and `index_together` meta properties on a model. If you have unique_together or index_together set for any existing models, you will need to add new baseline evolutions. (You won't have to delete these indexes in the database before applying, as Django Evolution is now smart about index.)

* Improved how Django Evolution works with indexes. If an index is renamed, or a new one is added that matches what an evolution would otherwise create, the evolutions will no longer break. Django Evolution will do the right thing with duplicate indexes and discovering index names.

* It's now easier to work with the codebase and run unit tests across different types of databases.

There's lots more. The release notes are up at:

http://downloads.reviewboard.org/releases/django-evolution/0.7/django_evolution-0.7.NEWS

Christian

--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org

Beanbag, Inc. - http://www.beanbaginc.com

[Christian Hammond]

Hi Robin,

Thanks! 

I'm happy to update the front page. As far as pip goes, though, I'm in strong disagreement with their recent change to assume all externally-hosted files are disallowed by default. There's analysis and logging we can do if we host it ourselves that we can't get through PyPI-hosted files.

There's some large discussions about this right now, and it sounds like there's much disagreement with what the pip authors have drafted for this. For the moment, I'm keeping things as-is, even though I know it's annoying to have to provide the --allow-* flags for this. I'll add some stuff to the front page on this.

For what it's worth, easy_install works just fine.

Christian

--
Christian Hammond - chi...@chipx86.com
Review Board - http://www.reviewboard.org

Beanbag, Inc. - http://www.beanbaginc.com

On Fri, May 16, 2014 at 9:37 AM, Robin Fordham <ging...@gmail.com> wrote:

On Tuesday, February 4, 2014 3:39:17 AM UTC, Christian Hammond wrote:

Hi everyone,

Django Evolution 0.7 is out. This release supports Django 1.4 through 1.6, and brings a lot of new additions and major performance enhancements

Hi Everyone,

Firstly many thanks for all the hard work with evolution, it is an excellent application!

If someone gets the chance please can version 0.7 be pushed to pip, it will make it a lot easier for user to get working with the latest version.

Also if someone could up update the front googlecode page to say it has migrated to github it would really help too.

Thanks again.

Regards,

Robin.