Hello folks, First time trying to use transactions, and I can't figure out what I'm doing wrong. First, the basics: perspective 8.1.17 (requirement for this project) mssql 2022 20.04 I'm going mad I tried a bunch of things, but the smallest sample I could get that raises the same error is this: …

I don't know that this is causing this issue, but normally you either commit or rollback the transaction before closing it. I wonder if that is at play at all. I also don't see where you are setting the isolationLevel though that shouldn't matter actually.

This is a bug, I think. Look for a thread with the same script call and a response from Kevin Collins.

[image] [IGN-3829] Error executing system.db.commitTransaction Ignition 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 ho…

Yea I remember this post. I just tried your script in 8.1.17 and it does give me the same issue just like you had @pascal.fragnoud . However, I also just tried it in 8.1.26 and had no issue. If you can upgrade that's probably your easiest solution.

Sadly, I can't. [image] pascal.fragnoud: perspective 8.1.17 (requirement for this project) @paul-griffith Well... let's see if I understand the bug correctly: A transaction is not actually opened when using 'beginNamedQueryTransaction', but put on a queue until a query is actually made. So,…

I'm a bit confused about something. Does using transaction make system.db.runNamedQuery run on the gateway scope ? The calls to that function fail with "project 'path/to/namedquery' does not exist". The project name is not part of the function parameters when in perspective scope. I call it from a …

I remember when I was using .17, although the path is documented as a necessary argument, I had to use a keyword argument like you said path='somePath' to make things work. I was confused by it too. The upgrade from .17 to .26 is free if that makes any difference. If transactions are going to be …

I can't upgrade. I could ask the customer to do it, but I already know they won't. They have to send analysts and architects and maybe even a priest before they upgrade things, so it's not something they do on a regular basis. Actually, I don't have access to the gateway machine at all. I can't …

What if you provide the project name and path as kwargs? Or args? The error does imply that its taking your first arg as the project name project not found: families/create Personally I would tell them to call the priest because this bug is demonic imo.

My point is, that the test query doesn't require naming parameters, but the other one does. I can't make sense of it !

system.db.closeTransaction error (caused by: transaction closed)

Ignition

paul-griffith May 11, 2023, 5:29pm 4