[SERVER-17023] Move call to runCommands() out of runQuery() Created: 23/Jan/15 Updated: 19/Sep/15 Resolved: 23/Mar/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | None |
| Fix Version/s: | 3.1.1 |
| Type: | Task | Priority: | Minor - P4 |
| Reporter: | David Storch | Assignee: | David Storch |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Backwards Compatibility: | Fully Compatible |
| Sprint: | Quint 3.1.0, Quint Iteration 3.1.1 |
| Participants: |
| Description |
|
Currently, all commands run through receivedQuery() => runQuery(). We should move the call to runCommands() up one level so that runQuery() and find.cpp are reserved for .find() operations. This way, code for .find() will not participate in the commands code path. |
| Comments |
| Comment by Githook User [ 23/Mar/15 ] |
|
Author: {u'username': u'dstorch', u'name': u'David Storch', u'email': u'david.storch@10gen.com'}Message: |