get_transaction().commit() stops execution
In my custom Zope Product (in python), get_transaction().commit() halts execution (without throwing an exception). Is this the proper behavior? If it is, then how do you commit what you've done so far without halting execution? And, if not, what would cause it to halt execution? Thank you in advance, Brian -------------------- Brian Rosenthal General Partner, RoboCommerce, LLC brian@robocommerce.com http://www.robocommerce.com 800-644-7626
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 zope-dev@rosenthaltechnologies.com wrote:
In my custom Zope Product (in python), get_transaction().commit() halts execution (without throwing an exception).
Is this the proper behavior?
Nope.
If it is, then how do you commit what you've done so far without halting execution?
The 'get_transaction' bit has been deprecated in recent versions of ZODB / Zope. The equivlaent non-deprecated spelling is:: import transaction transaction.commit()
And, if not, what would cause it to halt execution?
I've never seen such a thing. Is there anything at all in your logfiles which provdes a clue? If all else fails, you could set a breakpoint just before the 'commit' call and try stepping over /into it. Tres. - -- =================================================================== Tres Seaver +1 202-558-7113 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE/qva+gerLs4ltQ4RAjzjAKDLZT08oqS554CIh2gpWHwWzh2nVwCgxCmt VWs4x+VOV+zikJsYuel3tmE= =1WmK -----END PGP SIGNATURE-----
participants (2)
-
Tres Seaver -
zope-dev＠rosenthaltechnologies.com