Uploaded image for project: 'Documentation'
  1. Documentation
  2. DOCS-12215

resetError deprecation status

    XMLWordPrintable

Details

    • Improvement
    • Status: Resolved
    • Trivial - P5
    • Resolution: Fixed
    • None
    • None
    • manual, Server
    • None

    Description

      Description

      This page: https://docs.mongodb.com/manual/reference/command/resetError/ does not mention that resetError is deprecated. https://docs.mongodb.com/manual/reference/method/db.resetError/#db.resetError says the db command is deprecated since 1.6.

      For comparison, https://docs.mongodb.com/manual/reference/command/getPrevError/ says it's deprecated since 3.6 and https://docs.mongodb.com/manual/reference/method/db.getPrevError/#db.getPrevError says it's deprecated since 1.6.

      Scope of changes

      Investigating whether resetError is actually deprecated in the same way as getPrevError. If so, mark what version to consider resetError as deprecated. 

       

        status
      ​ db.getPrevError
      • deprecated in 1.6 DOCS-142 with githubcommit
      • removed in 4.2 – SERVER-33226 (need to mark as docs needed  so that corresponding docs ticket generated ugh, because the  downstream flag is different from before with separate docs changes needed, will just manually link this ticket as Documents that ticket. ) ​
      getPrevError command
      db.resetError
      resetError command Will mark as deprecated without specifying since when.   

      Impact to Other Docs

      MVP (Work and Date)

      Resources (Scope or Design Docs, Invision, etc.)

      Attachments

        Issue Links

          Activity

            People

              kay.kim@mongodb.com Kay Kim (Inactive)
              oleg.pudeyev@mongodb.com Oleg Pudeyev (Inactive)
              Kay Kim Kay Kim (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:
                2 years, 42 weeks, 4 days ago