> > I am still bemused that update_record can not know that it has failed and > return a result reflecting this. This is standard practice in computing. > Maybe this is just a weakness of sqlite I do not know. >
Well, we don't know where the failure is yet, so hard to say it is the fault of update_record. However, I agree that it might be useful if update_record provided some indication if no record gets updated (no reason to believe that would help in this particular case, though). Anyway, maybe replace your code with: db(db.transactions.token == request.vars.token).update(status='booked') If the problem persists, then at least we know the problem is not specifically with update_record. 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 web2py+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
