Begin Transaction, problem with tx number java.util.map

[ryan.white]

@mdemaris

Project Library package?

Correct, its in the project at the top of our inheritance stack. We've also put stuff like pturmel's later.py, xml.py and queueUtil.py in there.

Edit, looks like this issue has been around a while? Found this:

[IGN-3829] Error executing system.db.commitTransaction

I had a similar problem when I was trying to set up an all or nothing write to our DB. What fixed it for me was the first query in the transaction (after getting the transaction ID) needed to have the project argument filled. Subsequent named query calls do not need that parameter filled. This worked: txID = system.db.beginNamedQueryTransaction(project="project1", database="database1") try: system.db.runNamedQuery(project="project1", path="query1", params=params1, tx=txID) #do some stu…

Also, if you are interested, a transaction decorator that automatically catches errors:

Script Benchmarking with Decorators Example

I made something similar to what you are aiming for but its also made for managing database transactions and errors in a standard way by creating a Response object that then I inspect after. import functools import timeit import traceback from forms2.structs import Response import java.lang.Throwable class handleTransaction(object): def __init__(self, logger): self.logger = logger def __call__(self, inner_func): """ We do 'tx' not in kwargs a few times here. If a fucntion has tx=None…