From f95f0639f4a49d1731973c77352c911888ec43a3 Mon Sep 17 00:00:00 2001 From: Dave Conway-Jones Date: Fri, 11 Sep 2020 12:44:05 +0100 Subject: [PATCH 1/4] bump sqlite lib --- storage/sqlite/package.json | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/storage/sqlite/package.json b/storage/sqlite/package.json index 217db9eb..ed646689 100644 --- a/storage/sqlite/package.json +++ b/storage/sqlite/package.json @@ -1,9 +1,9 @@ { "name": "node-red-node-sqlite", - "version": "0.4.3", + "version": "0.4.4", "description": "A sqlite node for Node-RED", "dependencies": { - "sqlite3": "~4.1.1" + "sqlite3": "~4.2.0" }, "repository": { "type": "git", From 7e8571af423c0e688df0278af9391324aeb48c9f Mon Sep 17 00:00:00 2001 From: Dave Conway-Jones Date: Fri, 11 Sep 2020 22:21:52 +0100 Subject: [PATCH 2/4] update lib versions for grunt --- package.json | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/package.json b/package.json index 5cdd05a8..d4ae2196 100644 --- a/package.json +++ b/package.json @@ -33,22 +33,22 @@ "devDependencies": { "exif": "^0.6.0", "feedparser": "^2.2.10", - "grunt": "^1.1.0", + "grunt": "^1.3.0", "grunt-cli": "^1.3.2", "grunt-contrib-jshint": "^2.1.0", "grunt-jscs": "^3.0.1", "grunt-lint-inline": "^1.0.0", "grunt-simple-mocha": "^0.4.1", "imap": "^0.8.19", - "mailparser": "^2.7.7", + "mailparser": "^2.8.1", "markdown-it": "^11.0.0", "mocha": "~6.2.3", "msgpack-lite": "^0.1.26", "multilang-sentiment": "^1.2.0", "ngeohash": "^0.6.3", - "node-red": "^1.1.2", + "node-red": "^1.1.3", "node-red-node-test-helper": "~0.2.5", - "nodemailer": "^6.4.6", + "nodemailer": "^6.4.11", "poplib": "^0.1.7", "proxyquire": "^2.1.3", "pushbullet": "^2.4.0", From 4becf68848110f5bc2bb4eb5918cb6e75deb8417 Mon Sep 17 00:00:00 2001 From: Ross Cruickshank Date: Mon, 14 Sep 2020 17:21:41 +0100 Subject: [PATCH 3/4] use mongodb 3.6.1 client, add clustering support (#685) --- storage/mongodb/66-mongodb.html | 57 +++++++++++++------ storage/mongodb/66-mongodb.js | 46 ++++++++++++--- storage/mongodb/README.md | 14 ++++- storage/mongodb/locales/en-US/66-mongodb.json | 2 + storage/mongodb/package.json | 10 +++- 5 files changed, 101 insertions(+), 28 deletions(-) diff --git a/storage/mongodb/66-mongodb.html b/storage/mongodb/66-mongodb.html index f3180d65..05179a75 100644 --- a/storage/mongodb/66-mongodb.html +++ b/storage/mongodb/66-mongodb.html @@ -1,11 +1,24 @@ + @@ -90,20 +115,20 @@

Save will update an existing object or insert a new object if one does not already exist.

Insert will insert a new object.

Save and insert either store msg or msg.payload.

-

Update will modify an existing object or objects. The query to select objects to update uses msg.query, +

Update will modify an existing object or objects. The query to select objects to update uses msg.query and the update to the element uses msg.payload. If msg.query._id is a valid mongo ObjectId string it will be converted to an ObjectId type.

-

Update can add an object if it does not exist or update multiple objects.

+

Update can add a object if it does not exist or update multiple objects.

Remove will remove objects that match the query passed in on msg.payload. A blank query will delete all of the objects in the collection.

You can either set the collection method in the node config or on msg.collection. Setting it in the node will override msg.collection.

-

By default, MongoDB creates an _id property as the primary key, so repeated injections of the +

By default MongoDB creates an _id property as the primary key - so repeated injections of the same msg will result in many database entries.

-

If this is NOT the desired behaviour, i.e., you want repeated entries to overwrite, then you must set +

If this is NOT the desired behaviour - ie. you want repeated entries to overwrite, then you must set the msg._id property to be a constant by the use of a previous function node.

This could be a unique constant or you could create one based on some other msg property.

-

Currently we do not limit or cap the collection size, however this may well change.

+

Currently we do not limit or cap the collection size at all... this may well change.