Using an in-memory H2 database as a transient memory store for intermediate workflow results.
This doesn't require writing to file store and the data disappears when the workflow is reset
20 April 2021, @takbb Brian Bates
This is a companion discussion topic for the original entry at https://kni.me/w/vaCwqCPsqwQRi6cy
I really like this approach - thanks so much for sharing - and it would definitely prevent workflows looking like spaghetti with extremely long connectors all over the place!
I’ve a couple of questions if ok…
- I’m unfamiliar with H2 databases, are there any situations you wouldn’t use this approach? (ie. Table size too big, etc)
- What’s the purpose of the ‘Container Output (Table)’ node within this workflow?
Thanks in advance!