Mongoose - Version Error: No matching document found for id

前端 未结 4 1833
眼角桃花
眼角桃花 2020-12-12 01:59

Context: I have a Post Mongoose model that contains a csv_files array field to store csv strings. I make a fetch API

相关标签:
4条回答
  • 2020-12-12 02:11

    just to comment here what my problem apparently was.

    Error Message:

    message: 'No matching document found for id "5c86d3a15bbcb965d85d80d1" version 3', name: 'VersionError', version: 3

    My code:

    update: function (data) {
    
            var session = new Session(data);
            database.logging("INFO", "session-update", session.cid, session.order.orderNumber);
            return new Promise(function (resolve, reject) {
    
                session.save()
                    .then(savedSession => resolve(savedSession))
                    .catch(savedSessionError => reject(savedSessionError))
            });
    
        }
    

    My parameter 'data' was already a Mongoose object and I was creating a new one and trying to save() it. So like @dacopenhagen said, save() checks the version of the document and it's throwing an VersionError error.

    How I fixed it Just removing the creation of the Session() object. Removed this line

    var session = new Session(data);
    

    I hope this help.

    0 讨论(0)
  • 2020-12-12 02:21

    I deleted version property from requests for update at body.

    delete req.body.__v;

    0 讨论(0)
  • 2020-12-12 02:22

    Looks like @robertklep was right. I fixed my issue by wrapping the first API call in a Promise and then executing the second API call after the first one completed.

    I'll wait to mark this as the answer just in case anyone comes across a better solution.

    0 讨论(0)
  • 2020-12-12 02:35

    When saving an object to Mongo DB you have to understand that Mongo DB has a version control system in place. This helps ensure that if you save an object once, when saving it again you don't end up overwriting the previously saved data.

    This is the error you're seeing. If you want to force the object to update regardless of version control in this particular instance you may want to use .update() instead. This will force the object to be updated regardless of its currently saved state.

    This is because .save() watches and cares about version controls, while .update() will update the object regardless of version control.

    0 讨论(0)
提交回复
热议问题