# Node-red unresponsive while sqlite node is working

**URL:** <https://discourse.nodered.org/t/node-red-unresponsive-while-sqlite-node-is-working/63465>\
**Category:** General\
**Created:** [4 June 2022 19:36 UTC](https://discourse.nodered.org/t/node-red-unresponsive-while-sqlite-node-is-working/63465 "2022-06-04T19:36:43Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![sonntam](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/sonntam/32/19423_2.png) [@sonntam](https://discourse.nodered.org/u/sonntam)\
**Post date:** [4 June 2022 21:18 UTC](https://discourse.nodered.org/t/node-red-unresponsive-while-sqlite-node-is-working/63465/2 "2022-06-04T21:18:39Z")

</div>

Well,... sometimes I can't stop tinkering. I implemented a custom `exec async` node that uses node.js `childProcess` and `stream` libraries to start a process and pipe text to its stdin.

This custom node is used in a custom `sqlite read async` node to spawn a niced (to decrease process priority) `sqlite3` cli process which opens a sqlite db with the `-readonly -json` flags.

This works quite nicely. Note that you have to have the `nice` and `sqlite3` programs on your path in order for this to work. The sqlite file path cannot contain `~` as the path is put in double quotes, but you can use the `$HOME` env variable.

[Gist for custom sqlite read async node.](https://gist.github.com/sonntam/7ea3226d2fc0b078c59130af7eb4b494)

---

_[View the full topic](https://discourse.nodered.org/t/node-red-unresponsive-while-sqlite-node-is-working/63465)._