What was the issue with DB Update node? As @AnotherFraudUser you need both columns (record_id and insert_date) in your table and should work as expected…
Thank you @ipazin and @AnotherFraudUser. Much appreciated. Maybe I’m misreading what DB Update node does but it seems to require a one to one mapping of the Knime data table column name to an Oracle DB column name. Is that correct? The other gap is that I do actually want to use the time from the Oracle host rather than the Knime client and insert the time that the record was actually updated. I’ve done this before with other similar tools and I’m trying to understand what the similar process looks like in Knime.
Yes you need to have an exact mapping.
If you want to have the ORACLE default value, then it would be more complicated to do that
How many values are you updating? a few hundred, thousand,million?
If it is just hundred then you could create the in statement though an groupby node.
If is is thousand/million rows I think even a loop would not be great…
Can you change the default value of your update table to DEFAULT CURRENT_TIMESTAMP? Then you would set the value direcly with the insert of new rows
But I am not sure if there is a pretty purely in KNIME solution