When I use a named query transaction, but do not actually run any queries against it I receive an error. If I do the same thing using system.db.beginTransaction I do not get an error. Any ideas on how to get around this? txId = system.db.beginNamedQueryTransaction("myDatabaseConnection") system.…

If you’re going to omit the database argument (and use the project default database, which is perfectly fine), you’ll probably want to use keyword arguments. It is interpreting the first argument as the database connection name. Try: ... self.tx = system.db.beginNamedQueryTransaction(isolationLev…

Scratch all that. This works. Thank you. The documentation for system.db.beginNamedQueryTransaction - Ignition User Manual 8.0 - Ignition Documentation confused me a bit I guess. For example notice here system.db.runNamedQuery - Ignition User Manual 8.0 - Ignition Documentation If a parameter i…

I guess this issue is still in the backlog? WRT the workaround; if I run statements (and why wouldn't I? I mean that's why I'm wrapping this is a transaction), and set the attemptedQuery = True, shouldn't I expect to find my code re-raising the exception if both commit and close will generate java.…

I don't have an issue with this anymore (and have not since 8.1.17) but I don't know what you mean by attemptedQuery=True I don't see that as a kwarg in beginNamedQuery or anything related. What is your code?

[image] bkarabinchak.psi: I don't know what you mean by attemptedQuery=True It's just a flag that was used in kcollins1 post above.

Hello beautiful people, I had this issue a while ago and asked about it ( here ). @paul-griffith redirected me there. All in all, things got smoother and the error only ever appeared when a transaction was opened but there was nothing to commit. Which I fixed easily, by making sure not to open the t…

[image] pascal.fragnoud: and can't update. I'm not sure what to do now. Generally, that means you will simply have to put up with it. IA never backports fixes--it always takes an upgrade to get them.

I feel like there's a way to make it work satisfactorily. It works fine in most cases, there's just this one query set that makes it behave like that. And I believe this same query set used to work fine just last week... Also, my situation here seems to be a little different that the one discusse…

Not sure why you ran into an issue closing the transaction, I'm assuming you're not trying to close it twice or something like that. If everything committed just fine, you could probably catch anything that trips on the close and perhaps log it, but let your script continue on. Out of curiosity, wh…

I'm running the 2022-latest docker image, last updated about 3 weeks / 1month ago. The JDBC driver seems to be 4.2 [image] kcollins: I'm assuming you're not trying to close it twice or something like that No, I'm actually using a decorator to handle basic transaction stuff, so all my transa…

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

Ignition

Brandon_Peterson May 8, 2024, 9:22pm 29

Just wanted to post some good news to this thread in case anyone hasn't seen it yet. Looks like this issue will be solved in Ignition 8.1.40!