ok, for the official status:
as mentioned earlier, yuri and i are joining forces on
introspection-driven schema evolution. and since automatic
introspection is so controversial (and obviously a poison pill for
acceptance into django-proper), we've rewriting it as an external library.
the project page is here:
http://code.google.com/p/deseb/
i expect a release in the next week or two.
the dreaded "aka" syntax will remain, but will require one additional
import statement to the top of your models.py. and management
integration will continue through the external command support recently
added into the trunk.
i agree with yuri that requiring users to write migrations in some new
django-specific SQL abstraction language is dumb, not DRYish and an
all-around pita. if you want that that's ok, but it's not the itch
we're scratching here. (*)
as soon as we have a working implementation, i will be stopping support
for the schema-evolution branch.
thanks,
derek
(*) however that's not to say wide-scale-production-deployment
management as a whole isn't necessary - we just see it as a separate
issue. and one compatible with this project. (output from sqlevolve
would be saved into whatever system you wish to use)
Yuri Baburov wrote:
>> I'm actually waiting for some code to be put up to
>> http://code.google.com/p/django-evolution/ - Russell (I'm pretty sure
>> it was him... we discussed it at the end of the sprint) has someone
>> who has been working on some code and I really want to see it before I
>> do any more work.
> You better name the project django-migration then and left
> django-evolution name for us ;)
>
>> I like Derek's take on model comparison using introspection, but
>> really think that it should be based on a migration system. I know
>> several Django developers agree with me on this (including Russell).
> Maybe you are not against introspection but against lack of migration system?
> I'm just don't want to make writing migrations by hands a necessary
> operation. For small projects it's a pita. It's equally dumb to
> manually fixing tables with sql. It's not DRYish.
> But I'm vote with strong +1 for possibility to write them with hands
> and correct them with hands.
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-developers@googlegroups.com
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/django-developers?hl=en
-~----------~----~----~----~------~----~------~--~---
