-
Type: Bug
-
Resolution: Done
-
Priority: Minor - P4
-
Affects Version/s: 2.0.41
-
Component/s: MongoDB 3.2
-
Empty show more show less
version: 2.0.42
>lib/collection.js
-------insertMany function-line 435: options is not filled with forceServerObjectId property from collection properties . (we need to explicitly add it to insertMany query options)
>>>> I fixed it by using self.s.db.options.forceServerObjectId instead of options.forceServerObjectId
------- insertDocuments function-line 613,: insertDocuments don't use forceServerObjectId option from collection properties.
>>>> I fixed it by adding a condition on self.s.db.options.forceServerObjectId
>lib/bulk/ordered.js
-------OrderedBulkOperation.prototype.raw - line 325/328/334: don't use forceServerObjectId from collection properties
>>>> I fixed it by using this.s.collection.s.db.options.forceServerObjectId!==true;
-------OrderedBulkOperation.prototype.insert-line 353:don't use forceServerObjectId from collection properties
>>>> I fixed it by using this.s.collection.s.db.options.forceServerObjectId!==true;
>lib/bulk/unordered.js
-------UnorderedBulkOperation.prototype.raw: line 374/377: don't use forceServerObjectId from collection properties
>>>> I fixed it by using this.s.collection.s.db.options.forceServerObjectId!==true;
-------UnorderedBulkOperation.prototype.insert: line 308: don't use forceServerObjectId from collection properties
>>>> I fixed it by using this.s.collection.s.db.options.forceServerObjectId!==true;