On Thursday, August 22, 2013 6:43:39 AM UTC+2, Ben Finney wrote: > > This could be done by having Django's database interface catch the > error, and chain a new exception from that one: >
Knowing the model alone is imo pretty useless since that's in the traceback anyways; also what you suggest has to happen way up higher the chain; otherwise model wouldn't be known… -- You received this message because you are subscribed to the Google Groups "Django developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to django-developers+unsubscr...@googlegroups.com. To post to this group, send email to django-developers@googlegroups.com. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
