# Is saving flows (per tab) in database any easier in node-red 1.0?

**URL:** <https://discourse.nodered.org/t/is-saving-flows-per-tab-in-database-any-easier-in-node-red-1-0/15004>\
**Category:** General\
**Created:** [1 September 2019 16:15 UTC](https://discourse.nodered.org/t/is-saving-flows-per-tab-in-database-any-easier-in-node-red-1-0/15004 "2019-09-01T16:15:53Z")\
**Posts on this page:** 1\
**Showing post:** 8

<div class="post-metadata">

**Author:** ![abhutada](https://avatars.discourse-cdn.com/v4/letter/a/35a633/32.png) [@abhutada](https://discourse.nodered.org/u/abhutada)\
**Post date:** [21 July 2021 14:39 UTC](https://discourse.nodered.org/t/is-saving-flows-per-tab-in-database-any-easier-in-node-red-1-0/15004/8 "2021-07-21T14:39:51Z")

</div>

I tried the following 2 options.

> **[node-red-contrib-multi-flows-storage](https://www.npmjs.com/package/node-red-contrib-multi-flows-storage)**
>
> A Node-RED storage plugin that organize flows and subflows in folders as YAML or JSON for readability

> **[node-red-contrib-storagemodule-postgres](https://www.npmjs.com/package/node-red-contrib-storagemodule-postgres)**
>
> A module to provide Node-RED persistence using a postgres database instead of the default filesystem

The YAML solution (multi-flows) seems to be working closer to what I want - saving each flow in a separate YAML file.

However when using the postgres option, could not get too far:

- everything still stored in DB just as a single row
- cannot find reference to the tab created in the actual DB data  
Not sure if mongodb plugin works differently.  
[Saving flows into Database - #17 by knolleary](https://discourse.nodered.org/t/saving-flows-into-database/30549/17)

---

_[View the full topic](https://discourse.nodered.org/t/is-saving-flows-per-tab-in-database-any-easier-in-node-red-1-0/15004)._