I do not think the issue with your code. The issue with corrupted data in database. You seem to have an integer that contains list data. Perhaps one of your fields was a "list:integer" or "list:reference" type and then you changed it to "integer" or "reference" type. You ended up with corrupted data in there. A "normal" database like postgresql would have warned you of something like this and prevent such migration. I assume you are using sqlite which does allow inconsistent data types. Try delete (or move) your database and see if you can reproduce the problem.
On Friday, 16 May 2014 16:27:20 UTC-5, LaDarrius Stewart wrote: > > I deleted previous post stating it was working it's not im tired... > > On Friday, May 16, 2014 3:28:49 PM UTC-5, LaDarrius Stewart wrote: >> >> Omitted quite a bit Anthony but I feel I included the valuable >> information. Considering minus the record value of the SQLFORM the >> functionality works as intended. >> > -- 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/d/optout.
