On 11/27/07, Massimiliano Ravelli <[EMAIL PROTECTED]> wrote: > > On 25 Nov, 10:21, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > What is the recommended method to do this right now, what are you all > > using, just plain SQL? Basically, I'm looking for the best solution to > > this problem and would like to know what the community recommends. > > I can't raccomand you any of these but I can say that, after > a long waiting, I found the project *I* like and fits *my* needs: > Django Evolution. > > Here's some point about django evolution: > - good documentation > - clean and elegant (like django ;-) ) > - works with a recent version of trunk > - intergrates with django management without patching it > (thanks to the recent version of django itself) > - I can avoid to add information about evolution to my models > - helps to track and apply changes to the database.
Thanks for the compliments. I'm glad Django Evolution meets your needs. > I know: it can handle automatically only few case. > It doesn't support DeleteModel mutation... but I don't care: > I know a bit of sql and I can write a "DROP TABLE" statement. ;-) FYI - DE will support DeleteModel very soon. There is a prototype implementation attached to ticket #12; this patch requires a few minor tweaks before it is committed, but with any luck, I'll get a chance to put some time into this very soon. Yours, Russ Magee %-) --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
