Forum Discussion
@Damone
do it all in SQL
ie
IF EXIST(Select id from table_x where id=@id)
BEGIN
UPDATE table_x set col1=@col1 where id=@id
END
ELSE
BEGIN
INSERT INTO into table_x (id,col1) values(@id,@col1)
END
Thank you. That is definitely useful and I will go that route going forward. In this instance, one important thing that I forgot to mention is that my source is Oracle DB, and my target and lookup tables are in SQL Server. So I am selecting from Oracle, checking a SS table to see if the attribute exists, and if not, then insert / update.
Hi,
I have tested a bit more. If I force an error in e.g. Mapper3 or LogMessage (see picture below), I see the child-error-pipeline getting executed fine. Only, when I force an error in JSON Formatter Snap, it fails with the error message mentioned in the initial post.
Is it a BUG or a FEATURE, that JSON Formatter does not call error pipeline properly? Are there other snaps with this FEATURE?I also noticed, that the child-error-pipeline only gets executed once, for all the errors in the pipeline, WOW-1!
What is more, even if errors occured in more snaps, pipeline gets executed further, and I see “Completed” status in the Dashboard, WOW-2! ← this probably is why, error pipeline gets executed only once. Is there a possibility to force the pipeline to stop on error and use error pipeline?cheers
Simon 🙂
Related Content
- 6 years ago
- 3 years ago
- 5 years ago