aerospike 5.7.0 → 5.9.0

package/README.md

@@ -11,15 +11,14 @@
 
 The Aerospike Node.js client is a Node.js add-on module, written using V8.
 
-The client is compatible with Node.js 20 (LTS), 19, 18 (LTS), 16 (LTS).
+The client is compatible with Node.js 20 (Upcoming LTS) and 18 (LTS).
 It supports the following operating systems:
 - RHEL 8/9
-- Debian 10 (x86_64 architecture only)
 - Debian 11
 - Amazon Linux 2023
 - Ubuntu 20.04/22.04 (Focal Fossa, Jammy Jellyfish)
 - Many Linux distributions compatible with one of the above OS releases.
-- macOS versions 11/12/13 are also supported. (Node.js 14 install unavailable on M1 Mac systems)
+- macOS 12/13
 
 The client is compatible with arm64, aarch64, and x86_64 architectures.
 
@@ -301,7 +300,7 @@ const Aerospike = require('aerospike')
 Access the client API documentation at:
 [https://docs.aerospike.com/apidocs/nodejs](https://docs.aerospike.com/apidocs/nodejs).
 This documentation is built from the client's source using [JSDocs
-v3](http://usejsdoc.org/index.html) for every release.
+v4](https://www.npmjs.com/package/jsdoc) for every release.
 
 The API docs also contain a few basic tutorials:
 

package/aerospike-client-c.ini

@@ -1,3 +1,3 @@
 
 # Version number of the dependencies package for C client (Windows only)
-AEROSPIKE_C_DEPS_VERSION=1.0.1
+AEROSPIKE_C_DEPS_VERSION=1.0.2

package/aerospike-client-c.sha256

@@ -1 +1 @@
-3ef446436aa0b97dc952ab5f90141f7e2c7ff8254d545edb82654e490189d80a  aerospike-client-c-dependencies.1.0.1.zip
+BB7AEB63571E63FD6C9CD042DC1810743DF9C8F122C91EAFB705C2E08B87733A  aerospike-client-c-dependencies.1.0.2.zip

package/binding.gyp

@@ -145,6 +145,8 @@
         'src/main/enums/exp_enum.cc',
         'src/main/enums/batch_type.cc',
         'src/main/enums/privilege_code.cc',
+        'src/main/enums/exp_read_flags.cc',
+        'src/main/enums/exp_write_flags.cc',
         'src/main/stats.cc',
         'src/main/util/conversions.cc',
         'src/main/util/conversions_batch.cc',

package/lib/aerospike.js

@@ -264,6 +264,14 @@ exports.Key = require('./key')
  */
 exports.Record = require('./record')
 
+/**
+ * In the Aerospike database, each record (similar to a row in a relational database) stores
+ * data using one or more bins (like columns in a relational database).
+ *
+ * @summary {@link Bin} class
+ */
+exports.Bin = require('./bin')
+
 // ========================================================================
 // Enumerations
 // ========================================================================

package/lib/bin.js

@@ -0,0 +1,59 @@
+// *****************************************************************************
+// Copyright 2023 Aerospike, Inc.
+//
+// Licensed under the Apache License, Version 2.0 (the "License")
+// you may not use this file except in compliance with the License.
+// You may obtain a copy of the License at
+//
+//     http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+// *****************************************************************************
+
+'use strict'
+
+/**
+ * @class Bin
+ * @classdesc Aerospike Bin
+ *
+ * In the Aerospike database, each record (similar to a row in a relational database) stores
+ * data using one or more bins (like columns in a relational database). The major difference
+ * between bins and RDBMS columns is that you don't need to define a schema. Each record can
+ * have multiple bins. Bins accept the data types listed {@link  https://docs.aerospike.com/apidocs/nodejs/#toc4__anchor|here}.
+ *
+ * For information about these data types and how bins support them, see {@link https://docs.aerospike.com/server/guide/data-types/scalar-data-types|this}.
+ *
+ * Although the bin for a given record or object must be typed, bins in different rows do not
+ * have to be the same type. There are some internal performance optimizations for single-bin namespaces.
+ *
+ * @summary Construct a new Aerospike Bin instance.
+ *
+ */
+class Bin {
+  /** @private */
+  constructor (name, value, mapOrder) {
+    /**
+     * Bin name.
+     *
+     * @member {String} Bin#name
+     */
+    this.name = name
+
+    /**
+     * Bin value.
+     *
+     * @member {Any} Bin#value
+     */
+    if (mapOrder === 1) {
+      this.value = new Map(Object.entries(value))
+    } else {
+      this.value = value
+    }
+  }
+}
+
+module.exports = Bin