mg-dbx - npm Package Compare versions

Comparing version 2.1.17 to 2.1.18

unix/zmgsi.ci

package.json

		@@ -5,3 +5,3 @@ {
		"description": "High speed Synchronous and Asynchronous access to InterSystems Cache/IRIS and YottaDB from Node.js.",
		"version": "2.1.17",
		"version": "2.1.18",
		"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>
		1 August 2020, M/Gateway Developments Ltd [http://www.mgateway.com](http://www.mgateway.com)
		12 August 2020, M/Gateway Developments Ltd [http://www.mgateway.com](http://www.mgateway.com)

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

		Finally, add the following lines to the interface file (cm.ci in the example used in the db.open() method).
		Finally, add the following lines to the interface file (zmgsi.ci in the example used in the db.open() method).

		@@ -280,3 +280,3 @@ sqlemg: ydb_string_t * sqlemg^%zmgsis(I:ydb_string_t, I:ydb_string_t , I:ydb_string_t *)
		envvars = envvars + "ydb_routines=/root/.yottadb/r1.22_x86_64/o*(/root/.yottadb/r1.22_x86_64/r /root/.yottadb/r) /usr/local/lib/yottadb/r122/libyottadbutil.so\n"
		envvars = envvars + "ydb_ci=/usr/local/lib/yottadb/r122/cm.ci\n"
		envvars = envvars + "ydb_ci=/usr/local/lib/yottadb/r122/zmgsi.ci\n"
		envvars = envvars + "\n"
		@@ -788,2 +788,14 @@
		"sqlstate": "00000",
		"columns": [
		{
		"name": "Number",
		"type": "INTEGER"
		},
		"name": "Name",
		"type": "VARCHAR"
		},
		"name": "DateOfBirth",
		"type": "DATE"
		}
		]
		}
		@@ -1089,1 +1101,11 @@

		### v2.1.18 (12 August 2020)

		* Correct a fault that could lead to unpredictable behaviour and failures if more than one V8 worker thread concurrently requested a global directory listing.
		* For example: query = new cursor(db, {global: ""}, {globaldirectory: true});
		* For SQL SELECT queries, return the column names and their associated data types.
		* This metadata is presented as a columns array within the object returned from the SQL Execute method.
		* The columns array is created in SELECT order.
		* Attempt to capture Windows OS exceptions in the event log.
		* The default event log is c:\temp\mg-dbx.log under Windows and /tmp/mg-dbx.log under UNIX.

bin/winx64/node13/mg-dbx.node

bin/winx64/node8/mg-dbx.node

bin/winx64/node10/mg-dbx.node