Just change an abstraction level and it still will do
Database node as whole to be functional needs:
- query
- query execution
- result based route (could be one or more outputs)
A lot of my use cases, this granular concept makes flow messy:
- functional node (query definition) gets name like db node (but point is just that there are two nodes to achieve one operation)
and hard to read:
- moreover a lot of ifs (function nodes) based on sql query result - ie. if (SELECT COUNT(*) == 0) then output 1 else output 2
I've pasted example here: