in addition (or just using different words of what Anthony said) ONLY when
you are in the web2py env in an HTTP request, web2py automatically commits
at the end of a successul request and rolls back if some exceptions are
raised, to ensure that EVERY operation you did for a request gets treated
atomically.
If you are in the realm of scheduled task, or in a function or a module
executed in the web2py shell, or in a module that just uses pydal as a
package, you need to explicitely call commit() or rollback().
Think of the web2py HTTP request environment doing basically a big
try:
all your code
commit()
except:
rollback()
--
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.
