Skip to main content
Open

SQL Executor not waiting for result

Related products:Transformers
  • July 22, 2022
  • 1 reply
  • 31 views

johnt
Contributor
Forum|alt.badge.img+14

I know that it is intended for the SQL Executor to wait for the SQL result before moving on in a workspace, but in the case where I want to send a statement to refresh materialised views or trigger a function in Postgres, I only require it to wait 20 seconds or so to ensure there is no immediate error (like any missing dependent objects). Being deployed on FME Server, I do not want the workspace using up an engine for 2 hours while the database does it's thing. So an "Advanced" section with a tick box to tell it not to wait for the result, and an integer value for seconds to wait before moving on if a result is not returned in that time.

1 reply

johnt
Contributor
Forum|alt.badge.img+14
  • Author
  • Contributor
  • December 12, 2022

This can be deleted. I cannot find a way to delete it