Re: Handling IntegrityError on transaction middleware commit

On Fri, Nov 27, 2009 at 6:35 AM, Ryan <rfugger@gmail.com> wrote:

I realize that I should be validating my data before saving it, but
I'll admit I don't guard against every eventuality.  My question is,
should I be doing something in my code to prevent this kind of poor
exception handling, or should I file a bug against django?  I would
certainly prefer the whole server not to break when the transaction
commit fails for whatever reason -- it should rollback the transaction
and give a 500 error page.

I think there is already a ticket filed on this:

http://code.djangoproject.com/ticket/6094

Karen

 

--

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+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/django-users?hl=en.