On May 9, 5:33 pm, George Song <geo...@damacy.net> wrote:
> On 5/9/2009 7:14 AM, Rune Bromer wrote:
> > Hi,
>
> If you already did an override on `Payment.delete()`, then you should be
> fine.
>
> Although be mindful of bulk delete, as it doesn't use `Model.delete()`:
> <http://code.djangoproject.com/ticket/11022>
That's not a problem at all. I'll just remove the global delete action
and write my own. I was under the impression that all of the delete
functionality was not using the delete() method.
> Also you might want to think about setting up a group in auth to have
> finer grained permission control. It's pretty simple to just leave out
> delete for this specific model. Is there a reason they need to be
> superusers?
There is not. To be honest I'm also worried about myself :)
--~--~---------~--~----~------------~-------~--~----~
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
django-users+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/django-users?hl=en
-~----------~----~----~----~------~----~------~--~---
