Yes, I remember there was a thread about output_record always not working. 
Here it works most of the time, but very occasionally fails.

Peter

On Monday, 1 June 2015 16:13:11 UTC+1, Ian Ryder wrote:
>
> I can't give specifics as I had to workaround it but I was having a 
> similar issue last week with update_record. I'm using it everywhere without 
> issue but one particular method wouldn't update and didn't show any 
> error...if I see it again I'll post up and not work around it (I was having 
> trouble posting to the board at the time and needed to move on with the 
> code). 
>
> I was 100% sure my code was fine and it was a solid fact the database 
> (MySQL in my case) wasn't getting what I was trying to write. _lastsql 
> didn't seem to have evidence of the update instruction either. Will see if 
> I can recreate now and post up the code..
>
> On Saturday, May 23, 2015 at 10:44:25 AM UTC+2, peter wrote:
>>
>> It is in a regular HTTP request. I actually somewhat later when someone 
>> turned up to a gig believing they had paid as they had a confirmation 
>> email, but the database still said pending.
>>
>> There is no way the database record could get reset to 'pending'.
>>  Execution must have passed through the 
>>
>>    transaction.status='booked'
>>     transaction.update_record
>>
>> lines in order for the email to have been sent out. So the only 
>> explanation seems to be that the update_record failed to carry out its 
>> task. Clearly this is disconcerting. 
>>
>> The ticketing system has been running for a couple of years now and I 
>> have not been aware of this happening before.
>>
>> Peter
>>
>>
>>

-- 
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/d/optout.

Reply via email to