Howto insert with document validation of type "long".

[drupal-daffie]

How do I insert data in a collection when the collection has a validation on it with for a particular column of the type "long". This is used for 64 bit integers. When I try to a large integer the response that I get is that the document validation failed. With other special columns you create first object and insert that object as the column value (Decimal128). Using the Int64 class is not possible, because the construct method is private. Has anybody have an idea/example how to fix my problem.

I am using: PHP 7.1 and version 1.4.2 of this project and MongoDB 3.6.

[derickr]

Can you share:

• the code, as short as possible, and something I could run without modification
• the validation schema, perhaps also explaining how you've configured this
• the exact error message

Decimal128 should generally only be used for very specific use cases.

Int64 is a class that is only used when reading data that is stored in MongoDB as a IntLong/64-bit integer on a 32-bit platform. Without an Int64 class wrapping the value, the data would end up being corrupt in that case. On 64-bit platforms, Int64 should never be generated for you when reading data.

[drupal-daffie]

$collection = (new MongoDB\Client)->test->test;

$insertOneResult = $collection->insertOne([
    'big_integer' => 223372036854775807,
]);

The validation level is strict.
The collection test has the following validation:

{ 
    "$and" : [
        {
            "big_integer" : {
                "$type" : "long"
            }
        },
        {
            "big_integer" : {
                "$exists" : true
            }
        }
    ]
}

The error message that I get is: "MongoDB\Driver\Exception\BulkWriteException: Document failed validation"

Hopefully this is enough. And thank you in advance for your help.

[derickr]

I have just tried this and it works on my 64-bit PHP compile. However, on a 32-bit PHP version it indeed shows the error that you get.

Can you run the following script for me, and reply with its output?

<?php
echo PHP_INT_SIZE, "\n";
var_dump( [
    'big_integer' => 223372036854775807,
]);

[drupal-daffie]

The result of running your code on my machine is:
"8 array(1) { ["big_integer"]=> int(223372036854775807) }"

[jmikola]

It looks like query expression validation is being used as opposed to a JSON schema. Looking at the $type query documentation, "int" and "long" are specific to 32-bit (BSON type 0x10) and 64-bit (0x12) integers, respectively. During BSON encoding, the PHP driver determines which BSON type to use based on the integer's value on 64-bit platforms. For 32-bit platforms, PHP integers would only ever be 32-bit values so we always encode as such (type 0x10).

Was the machine used in the most recent comment (to run @derickr's example script) the same as the environment where the validation exception was encountered? An alternative test to investigate this might be to have the original environment insert the same data into a separate collection (without validation) and examine the type that ends up inserted on the server side. The mongo shell could be used for that.

I'm not sure if the original intention of the validation was to require integers that are outside the range of 32-bit values. If not, and the intention was just to require an integer (as opposed to the "number" alias, which might allow floats), you could use $type: [ "int", "long" ] to make the validation more permissive.

---

Side note: I'm not sure if the JSON schema format differentiates between 32-bit and 64-bit integers, since the external numeric types documentation suggests there is a generic "integer" type, but MongoDB's own docs for $jsonSchema only refer to a "number" type that considers both integers and floats. I opened an internal ticket for MongoDB's docs team to look into that. It's probably not relevant to this issue but it's something I discovered while reading this so I felt compelled to share.

[drupal-daffie]

Yes, I am using query expression validation. I should have mentioned that.

Changing the validation from $type => "long" to $type => ["int", "long"] fixed my problem.
Thank you jmikola for your suggestion.

Integer values in the column are now stored as "Int32" for small integer values and as "Int64" for large integer values.
It was probably my OCD side that wanted to store all integer values in that column as "Int64".

I would like to thank both derickr and jmikola for their fast responce to my problem and their very expert help/suggestions.
I will now close this issue. If someone still would like to add something, please do.