> Within the context of a web2py request, wouldn't there be two transactions > open (one for each database)? In that case, at least if the request results > in an error, both transactions would be rolled back. > > Anthony >
well, pydal isn't used only in web2py's context but even if it was, you'd be forced to call a commit() on the callback (or just before that) to ensure referential integrity when dealing with such scenario. This theoretically would enable handling the logic required to perform such a task feasible, but only in the case if it's the only operation in the whole function. A user can still put a commit() here and there in web2py, breaking the aforementioned "safety"... moreover, I don't certainly want a "something" commit()ting on my behalf under the hood, breaking my own app's integrity. -- 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.
