METEOR: Expected not to find a document already present for an add error











up vote
0
down vote

favorite












I am using Meteor 1.8 and the error above is coming because I am using persistent-minimongo.



My use case for persistent minimongo is to use it not only for offline support but to also use it as cache for slow networks. Now the problem happens when user is online and loads the page, persistent-minimongo starts writing data from indexed-db(or similar browser storage) to minimongo while subscriptions too start writing to minimongo, in which case there is a conflict if persitent-minimono wrote any document first in minimongo and we receive the above error.



To fix this I have cloned mongo inside packages folder of my project and made changes to collection.js. Below is the part of the code which was throwing the above error.



    Object.assign(Mongo.Collection.prototype, {
_maybeSetUpReplication(name, {
_suppressSameNameError = false
}) {
....
....

update(msg) {
....
....

} else if (msg.msg === 'added') {
if (doc) {
throw new Error("Expected not to find a document already present for an add");
}
self._collection.insert({ _id: mongoId, ...msg.fields });*
}

...
...


I changed the above part of the code to not thorw an error as shown below.



else if (msg.msg === 'added') {
if (doc) {
self._collection.remove(mongoId)
}
self._collection.insert({ _id: mongoId, ...msg.fields });


Note: I do not want to make change to meteor core packages but I could not find any better solution.



The above change fixed my issue but I am a little worried about the repercussion of the above change. Want to understand as to why an error is thrown rather than replacing the document.



Any help would be appreciated. Thanks in advance!!










share|improve this question




























    up vote
    0
    down vote

    favorite












    I am using Meteor 1.8 and the error above is coming because I am using persistent-minimongo.



    My use case for persistent minimongo is to use it not only for offline support but to also use it as cache for slow networks. Now the problem happens when user is online and loads the page, persistent-minimongo starts writing data from indexed-db(or similar browser storage) to minimongo while subscriptions too start writing to minimongo, in which case there is a conflict if persitent-minimono wrote any document first in minimongo and we receive the above error.



    To fix this I have cloned mongo inside packages folder of my project and made changes to collection.js. Below is the part of the code which was throwing the above error.



        Object.assign(Mongo.Collection.prototype, {
    _maybeSetUpReplication(name, {
    _suppressSameNameError = false
    }) {
    ....
    ....

    update(msg) {
    ....
    ....

    } else if (msg.msg === 'added') {
    if (doc) {
    throw new Error("Expected not to find a document already present for an add");
    }
    self._collection.insert({ _id: mongoId, ...msg.fields });*
    }

    ...
    ...


    I changed the above part of the code to not thorw an error as shown below.



    else if (msg.msg === 'added') {
    if (doc) {
    self._collection.remove(mongoId)
    }
    self._collection.insert({ _id: mongoId, ...msg.fields });


    Note: I do not want to make change to meteor core packages but I could not find any better solution.



    The above change fixed my issue but I am a little worried about the repercussion of the above change. Want to understand as to why an error is thrown rather than replacing the document.



    Any help would be appreciated. Thanks in advance!!










    share|improve this question


























      up vote
      0
      down vote

      favorite









      up vote
      0
      down vote

      favorite











      I am using Meteor 1.8 and the error above is coming because I am using persistent-minimongo.



      My use case for persistent minimongo is to use it not only for offline support but to also use it as cache for slow networks. Now the problem happens when user is online and loads the page, persistent-minimongo starts writing data from indexed-db(or similar browser storage) to minimongo while subscriptions too start writing to minimongo, in which case there is a conflict if persitent-minimono wrote any document first in minimongo and we receive the above error.



      To fix this I have cloned mongo inside packages folder of my project and made changes to collection.js. Below is the part of the code which was throwing the above error.



          Object.assign(Mongo.Collection.prototype, {
      _maybeSetUpReplication(name, {
      _suppressSameNameError = false
      }) {
      ....
      ....

      update(msg) {
      ....
      ....

      } else if (msg.msg === 'added') {
      if (doc) {
      throw new Error("Expected not to find a document already present for an add");
      }
      self._collection.insert({ _id: mongoId, ...msg.fields });*
      }

      ...
      ...


      I changed the above part of the code to not thorw an error as shown below.



      else if (msg.msg === 'added') {
      if (doc) {
      self._collection.remove(mongoId)
      }
      self._collection.insert({ _id: mongoId, ...msg.fields });


      Note: I do not want to make change to meteor core packages but I could not find any better solution.



      The above change fixed my issue but I am a little worried about the repercussion of the above change. Want to understand as to why an error is thrown rather than replacing the document.



      Any help would be appreciated. Thanks in advance!!










      share|improve this question















      I am using Meteor 1.8 and the error above is coming because I am using persistent-minimongo.



      My use case for persistent minimongo is to use it not only for offline support but to also use it as cache for slow networks. Now the problem happens when user is online and loads the page, persistent-minimongo starts writing data from indexed-db(or similar browser storage) to minimongo while subscriptions too start writing to minimongo, in which case there is a conflict if persitent-minimono wrote any document first in minimongo and we receive the above error.



      To fix this I have cloned mongo inside packages folder of my project and made changes to collection.js. Below is the part of the code which was throwing the above error.



          Object.assign(Mongo.Collection.prototype, {
      _maybeSetUpReplication(name, {
      _suppressSameNameError = false
      }) {
      ....
      ....

      update(msg) {
      ....
      ....

      } else if (msg.msg === 'added') {
      if (doc) {
      throw new Error("Expected not to find a document already present for an add");
      }
      self._collection.insert({ _id: mongoId, ...msg.fields });*
      }

      ...
      ...


      I changed the above part of the code to not thorw an error as shown below.



      else if (msg.msg === 'added') {
      if (doc) {
      self._collection.remove(mongoId)
      }
      self._collection.insert({ _id: mongoId, ...msg.fields });


      Note: I do not want to make change to meteor core packages but I could not find any better solution.



      The above change fixed my issue but I am a little worried about the repercussion of the above change. Want to understand as to why an error is thrown rather than replacing the document.



      Any help would be appreciated. Thanks in advance!!







      meteor






      share|improve this question















      share|improve this question













      share|improve this question




      share|improve this question








      edited Nov 20 at 8:55

























      asked Nov 20 at 8:40









      abhima9yu

      435




      435





























          active

          oldest

          votes











          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389102%2fmeteor-expected-not-to-find-a-document-already-present-for-an-add-error%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown






























          active

          oldest

          votes













          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes
















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.





          Some of your past answers have not been well-received, and you're in danger of being blocked from answering.


          Please pay close attention to the following guidance:


          • Please be sure to answer the question. Provide details and share your research!

          But avoid



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53389102%2fmeteor-expected-not-to-find-a-document-already-present-for-an-add-error%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          Popular posts from this blog

          Wiesbaden

          Marschland

          Dieringhausen