# SQLite - Add support for mustache in fixed statement

**URL:** <https://discourse.nodered.org/t/sqlite-add-support-for-mustache-in-fixed-statement/2572>\
**Category:** Feature Requests\
**Created:** [26 August 2018 08:33 UTC](https://discourse.nodered.org/t/sqlite-add-support-for-mustache-in-fixed-statement/2572 "2018-08-26T08:33:53Z")\
**Posts on this page:** 1\
**Showing post:** 3

<div class="post-metadata">

**Author:** ![tmdoit](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tmdoit/32/18441_2.png) [@tmdoit](https://discourse.nodered.org/u/tmdoit)\
**Post date:** [26 August 2018 14:45 UTC](https://discourse.nodered.org/t/sqlite-add-support-for-mustache-in-fixed-statement/2572/3 "2018-08-26T14:45:56Z")

</div>

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:

> [@SQLite - Add (function) editor to node](https://discourse.nodered.org/t/sqlite-add-function-editor-to-node/2576/7):
>
> I thought about what you said and think that product must evolve (as Church from Crusades to nowdays ;)) and meet market/use cases expectations to alive and expand. In described example above to Colin I've pointed out number of additional nodes. When working with db: you must set the query upon the result you will route the msg

---

_[View the full topic](https://discourse.nodered.org/t/sqlite-add-support-for-mustache-in-fixed-statement/2572)._