On 4/19/07, Gábor Farkas <[EMAIL PROTECTED]> wrote: > i do not want this. i'd like to find a way, > which TRIES to delete the object, and if not possible > (foreign-key-restrictions), then raises an exception.
This really isn't possible right now without doing a lot of hacking around; the problem is that Postgres is the only database which really supports referential integrity (MySQL has a table type that does it, but nobody seems to actually use that...), so you can't rely on the database to throw you an integrity error (that's why Django "manually" figures out which objects need to be deleted). Probably the best option would be to write a new method for the model you need this on, and call it something like "safe_delete"; look at the logic Django uses to find related objects which need to be deleted, replicate that, and if you find related objects have your "safe_delete" method raise an exception or otherwise kick back an error message to the user. This has the advantage of keeping the "real" delete method around for admin usage. -- "Bureaucrat Conrad, you are technically correct -- the best kind of correct." --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
