I've read (if it is correct) that at the end of a request without errors, 
the db is automatically committed by web2py.
Now, I have an xmlrpc function that should insert 2 records in a 
transaction.
If the second insert fails (for example for a syntax error in the query, or 
for a notnull constraint violated), the client receives an xmlrpc fault 
message but the first insert was committed!
Is it a web2py bug or I'm wrong?

-- 
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.

Reply via email to