# Node-RED 0.20.0-beta.3 released

**URL:** <https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660>\
**Category:** News\
**Created:** [10 January 2019 14:27 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660 "2019-01-10T14:27:47Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![harsh](https://avatars.discourse-cdn.com/v4/letter/h/57b2e6/32.png) [@harsh](https://discourse.nodered.org/u/harsh)\
**Post date:** [21 January 2019 02:29 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660/21 "2019-01-21T02:29:56Z")

</div>

Closing the loop on this question, based on information gathered from Slack channel.

Each of the sub modules are not standalone executables. It isn't an initial goal of 0.20

---

<div class="post-metadata">

**Author:** ![tree-frog](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/tree-frog/32/89303_2.png) [@tree-frog](https://discourse.nodered.org/u/tree-frog)\
**Post date:** [26 January 2019 20:16 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660/23 "2019-01-26T20:16:38Z")

</div>

"node-red-contrib-mssql-plus", I thought was working fine until I upgraded to NR 20.0-beta.3. But I'm not sure if the 20.0-beta.3 is the problem. It's not exactly not working, but giving me an error when I click a button to pull data from a particular database. The one with the problem is MSSQL 2008-R2 and not another older database server which is 2002. The first flow gets data from the 2008R2 to get a part number then to pull data from a SKU parts table in 2002. The first queries work fine and the system gets back all it needs. The second attempt to update on a change yields an error "Object not found" citing the table name in the 2008R2 DB while the connection is still opened. Has anyone run into this with "node-red-contrib-mssql-plus"? Which MSSQL nodes are best? and does anyone have a favourite? Has anyone run into this sort of thing using the new beta.3? Thanks.

---

<div class="post-metadata">

**Author:** ![Colin](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/colin/32/17040_2.png) [@Colin](https://discourse.nodered.org/u/Colin)\
**Post date:** [26 January 2019 21:40 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660/24 "2019-01-26T21:40:11Z")

</div>

Show us the query you are running and the exact error message please. Assuming you are feeding the query in a message then put a debug node in to show the query.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [26 January 2019 21:43 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660/25 "2019-01-26T21:43:04Z")

</div>

@tree-frog please start a new topic on this. If it proves to be related to the Beta, then you can provide an update here. I don't want this topic to turn into debugging the mssql-plus node - its for feedback on the beta.

---

<div class="post-metadata">

**Author:** ![knolleary](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/knolleary/32/3_2.png) [@knolleary](https://discourse.nodered.org/u/knolleary)\
**Post date:** [6 February 2019 16:05 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660/26 "2019-02-06T16:05:42Z")

</div>

Hi @TotallyInformation

finally got around to looking at the duplicate context issue you mentioned.

I think this is probably expected behaviour, albeit slightly unfortunate.

You have configured two separate localfilesystem storage modules, but left them both to use the _same_ path as you don't provide a `base` directory setting to either. That means they use the same files on disk; writing to one will make the value appear in the other - albeit depending on your cache setting, it may not appear until a restart.

If you want to use multiple separate `localfilesystem` stores, you must give them different `base` settings. The default setting is `context` inside the user directory.

```auto
contextStorage: {
        default: {
            module: "localfilesystem"
            // this will use ~/.node-red/context/...
        },
        memory: {
            module:"memory"
        },
        file: {
            module: "localfilesystem",
            base: "another-context"
            // this will use ~/.node-red/another-context/...
        }
    },

```

I describe this as unfortunate as I suspect its all too easy to fall into this mistake without a careful reading of the docs. We should make it clearer.

---

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [6 February 2019 20:46 UTC](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660/27 "2019-02-06T20:46:47Z")

</div>

> [@knolleary](#):
>
> You have configured two separate localfilesystem storage modules

Doh! Not sure why I didn’t think of that really. I guess I was thinking that I’d set up two stores and chosen the default one of them rather than thinking of default as another store.

Thanks.

[Previous page](https://discourse.nodered.org/t/node-red-0-20-0-beta-3-released/6660.md?page=1)