[DRIVERS-192] Error message changed for command not found Created: 14/Nov/14  Updated: 15/Apr/19  Resolved: 22/Jan/16

Status: Closed
Project: Drivers
Component/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: David Golden Assignee: Barrie Segal
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
depends on CXX-513 Ensure we don't depend on the "no suc... Closed
Related
Driver Compliance:
Key Status/Resolution FixVersion
CXX-513 Done legacy-1.0.1

 Description   

SERVER-14507 changed the error message from "no such cmd" to "no such command".

Tests/code that check for the error string should look for error code 59 instead, as in this change to server tests: https://github.com/mongodb/mongo/commit/0b2aa4d52ed162d35a414afa215aea708f0cfd6a



 Comments   
Comment by Andrew Morrow (Inactive) [ 03/Mar/15 ]

Validating for C++11 since validated for C

Comment by A. Jesse Jiryu Davis [ 19/Nov/14 ]

PyMongo is good, it checks for codes 59, 13390, and none. There is one place it looks for "no such cmd", but it's specifically looking for "no such cmd: saslStart", which a new mongod won't return with the "cmd" or the "command" spelling.

Comment by David Golden [ 14/Nov/14 ]

Fixed in the Perl driver for both v0.x and v1.x branches.

Comment by David Golden [ 14/Nov/14 ]

However, the error message returned by mongos seems unaffected.

Generated at Thu Feb 08 08:20:58 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.