Skip to main content
Archived

Improve on handling SQL statements

Related products:Transformers
  • January 28, 2018
  • 1 reply
  • 9 views

takashi
Celebrity

From this Q&A: Comments in END_SQL statements ?

FME ignores errors that occurred while executing a SQL statement if you added a single hyphen preceding the statement. As far as I know, this FME specific SQL syntax can be used anywhere you can set SQL statements in a workspace, but I'm afraid that many users don't know the syntax since it is documented only in the help on the SQLExecutor.
  1. It would be good if the Workbench Help would contain a section commonly describing how FME handles SQL statements set in a parameter, including the behavior on the hyphen.

  2. In addition, it would be better that FME could treat a line starting with two consecutive hyphens in a SQL script as a comment statement (see the question above).

This post is closed to further activity.
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.

1 reply

lifalin2016
Supporter
Forum|alt.badge.img+40
  • Supporter
  • February 21, 2018

Actually, the assumption that FME ignores errors, when commands are prepending with a dash, is not entirely true.

Even when I know that a command will fail (MS/SQL "Create Schema [MyDatedName]" called multiple times), and I prepend the command with a dash, it still (when it fails) gets logged as an error in the log file.

This is most irritating, as I assumed the dash would make FME ignore any errors - including not logging it as one. At least don't log it as an error, just as a warning.

I'm automatically checking all recent FME log files for errors, and this yields a false positive in that respect.