Skip to main content
Archived

Add rejection port to the SQL FeatureWritter

Related products:FME Form
  • April 3, 2024
  • 1 reply
  • 61 views
gboquin
Contributor
Forum|alt.badge.img+8

Good afternoon,

I just experienced a situation that caused my workflow to stop because the source had a value that changed the datatype of a row. For instance, the table was expecting a date, but because the date was not formatted properly the SQL Writer thought that I was trying to pass a string into a date data type.

Another  case were this could have been useful is when my input has orphan records from a related table. the SQL writer had an issue because the source had  items that violated database relationships-- meaning there was a record that didnt  exist in the parent table.

These two scenarios were painful to diagnose and currently there is no work around for them with out having to build another tool from scratch.

Thanks for the help

    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

    LizAtSafe
    Safer
    Forum|alt.badge.img+21
    • LizAtSafeSafer
    • Safer
    • July 3, 2024
    Updated idea statusNew→Archived
    Idea merged into:

    All the votes from this idea have been transferred.

      Community Stats

      32,431
      Posts
      123,238
      Replies
      40,557
      Members
      Terms & ConditionsCookie settingsAccessibility statement
      A product of
      Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.