Database Looping - error handling?


I'm trying to use Database Looping to process a table of a couple of thousand records. The node chugs along for a while but, on record 775, generates an SQL exception.  The node then turns red and no data are available.

1) Can the good people who maintain this wonderful KNIME system take an enhancement request to make Database Looping resistent to errors?  How about returning a blank row or error message in such cases and leaving the results of successful queries on the remaining rows?

2) Have others come up with a clever work-around for this type of situation?



Hello Mitch,

we are curently working on an improved version for the database looper node which will have the option to handle sql errors gracefully. Have a look at the next release which is planned for July.