Just a simple question to which I could not find the answer in the help of the node: does the sqlite node build a queue of the incoming requests? As there may be multiple concurrent listeners of the same sqlite db, it may easily lead to a conflict. So I was pondering if the sqlite node handles that situation itself or shall I build my own solution for it? My only problem is when I need to build it myself is that:
- subflows would come handy but they are instantiated so the number of listeners would be the same and they could still access the db concurrently.
- if I create a separate tab for the solution with a single sqlite node and the queueing logic around it, I'll need to use link nodes and take care about routing the output to the (one and only) appropriate tab back.