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... Or is that in M-R and I missed it...??? -- Glenn --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
