On 2006-12-11, Victor Ng <[EMAIL PROTECTED]> wrote: > > I've got a rough version of schema evolution working now. > > The basic implementation is what the SoC project was trying to do.
[...] > I honestly think it's a *bad* solution to the problem. I've been > looking at sqlalchemy and the 'migrate' project : > > http://erosson.com/migrate/trac/ > > and it seems like it's a better solution for a couple reasons. > > Ways in which my schema evolution code sucks: > > 1) converting the database is done pretty much all automatically so > you don't really have a way to version control your schema changes Is this a departure from the Proposal in the wiki[1]? It says: "Introspection + migration This approach is a combination of Automatic db introspection and Automatically applied migration code -- one command produces a migration script, you tickle your version number, and the syncdb runs the migrations" Steve [1] http://code.djangoproject.com/wiki/SchemaEvolution --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Django users" group. To post to this group, send email to django-users@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-users?hl=en -~----------~----~----~----~------~----~------~--~---
