[DOCS-15381] [Server] Improve 6.0 compatibility notes for removal of legacy op codes to also mention getLastError Created: 31/May/22  Updated: 13/Nov/23  Resolved: 07/Jun/22

Status: Closed
Project: Documentation
Component/s: manual, Server
Affects Version/s: 6.0.0
Fix Version/s: 6.0.0, Server_Docs_20231030, Server_Docs_20231106, Server_Docs_20231105, Server_Docs_20231113

Type: Improvement Priority: Major - P3
Reporter: David Storch Assignee: Jeffrey Allen
Resolution: Fixed Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:
Days since reply: 1 year, 35 weeks, 1 day ago
Epic Link: DOCSP-19446

 Description   

I think we should improve the documentation at https://www.mongodb.com/docs/v6.0/release-notes/6.0-compatibility/#legacy-opcodes-removed to mention the getLastError command. This command was used by old drivers in conjunction with the legacy op codes for doing writes (OP_INSERT, OP_UPDATE, and OP_DELETE). As part of removing support for the legacy op codes in 5.1, we removed support for getLastError as well. It's worth mentioning this explicitly in the release notes.

Note that we did already document the removal of getLastError elsewhere, e.g. here: https://www.mongodb.com/docs/v6.0/reference/command/getLastError/



 Comments   
Comment by Githook User [ 07/Jun/22 ]

Author:

{'name': 'jeff-allen-mongo', 'email': 'jeffrey.allen@10gen.com', 'username': 'jeff-allen-mongo'}

Message: (DOCS-15381): update opcodes compatibility notes to mention getLastError (#1202)

  • (DOCS-15381): update opcodes compatibility notes to mention getLastError
  • address review feedback
  • address review feedback
  • formatting and edits
  • adjust highlighting
  • clarify distinction
  • OP_QUERY adjustments
  • more adjustments
  • bold
  • reordering
  • change title
  • remove period
  • remove commas
Generated at Thu Feb 08 08:12:44 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.