On 4/11/06, Glenn Tenney <[EMAIL PROTECTED]> wrote: > > On Tue, Apr 11, 2006 at 05:01:39PM -0000, arthur debert wrote: > > more on this here: > > http://code.djangoproject.com/wiki/RemovingTheMagic#Addedamorepowerfulwayofoverridingmodelmethodsremovedhardcoded_pre_save_post_saveetc. > > > Everything that I read there shows that you can choose to save or > not-save, delete or not-delete, etc... which is fine, but I don't > think goes far enough. I wouldn't want attempts to > save/delete/insert/whatever to just not happen with everything else > seeming to be fine, and with no ability to get an error message of > some sort to the user. > > Shouldn't there be a way to signal that the save/delete/etc. did or > did not work ok? Either by raising an exception or by returning a > success / failure result...
You are free to raise your own exception in the path that fails to call super().delete() in M-R. -- --Max Battcher-- http://www.worldmaker.net/ All progress is based upon a universal innate desire on the part of every organism to live beyond its income. --Samuel Butler --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
