[DOCS-75] document all the long forms of commands for the sake of older drivers Created: 03/Nov/11 Updated: 08/Sep/12 Resolved: 08/Feb/12 |
|
| Status: | Closed |
| Project: | Documentation |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Task | Priority: | Major - P3 |
| Reporter: | Chris Westin | Assignee: | Sam Kleinman (Inactive) |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Participants: | |
| Days since reply: | 12 years, 2 weeks ago |
| Description |
|
It's not easy to find the long forms of commands for folks that need to know this because their driver of choice has not implemented shortcuts for all commands. Some of these don't appear to be documented at all, even though they must exist under the covers. For every command, we should give the long form (the db.runCommand( {...})) form on the page for the command. |
| Comments |
| Comment by Sam Kleinman (Inactive) [ 08/Feb/12 ] |
|
Marking resolved, as the new documents handle this form. Will close when new docs are published. |
| Comment by Sam Kleinman (Inactive) [ 03/Nov/11 ] |
|
In the documentation overhaul that I've been working on (e.g. "Docs 2.0") I use the db.runCommand() form. Note, that still is still very much in a draft status. A working copy of this draft is at: |
| Comment by Scott Hernandez (Inactive) [ 03/Nov/11 ] |
|
That is not the long form: db.runCommand(<cmd>) The docs include a page with all command and page describing how to run any of those commands: We also tag command pages with label so they can easily be found/listed. What is missing here? |