[DOCS-728] Improve 2.2 release notes to help determine if driver upgrade is necessary in auth situation Created: 07/Nov/12 Updated: 30/Oct/23 Resolved: 07/Nov/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | dochub, manual |
| Affects Version/s: | mongodb-2.2 |
| Fix Version/s: | Server_Docs_20231030 |
| Type: | Improvement | Priority: | Major - P3 |
| Reporter: | sam.helman@10gen.com | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Participants: | |||||
| Days since reply: | 11 years, 15 weeks ago | ||||
| Description |
|
The 2.2 release notes on upgrading with auth enabled (see http://docs.mongodb.org/manual/release-notes/2.2/#synopsis) state that "you must upgrade the drivers before upgrading the mongod instance or instances", without further information on what determines if a driver upgrade is necessary. An upgrade is necessary if the current driver version always calls getLastError on the admin database, and this information is in the driver notes. The docs could be upgraded to recommend checking the driver notes to see if a driver upgrade is necessary. |
| Comments |
| Comment by auto [ 07/Nov/12 ] |
|
Author: {u'date': u'2012-11-07T21:14:41Z', u'email': u'samk@10gen.com', u'name': u'Sam Kleinman'}Message: |