Icon

Inconsistent DB Error trapping

Workflow demonstrating that using In database nodes, the Try-Catch nodes appear to treat invalid SQL as configuration errors, whereas using DB Query Reader nodes, they treat it is a trappable execution error.

Node 18select from table that doesn't existdoesn't catch sql errorquick creation of a tableselect from table that doesn't existcatches sql errorreturns empty tablewe never get herewe get hereselect from table that DOES exist"return default table"we never get hereselect from table that DOES exist"return default table"we get hereH2 Connector DB Table Selector Try (VariablePorts) Catch Errors(Generic Ports) DB SQL Executor Try (VariablePorts) DB Query Reader Catch Errors(Data Ports) Java Edit Variable Java Edit Variable DB Table Selector DB Reader DB Query Reader String Manipulation Node 18select from table that doesn't existdoesn't catch sql errorquick creation of a tableselect from table that doesn't existcatches sql errorreturns empty tablewe never get herewe get hereselect from table that DOES exist"return default table"we never get hereselect from table that DOES exist"return default table"we get hereH2 Connector DB Table Selector Try (VariablePorts) Catch Errors(Generic Ports) DB SQL Executor Try (VariablePorts) DB Query Reader Catch Errors(Data Ports) Java Edit Variable Java Edit Variable DB Table Selector DB Reader DB Query Reader String Manipulation

Nodes

Extensions

Links

Download

To use this workflow in KNIME, download it from the below URL and open it in KNIME:

Download Workflow
Created by: bbate
Created at: 2023-11-04
On NodePit since: 2023-11-04
Last update: 2026-01-10
Created with KNIME version: v4.7.7

Deploy, schedule, execute, and monitor your KNIME workflows locally, in the cloud or on-premises – with our brand new NodePit Runner.

Try NodePit Runner!