Details

    • Type: New Feature New Feature
    • Status: Open Open
    • Priority: Major - P3 Major - P3
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: planned but not scheduled
    • Component/s: Usability
    • Labels:
      None
    • # Replies:
      57
    • Last comment by Customer:
      true

      Description

      insert/update/remove/missing object

        Issue Links

          Activity

          Hide
          OptimusPrime
          added a comment -

          +1. Think that you have to check the XSD before inserting an JSON'ed XML document! I know you will say that I can do it in my application. But remember that may be I have only one Application Server but several MongoDB servers.
          And here is another reason:
          An application is constantly inserting data into MongoDB, and a seperate application is watching it live. How can second application know which rows inserted? Please don't tell me to use timestamp or something like that and make periodic queries.
          There is a whole bunch of examples out there which actually "need" triggers.

          Show
          OptimusPrime
          added a comment - +1. Think that you have to check the XSD before inserting an JSON'ed XML document! I know you will say that I can do it in my application. But remember that may be I have only one Application Server but several MongoDB servers. And here is another reason: An application is constantly inserting data into MongoDB, and a seperate application is watching it live. How can second application know which rows inserted? Please don't tell me to use timestamp or something like that and make periodic queries. There is a whole bunch of examples out there which actually "need" triggers.
          Hide
          Mark Waschkowski
          added a comment -

          Our company is soon needing this kind of functionality.

          Issues seen from previous comments, but not yet addressed:
          -delete's only show the oid (not anything else about the element that was deleted), so how can you create triggers around deletes? You would really need to know more about deletes to trigger from, and doing logical deletes is a time wasting work around
          -sharding, and having to worry about multiple oplogs
          -optimizations not available (search for 'interesting optimizations' from John Crenshaw)
          -oplog format isn't a portable solution (format may change in the future), so its really more of a hack than a real solution

          Eliot, do you really want the all the developers out there needed trigger functionality parsing the oplog? If so, fine, I'll write my own version of code to do so. If not, can you me know what would be required to move this forward? My company wouldn't be able to afford funding this alone, but would have funds to put towards this.

          Show
          Mark Waschkowski
          added a comment - Our company is soon needing this kind of functionality. Issues seen from previous comments, but not yet addressed: -delete's only show the oid (not anything else about the element that was deleted), so how can you create triggers around deletes? You would really need to know more about deletes to trigger from, and doing logical deletes is a time wasting work around -sharding, and having to worry about multiple oplogs -optimizations not available (search for 'interesting optimizations' from John Crenshaw) -oplog format isn't a portable solution (format may change in the future), so its really more of a hack than a real solution Eliot, do you really want the all the developers out there needed trigger functionality parsing the oplog? If so, fine, I'll write my own version of code to do so. If not, can you me know what would be required to move this forward? My company wouldn't be able to afford funding this alone, but would have funds to put towards this.
          Hide
          Flavius Aspra
          added a comment -

          This feature would be extremely useful, particularily if there would be a trigger when starting the daemon.

          Show
          Flavius Aspra
          added a comment - This feature would be extremely useful, particularily if there would be a trigger when starting the daemon.
          Hide
          Joel Sanderson
          added a comment -

          +1. I would like this feature to be able to maintain consistency of duplicate data across collections. Another usefulness would be able to execute some server-side JavaScript that would update a "view" as new data gets inserted/updated/deleted, similar to Couchbase views I believe.

          Show
          Joel Sanderson
          added a comment - +1. I would like this feature to be able to maintain consistency of duplicate data across collections. Another usefulness would be able to execute some server-side JavaScript that would update a "view" as new data gets inserted/updated/deleted, similar to Couchbase views I believe.
          Hide
          Vicary Archangel
          added a comment -

          +1 Server scripts (Node.js, Java and else) would definitely take advantage from this, saving enormous resources from polling, while page scripts (PHP, Ruby ... etc) doesn't really care as they make queries every single HTTP request.

          Show
          Vicary Archangel
          added a comment - +1 Server scripts (Node.js, Java and else) would definitely take advantage from this, saving enormous resources from polling, while page scripts (PHP, Ruby ... etc) doesn't really care as they make queries every single HTTP request.

            Dates

            • Created:
              Updated:
              Days since reply:
              35 weeks ago
              Date of 1st Reply: