[SERVER-3119] shell prompt is incorrectly changed after creating a new Mongo object Created: 19/May/11 Updated: 15/May/15 Resolved: 15/May/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Shell |
| Affects Version/s: | 1.8.1 |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Alvin Richards (Inactive) | Assignee: | Unassigned |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Fully Compatible | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
Problem: /local/mongo/bin/mongo The prompt is now reflecting the set and node connected through the new Mongo object, rather than the node its actually connected. Solution: Business Case:
|
| Comments |
| Comment by Daniel Pasette (Inactive) [ 15/May/15 ] |
|
this was fixed at some point after v1.8 |
| Comment by Alvin Richards (Inactive) [ 20/May/11 ] |
|
I would say that the prompt should reflect where the default commands go to. In this example if you execute db.foo.count() is executed against the node that your first connected to. To use the other connection you need to change syntax to do other.foo.count(); The prompt should reflect what the default db... is connect to. |
| Comment by Eliot Horowitz (Inactive) [ 20/May/11 ] |
|
unclear to me which is correct. |