I have actually come across this error before, and although I have not looked at the code, last time it was because I was trying to set a non json serializable object to the db. Probably because of poor design, the error given is completely unrelated.