Named Queries VARCHAR Error

[Jack_Jones]

@pascal.fragnoud

Create a function in the script library, and call it from the event.

Does this not still use the tag threads? (not sure what the technical term is for them). When calling from the library it still takes the same amount of time whether it's defined outside and called or defined inside and called correct?

[Transistor]

My understanding is that the tag fires off the script from the library and lets go.

Phil has posted on this sort of issue many times. Here's one related post: Tag change script thread mode - #2 by pturmel.

[pturmel]

@Jack_Jones

Does this not still use the tag threads?

Yes. Calling a library function doesn't change what thread is running. It's just a library. If from a tag event, it is still using the limited thread pool. If from a gateway tag change event, it is still occupying that one dedicated thread.

[pturmel]

@Transistor

fires off the script from the library and lets go.

No. You might be confusing libraries with the technique I recommend in this topic:

Java concurrent queue for tag change scripts

Continuing the discussion from [SOLVED] Are tag Value Changed scripts running asynchronously?: We've got code in our standard library that I need to log a value change on a tag and then associate various data points with that value change. The value is located in a UDT, and because this is part of our "standard" library we use for our customers, the number of tags is variable and quite possibly numerous so having a gateway tag event script isn't feasible for this solution. I was reading up on …

Using queueUtil does push the work out of the tag event thread pool.

[pascal.fragnoud]

I'm not suggesting you call it from a tag script, but from the gateway event.
You shouldn't put too much code in a gateway event, or you'll run into weird scoping behavior. So write your script as a library function where you won't have those issues.