This is probably just a useless side note, but in one Django project we actually successfully used the Rails migration system.
Erik On 16.10.2008, at 9:53, Bruce Kroeze wrote: > On Wed, Oct 15, 2008 at 8:58 AM, Erik Allik <[EMAIL PROTECTED]> wrote: > Here's the question: why not pick a schema evolution tool and use > that to avoid such problems? Obviously I'm not the only one having > these issues. Also, considering that Satchmo is quite a respectable > project in the world of Django, this would provide great feedback to > the community and Django core developers (and the authors of django- > evolution, dmigrations and south) as to what the schema migration > framework should be like once it lands in Django 1.x (hopefully not > later than 1.2). > > I would love to see us start using such a tool. I think the natural > time for it is right after we release 0.8. The problem is really > picking the right one for us. I tried to use django-evolution for > my Banjo project, but I just couldn't use it the way I wanted to. > The "all-or-nothing" philosophy ended up with me choosing to use > nothing instead of hacking around the pain. > > At Djangocon, I was really impressed by dbmigrations and south, but > at that time, they didn't seem ready for prime-time. For example, > one of 'em only worked with MySQL. Not acceptable for Satchmo, > obviously. Perhaps those problems are fixed by now. Does anyone on > the list have any real-world experience using those tools? > > Bruce > http://gosatchmo.com > > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Satchmo users" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/satchmo-users?hl=en -~----------~----~----~----~------~----~------~--~---
