It looks like what i was missing is that the SQLFORM will perform an insert or update depending on *its form name*, it wont matter if i explicit set a record id when before its processed.
If the submmited form name is mytable/create it will perform an insert, but i was passing an id that existed with the hope that it was smart enough to know i wanted an update. The problem with this is to render a writable table, each row needs a form with a name like "mytable/record_id" to perform updates. And at the controller create as many forms as rows in the table to process only the one it was submitted. This isnt optimal when you only want to process a single post. So what's left would be to trick sqlform name before its processed. Ill keep reading the book but this looks like a really odd way to distinguish between inserts and multiple updates. -- 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.
