bindata | BinData - Parsing Binary Data in Ruby | Serialization library

You can use go list with the -m flag and the -f flag like so:

The types that MongoDB server understands are listed in the documentation you found, https://docs.mongodb.com/manual/reference/bson-types/. The server does not understand and does not accept any other types.

Your application does not talk to the server directly but does that through a driver. The driver is responsible for converting basic types of your programming language to the bson types that the server understands. Sometimes this conversion is straightforward, sometimes it is not. For example, the only bson string type requires utf-8 encoding, which the driver may enforce on input strings. Similarly there are languages like Ruby and Python that contain a single integer type which can contain arbitrarily large values; the driver converts those values to one of two bson integer types (32-bit or 64-bit) or errors if the value is too big.

Basic language types generally do not include all of the types that are defined by the language's standard library (for example, the various collection types may be supported only to the extent that they provide automatic conversions to the basic language array or mapping).

Your driver, or other related libraries, may provide facilities for defining additional type conversions. For example, Mongoid does this via custom fields.

Consult your driver documentation for what type conversions are provided and how they work. Example for Ruby: https://docs.mongodb.com/ruby-driver/master/tutorials/bson-v4/#supported-classes

Strange how it could be. Anyway, you can find duplicate data with this aggregation pipeline:

I found the root cause why my search didn't use the sharding key. It's all about the collation.

Sharding key always use collation : { locale : "simple" } to do a binary comparison, while in my case my collection and indexes are designed to use "collation" : { "locale" : "en_US", "strength" : 2 }.

After redesigning my collection without any collation, now everything is fine.

Be aware that if your Realm model includes a List and that is a List of primitives, it's not well supported at this time (generally, avoid it).

EDIT: Release 10.7 added support for filters/queries as well as aggregate functions on primitives so the below info is no longer completely valid. However, it's still something to be aware of.

The List should be a List of Realm objects whose property is a String.

See the Relationship section of the documentation under the Lists Of Primitives section

Lists of primitives do not support lists-of-lists and querying

From the docs:

isMaster.passives

An array of strings in the format of "[hostname]:[port]" listing all members of the replica set which have a members[n].priority of 0.

This field only appears if there is at least one member with a members[n].priority of 0.

Those nodes have been set to priority 0 somehow, and will therefore never attempt to become primary.

and when I run cmake, I would like to

• compile each of subprograms
• generate shellcode from each of them, by running generate_shellcode program on them
• build main_program passing shellcodes from step 2

Then let's do that. Let's first write a short script to generate a header:

MongoDB comparison/sort order compares binary data in 3 steps:

1. First, the length or size of the data.
2. Then, by the BSON one-byte subtype.
3. Finally, by the data, performing a byte-by-byte comparison.

Since legacy and current UUIDs are the same length, you could search from the null UUID in type 3 to the null UUID in type 4, like:

Redis supports a kind of transactions. This fits exactly your needs.

All the commands in a transaction are serialized and executed sequentially. It can never happen that a request issued by another client is served in the middle of the execution of a Redis transaction. This guarantees that the commands are executed as a single isolated operation.

A Redis transaction is entered using the MULTI command. At this point the user can issue multiple commands. Instead of executing these commands, Redis will queue them. All the commands are executed once EXEC is called.

Pseudo Code: