[CXX-1101] collection::drop() throws exception when collection does not exist and connected to 3.0 mongod or earlier Created: 25/Oct/16 Updated: 26/Oct/16 Resolved: 25/Oct/16 |
|
| Status: | Closed |
| Project: | C++ Driver |
| Component/s: | Implementation |
| Affects Version/s: | None |
| Fix Version/s: | 3.0.3 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | J Rassi | Assignee: | J Rassi |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
When collection::drop() is invoked on a collection that does not exist, it is inconsistent about whether or not it throws operation_exception. Currently, it varies between server type and server version (an exception is not thrown when connected to mongod 3.2 or later or when connected to mongos, but an exception is thrown when connected to mongod versions 3.0 or earlier). collection::drop() should never throw an exception due to a missing collection. |
| Comments |
| Comment by Githook User [ 26/Oct/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'J. Rassi', u'email': u'rassi@10gen.com'}Message: |
| Comment by Githook User [ 25/Oct/16 ] |
|
Author: {u'username': u'jrassi', u'name': u'J. Rassi', u'email': u'rassi@10gen.com'}Message: |