Figured it out - I was on the wrong track. It was something the user was typing in.
There is a field called "Year of birth", and the user was typing in date, month, year & ?? (e.g. "2909501950"). It passed the integer validator, but it is out of range for a postgresql integer. I guess I should implement my own integer validator? Thanks, Neil On Monday, 13 January 2014 18:10:43 UTC, Neil wrote: > > This doesn't seem to be the case: > > - I looked at the database, and the types match the definition in the > model > - I can't see how that would only cause problems for one user out of > thousands. > > Any other things I can check out? > > On Monday, 13 January 2014 14:21:55 UTC, Massimo Di Pierro wrote: >> >> DataError is not a web2py or a python error. It is an error from the >> driver. I suspect you have an "integer" field which you changed to >> "string". Web2py knows about the change but the database does not and >> refuses to store a string in it. Delete everything under "databases". You >> will lose data but you will have a clean migration. >> >> -- Resources: - http://web2py.com - http://web2py.com/book (Documentation) - http://github.com/web2py/web2py (Source code) - https://code.google.com/p/web2py/issues/list (Report Issues) --- You received this message because you are subscribed to the Google Groups "web2py-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
