On Wednesday, August 21, 2013 12:18:24 PM UTC+2, Anssi Kääriäinen wrote: > > Improvements to error messages are usually accepted. This idea, too, if > there is a way to actually do it without ugly hacks. >
I doubt there is a way to get that from the error message itself and I'll strongly object to adding logic like parsing the error message to figure that stuff out. Especially since the traceback is pretty clear and it's not as if one were searching through 5000 fields in a model… Also, this error is the result of putting data into the database without prior validation which is a bad idea anyways… -- 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 [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/django-developers. For more options, visit https://groups.google.com/groups/opt_out.
