mg-dbx - npm Package Compare versions

Comparing version 2.0.14 to 2.0.15

package.json

		@@ -5,3 +5,3 @@ {
		"description": "High speed Synchronous and Asynchronous access to InterSystems Cache/IRIS and YottaDB from Node.js.",
		"version": "2.0.14",
		"version": "2.0.15",
		"maintainers": "Chris Munt <cmunt@mgateway.com>",
		@@ -8,0 +8,0 @@ "homepage": "https://github.com/chrisemunt/mg-dbx",

README.md

		@@ -6,3 +6,3 @@ # mg-dbx
		Chris Munt <cmunt@mgateway.com>
		17 June 2020, M/Gateway Developments Ltd [http://www.mgateway.com](http://www.mgateway.com)
		22 June 2020, M/Gateway Developments Ltd [http://www.mgateway.com](http://www.mgateway.com)

		@@ -1033,3 +1033,3 @@ * Verified to work with Node.js v8 to v14.

		* Extend the processing of InterSystems Object References (orefs) to cater for instances of an object embedded as a property in other objects. For example, consider two classes Patient and Doctor where an instance of a Doctor may be embedded in a Patient record (On the Server: "Property MyDoctor As Doctor"). And on the Node.js side...
		* Extend the processing of InterSystems Object References (orefs) to cater for instances of an object embedded as a property in other objects. For example, consider two classes: Patient and Doctor where an instance of a Doctor may be embedded in a Patient record (On the Server: "Property MyDoctor As Doctor"). And on the Node.js side...

		@@ -1041,1 +1041,6 @@ var patient = db.classmethod("User.Patient", "%OpenId", patient_id);
		* Correct a fault in the processing of output values returned from YottaDB functions that led to output string values not being terminated correctly. The result being unexpected characters appended to function outputs.

		### v2.0.15 (22 June 2020)

		* Correct a fault that could lead to fatal error conditions when creating new JS objects in multithreaded Node.js applications (i.e. when using Node.js/V8 worker threads).

bin/winx64/node10/mg-dbx.node