On 9/19/07, Kenneth Gonsalves <[EMAIL PROTECTED]> wrote: > > hi, > > was trying sqlreset after a long time. It does not do the drop and > create statements in the proper order:
It never has, and in its current form, it will be very difficult to fix. sqlreset operates on a per-app basis; however, many of the ordering and constraint problems run across apps, and there are some circular relationship problems that are very difficult to resolve in a clean fashion. Back when I was doing the fixture work I was an advocate for removing sqlreset. The decision was made to keep because it can occasionally be useful (when it works), and there isn't an alternative on offer at the moment. If/when we get a schema evolution implementation into core, I would personally expect to see the reset commands be deprecated. Of course, in the meantime, if anyone wants to put the time into resolving the myriad constraint issues that are involved in making sqlreset work, they should feel free to do so. However, it certainly isn't high on my list of priorities. In the meantime, you can always drop and rebuild the entire database, or fall back to raw SQL DROP TABLE statements, managed manually. 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 -~----------~----~----~----~------~----~------~--~---
