> > > Anyway, I don't want anyone to think that I complain as I don't have the > resources to write yet another migration tool and both South and Django > migrations beat writing SQL by hand. >
Have you tried Liquibase ever? It is very reliable, unfortunatelly it is missing automatic changesets generation (because models aren't tracked) and you must rewrite Django's and 3rd party apps migrations by yourself. I started this topic to talk about an improvement to the Django migrations, to provide some advantages known from Liquibase. Knowing LB may help everyone to understand my proposals. So the most important for me is a separation from an application layer to improve stability. The 2nd one is having a possibility to direct use of Django and 3rd party app migrations, to help everyone making upgrades. The 3rd one is a "dependency hell", where project-wide and flat files of sequences are easier to maintain, especially when project dependencies (i.e. 3rd party apps) are changing. They are very important for a long-term projects. Marcin -- You received this message because you are subscribed to the Google Groups "Django developers (Contributions to Django itself)" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/django-developers. To view this discussion on the web visit https://groups.google.com/d/msgid/django-developers/cf0e4d55-2df8-41cf-8779-c7281be54733%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
