Skip to main content
Question

Microsoft SQL Server Non-Spatial error handling

  • January 3, 2019
  • 1 reply
  • 11 views
G

I have noticed in FME 2018.0 and 2019b that the Microsoft SQL Server Non-Spatial writer only raises a warning when a feature is not written due to (for example) NULL value constraints.

Personally I think that an error should be raised in any situation where a feature is not written to the database.

Despite the warning, the workspace continuous normally and the feature even shows up in the features written summary.

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

G
  • gertjangj87
  • Author
  • 2 replies
  • January 3, 2019

I have made a quick solution in the form of a startup-script:

Community Stats

32,083
Posts
121,831
Replies
39,718
Members

Latest FME

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.