mg-dbx - npm Package Compare versions

Comparing version 2.0.16 to 2.1.17

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.16",
		"version": "2.1.17",
		"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>
		8 July 2020, M/Gateway Developments Ltd [http://www.mgateway.com](http://www.mgateway.com)
		1 August 2020, M/Gateway Developments Ltd [http://www.mgateway.com](http://www.mgateway.com)

		@@ -24,2 +24,3 @@ * Verified to work with Node.js v8 to v14.
		* [Using Node.js/V8 worker threads](#Threads)
		* [The Event Log](#EventLog)
		* [License](#License)
		@@ -945,3 +946,33 @@

		## <a name="EventLog"></a> The Event Log

		mg\-dbx provides an Event Log facility for recording errors in a physical file and, as an aid to debugging, recording the mg\-dbx functions called by the application. This Log facility can also be used by Node.js applications.

		To use this facility, the Event Log file must be specified using the following function:


		db.setloglevel(<log_file>, <Log_level>, <log_filter>);

		Where:

		* log\_file: The name (and path to) the log file you wish to use. The default is c:/temp/mg-dbx.log (or /tmp/mg-dbx.log under UNIX).
		* log\_level: A set of characters to include one or more of the following:
		* e - Log error conditions.
		* f - Log all mg\-dbx function calls (function name and arguments).
		* t - Log the request data buffers to be transmitted from mg\-dbx to the DB Server.
		* log\_filter: A comma-separated list of functions that you wish the log directive to be active for. This should be left empty to activate the log for all functions.

		Examples:

		db.setloglevel("c:/temp/mg-dbx.log", "e", "");
		db.setloglevel("/tmp/mg-dbx.log", "ft", "dbx::set,mglobal::set,mcursor::execute");

		Node.js applications can write their own messages to the Event Log using the following function:

		db.logmessage(<message>, <title>);

		Logging can be switched off by calling the setloglevel function without specifying a log level. For example:

		db.setloglevel("c:/temp/mg-dbx.log");

		## <a name="License"></a> License
		@@ -1051,1 +1082,7 @@

		### v2.1.17 (1 August 2020)

		* Introduce a log facility to record error conditions and run-time information to assist with debugging.
		* Change the default for the multihtreaded property to be true. This can be set to false (in the open() method) if you are sure that your application does not use Node.js/V8 threading and does not call mg\-dbx functionality asynchronously. If in doubt, it is safer to leave this property set to true.
		* A number of faults related to the use of mg\-dbx functionality in Node.js/v8 worker threads have been corrected. In particular, it was noticed that callback functions were not being fired correctly for some asynchronous invocations of mg\-dbx methods.

bin/winx64/node10/mg-dbx.node