If you get this error, it's not your fault! This is a programming error and it should have been fixed by now. The programmers must have higher priority problems to work on or it's buried deep in the code. The error seems random which makes it hard to trace and correct.
Reminds me of the old days. I would get to work and the System Admin would be waiting for me with a 2" thick system dump print out. I would have to go through it to figure out what went wrong. It would end up being something simple like a user had entered an I (capital i) instead of a 1 (one) in a data entry field. Database wants a number and it gets a letter; bad! That's a type mismatch (TypeError). Anyhow, all you had to do was ask the programmer to add a couple of lines of code to check for it and it won't happen again.
