New version of GlobalsDB 2012
March 12 announced the release of the next version of the free NoSQL InterSystems DBMS - GlobalsDB v2012.296.
The new version has a .NET API interface, minor changes have been made and a number of bugs fixed.
The full English version of the document is available on the GlobalsDB.org website.
Download GlobalsDB .
Details under the cut.
This version implements the .NET interface to access GlobalsDB.
The interface is supported on Microsoft Windows OS in the following versions:
Globals .NET API online documentation.
The .NET Globals API is very similar to the Java Globals API, except for the following differences:
1. Methods in the .NET API are named in Pascal notation (for example, CreateNodeReference), and not in Camel, as in Java (createNodeReference).
2. There are no interfaces in Globals .NET API: NodeReference, Connection, ValueList and
GlobalsDirectory are implemented as public classes. In Java API, they were presented in the form of public interfaces. Thus, in the .NET API, you can inherit directly from these classes, and not from interface implementation classes (as in Java NodeReferenceImpl, for example). In this regard, in classes there are protected (protected) constructors.
3. Two elements that in Java API are methods, in .NET API are properties:
ValueList.Length and GlobalsException.ErrorCode (in Java, ValueList.length () and GlobalsException.getErrorCode (), respectively).
')
And just like in the Java API, multi-threaded connections are not supported in the .NET API. This means that one application can create only one connection to GlobalsDB in one of its threads. However, when working with Caché multi-threaded connections are possible (Java Extreme technology).
1. In the handling of connection errors, explicit text messages about operating system errors have been added.
2. A non-argument form of calling open () has appeared. In this case, the path to globals will be taken from the environment variables globalsRoot or GLOBALS_HOME for * nix and Windows systems, respectively.
Examples of open call:
3. Fixed the error that occurred during an asynchronous call to global_directory ().
4. The error of multiple open () calls has been fixed - now this situation is handled correctly.
5. The version () and about () methods in the new version work correctly in asynchronous mode.
Learn more about Node.JS + GlobalsDB .
1.In the documentation, an extended description has been added of the need to call the close () method when completing work with instances of the NodeReference, ValueList and GlobalsDirectory interfaces. The need to call close () prevents memory leaks that may occur when allocating memory for instances, since When calling JNI, native operating system code is used for memory reservation, which is not controlled by the Java garbage collector.
2. Correct processing of string-numbers in ValueList, stored as double or decimal numeric when reading from ValueList.
3. The error of processing the last ValueList element has been fixed, in the case when it is a nested ValueList with an element of zero length.
4. Solved the problem with Segfault when adding items to the ValueList
Below is a list of supported operating systems.
• Apple Mac OS X 10.6, 10.7 for x86-64
• Microsoft Windows XP Pro, Server 2003, Vista, Server 2008, 7 for x86-32
• Microsoft Windows Server 2003, Vista, Server 2008, 7 for x86-64
• Microsoft Windows Server 2008 Amazon EC2 for x86-64
• Red Hat Enterprise Linux 5, 6 Advanced Platform for x86-32
• Red Hat Enterprise Linux 5, 6 Advanced Platform for x86-64
• Red Hat Enterprise Linux 5 Amazon EC2 for x86-64
• SUSE Linux Enterprise Server 11 for x86-32
• SUSE Linux Enterprise Server 11 for x86-64
• SUSE Linux Enterprise Server 11 Amazon EC2 for x86-64
• Ubuntu 11.04 for x86-32 and x86-64
The new version has a .NET API interface, minor changes have been made and a number of bugs fixed.
The full English version of the document is available on the GlobalsDB.org website.
Download GlobalsDB .
Details under the cut.
1 Innovations
GlobalsDB .NET API
This version implements the .NET interface to access GlobalsDB.
The interface is supported on Microsoft Windows OS in the following versions:
- Windows Server 2008;
- Windows Vista;
- Windows 7;
- Windows 7 SP 1 for x86-32 & x86-64.
Globals .NET API online documentation.
The .NET Globals API is very similar to the Java Globals API, except for the following differences:
1. Methods in the .NET API are named in Pascal notation (for example, CreateNodeReference), and not in Camel, as in Java (createNodeReference).
2. There are no interfaces in Globals .NET API: NodeReference, Connection, ValueList and
GlobalsDirectory are implemented as public classes. In Java API, they were presented in the form of public interfaces. Thus, in the .NET API, you can inherit directly from these classes, and not from interface implementation classes (as in Java NodeReferenceImpl, for example). In this regard, in classes there are protected (protected) constructors.
3. Two elements that in Java API are methods, in .NET API are properties:
ValueList.Length and GlobalsException.ErrorCode (in Java, ValueList.length () and GlobalsException.getErrorCode (), respectively).
')
And just like in the Java API, multi-threaded connections are not supported in the .NET API. This means that one application can create only one connection to GlobalsDB in one of its threads. However, when working with Caché multi-threaded connections are possible (Java Extreme technology).
2 Changes and bug fixes
2.1 GlobalsDB + Node.js
1. In the handling of connection errors, explicit text messages about operating system errors have been added.
2. A non-argument form of calling open () has appeared. In this case, the path to globals will be taken from the environment variables globalsRoot or GLOBALS_HOME for * nix and Windows systems, respectively.
Examples of open call:
<code> user.open ({
path: "/ usr / mp / globalsdb / mgr",
username: "_SYSTEM",
password: "SYS",
namespace: "USER"});
user.open ({path: "/ usr / mp / globalsdb / mgr"});
user.open ("/ usr / mp / globalsdb / mgr");
user.open (); </ code> 3. Fixed the error that occurred during an asynchronous call to global_directory ().
4. The error of multiple open () calls has been fixed - now this situation is handled correctly.
5. The version () and about () methods in the new version work correctly in asynchronous mode.
Learn more about Node.JS + GlobalsDB .
2.2 GlobalsDB Java API
1.In the documentation, an extended description has been added of the need to call the close () method when completing work with instances of the NodeReference, ValueList and GlobalsDirectory interfaces. The need to call close () prevents memory leaks that may occur when allocating memory for instances, since When calling JNI, native operating system code is used for memory reservation, which is not controlled by the Java garbage collector.
2. Correct processing of string-numbers in ValueList, stored as double or decimal numeric when reading from ValueList.
3. The error of processing the last ValueList element has been fixed, in the case when it is a nested ValueList with an element of zero length.
4. Solved the problem with Segfault when adding items to the ValueList
3 Supported Platforms
Below is a list of supported operating systems.
• Apple Mac OS X 10.6, 10.7 for x86-64
• Microsoft Windows XP Pro, Server 2003, Vista, Server 2008, 7 for x86-32
• Microsoft Windows Server 2003, Vista, Server 2008, 7 for x86-64
• Microsoft Windows Server 2008 Amazon EC2 for x86-64
• Red Hat Enterprise Linux 5, 6 Advanced Platform for x86-32
• Red Hat Enterprise Linux 5, 6 Advanced Platform for x86-64
• Red Hat Enterprise Linux 5 Amazon EC2 for x86-64
• SUSE Linux Enterprise Server 11 for x86-32
• SUSE Linux Enterprise Server 11 for x86-64
• SUSE Linux Enterprise Server 11 Amazon EC2 for x86-64
• Ubuntu 11.04 for x86-32 and x86-64
Source: https://habr.com/ru/post/140583/
All Articles