On Sat, 2006-08-12 at 21:56 +0400, Ivan Sagalaev wrote: > 一首诗 wrote: > > But how can I give some information to user that the delete is not > > allowed? > > By the codes above, the user just see that the delete was done! > > This is exactly the case for using exceptions. Define your own exception > and raise it where user shouldn't delete an object. Then define a > middleware hook that will catch your exception and create some sensible > response for the user (403 Forbidden should fit).
This still isn't ideal, though. Because ideally you want to check this sort of thing as part of the validation of the form, so that you can seamlessly redirect the user back to the form with the errors filled in, just as for other form failures. The problem is that we do saving and deleting well after validation in the automatic manipulator flow. Now, yes, you can still do this with a bit of work in a custom view, but it is something that might become easier with model-aware validators/manipulators/whataver we end up calling them (since you can check it in context) and The Great Manipulator Rewrite of '06. Malcolm --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
