You cannot post messages because only members can post, and you are not currently a member.
Description:
A forum for discussing the Django Evolution schema evolution framework.
|
|
|
Django Evolution 0.6.7 released
|
| |
Hi everyone, There's a new release of Django Evolution out. It's a small release with just one bug fix. Previously, an app (listed in INSTALLED_APPS) that didn't contain models would error out when installing a baseline evolution. Now we handle that case and just skip over such apps. This should help with apps... more »
|
|
|
Django Evolution 0.6.6 released
|
| |
Hey everyone, I put out a small Django Evolution release tonight. Changes: * Supports Django 1.4's timezone awareness when saving Version models. * Generates better sample evolutions, particularly when using third-party database models. Christian
|
|
|
Django Evolution 0.6.5 released
|
| |
Hi everyone, Django Evolution 0.6.5 was just released. Release notes: * Fixed the version association for baseline evolutions for apps. The new code for installing a baseline evolution for new apps in 0.6.4 was associating the wrong Version model with the Evolution. This doesn't appear to cause any real-world problems, but it does make it harder... more »
|
|
|
Django Evolution 0.6.4 released
|
| |
Hi everyone, I put out a release of Django Evolution 0.6.4 tonight. It has some unit test compatibility fixes for Django SVN, and installs a baseline evolution history for any new apps, preventing the problem where an up-to-date set of models for a new app would be installed on syncdb, followed by a failed... more »
|
|
|
Django Evolution 0.6.3 released
|
| |
Hey everyone, Django Evolution 0.6.3 is released, and fixes both a long-standing PostgreSQL bug with adding non-null fields with default values, and the multi-database support when the databases are of different backends. It's registered in PyPI, so you can just easy_install -U django_evolution. Let me know if you hit any problems.... more »
|
|
|
New Django models not taken into account
|
| |
Hello,
django-evolution is working fine and correctly detects modifications
on any model found in its signature, but what is the procedure for new
Django models?
When I add a new MyModel in models.py and then run a syncdb, Django
creates the new table but django-evolution does not seem to update its... more »
|
|
|
Django Evolution 0.5 released
|
| |
Hi everyone,
I just put out the first ever release of Django Evolution, which I
arbitrarily dubbed 0.5. It features compatibility with Django 1.2, which
from all my tests (unit tests and real-world production tests) works quite
well. I would love feedback from anyone who tries it with Django 1.2,... more »
|
|
|
Django 1.2 support has landed
|
| |
Hi everyone,
I just committed support for Django 1.2. From my initial tests (unit tests
for PostgreSQL, MySQL, SQLite and real-world migrations of Review Board from
old databases) it appears to work. It also retains Django 1.1 compatibility.
At this point, I'd like to ask people to give it a try with their databases... more »
|
|
|
A changing of the guard
|
| |
Hi all, This is a quick note to let you all know that I am formally stepping down as a project maintainer of Django Evolution. This shouldn't come as a surprise to anyone - there hasn't been any significant development work done on Evolution in over a year. My personal commitments and my work on Django core are absorbing all my... more »
|
|
|
Problem running evolution
|
| |
Hi I'm using evolution with python 2.6 and django 1.2.0 beta 1 When doing syncdb I get the following error message: AttributeError: 'module' object has no attribute 'EvolutionOperations' Is there a way around this problem? -Anton
|
|
|
