On Tue, Sep 16, 2008 at 11:03 AM, akonsu <[EMAIL PROTECTED]> wrote: > > hello, > > on pgsql 'reset auth' fails with an error saying that it cannot drop > one of the tables (i do not remember which though) because other > objects depend on it. on sqlite it works fine. i did not try it on > mysql.
This isn't surprising. Postgres has referential integrity. SQLite doesn't have any referential integrity. MySQL only has referential integrity if you're using InnoDB tables. The reset command is problematic when you have referential integrity, because you can have all sorts of circular dependencies in your data which the constraints can trip over. It isn't a problem that can be easily fixed, either. Untangling the web of potential constraints is a hard problem. As a result of these complications, I've long been an advocate for removing the reset command entirely. However, this isn't really feasible until there is a comprehensive schema evolution solution available. The discussions that happened at DjangoCon lead me to believe that we're not that far off this becoming a reality. If you're looking to do a cleanup of your database, you may find that flush is a better option. This operates on an entire database rather than a single application, but if you're looking to delete all your tables and start fresh, it will always work. 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 [email protected] 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 -~----------~----~----~----~------~----~------~--~---
