Oh, wait, I see it is a keyed table with no auto-incrementing "id" field. 
In that case (as stated in the book), the .update_record() method is not 
available.

Actually, there is an integer "Id" field -- is it auto-incrementing? If so, 
change its field type from "integer" to "id", and remove the "primarykey" 
argument. In that case, .update_record() will be available.

Anthony

On Thursday, December 12, 2013 9:12:21 AM UTC-5, Anthony wrote:
>
> - cacheable=True **strips** from the Row object any "bells and whistles" 
>> to be able to cache it from an outside module (select(cache=True) does this 
>> by default) AND to leverage some speedups in case delete_record(), 
>> update_record() and automatic FK are not needed. It's ok, expected and 
>> documented that trying to do an update_record() on a Row fetched with 
>> cacheable=True will **not** work.
>>
>
> But the code has cacheable=False, so .update_record() should work, no?
>
> Anthony
>

-- 
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 [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to