Order of SQLCreator
+40- Contributor
Best answer by takashi
As far as I know, there is no way to control the order of executing multiple SQLCreators. How about using multiple SQLExecutors in a series?
This screenshot illustrates my intention.
It may be an old question, an answered question, an implemented idea, or a notification-only post.
Please check post dates before relying on any information in a question or answer.
For follow-up or related questions, please post a new question or idea.
If there is a genuine update to be made, please contact us and request that the post is reopened.
- Best Answer
As far as I know, there is no way to control the order of executing multiple SQLCreators. How about using multiple SQLExecutors in a series?
This screenshot illustrates my intention.
+40- Contributor
Perhaps ugly but works certainly as expected.
If every SQL statement would be executed on the same database, alternatively, it's also possible to execute all the statements in the correct order with a single SQLCreator, and then filter the output features with the FeatureTypeFilter.
oops, "fme_feature_type" will not be set to the feature type name if you read the features with the SQLCreator/Executor, so the FeatureTypeFilter cannot be used. Need to consider other way to identify feature type.
As far as I've been able to tell, the SQLCreators are executed in their Z-order in the workspace. I've successfully been able to influence the execution order just by cutting and pasting the same SQLCreator back into the same workspace. Be sure to document whenever you do it though, it isn't exactly trivial to debug when some poor guy inherits your workspace ;-)
Safe has already registered an enhancement request for this. I suggest you contact them about this issue and ask to be associated with it. The more people on an enhancement request, the more likely it is to be implemented.
David
As far as I've been able to tell, the SQLCreators are executed in their Z-order in the workspace. I've successfully been able to influence the execution order just by cutting and pasting the same SQLCreator back into the same workspace. Be sure to document whenever you do it though, it isn't exactly trivial to debug when some poor guy inherits your workspace ;-)
Safe has already registered an enhancement request for this. I suggest you contact them about this issue and ask to be associated with it. The more people on an enhancement request, the more likely it is to be implemented.
David
It would be great if the user could control the execution order for all "starter" transformers such as Creator, SQLCreator, PythonCreator etc. If the order of them will be controllable, also hope a workspace parameter will be added, which determines which is run first, readers or the starter transformers.
It would be great if the user could control the execution order for all "starter" transformers such as Creator, SQLCreator, PythonCreator etc. If the order of them will be controllable, also hope a workspace parameter will be added, which determines which is run first, readers or the starter transformers.
I agree, that would be a great improvement. Feel free to add your name to the list of people waiting for this :-)
I agree, that would be a great improvement. Feel free to add your name to the list of people waiting for this :-)
OK, I'll post it as new idea here :)
