[GODRIVER-96] Use insertion-ordered map in ops.Find Created: 27/Sep/17 Updated: 28/Oct/23 Resolved: 23/Feb/18 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | None |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Samuel Rossi (Inactive) | Assignee: | Samuel Rossi (Inactive) |
| Resolution: | Fixed | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Description |
|
Because `collection.FindOne()` allows the user to specify FindOptions, it's possible that a user could specify a limit other than 1. To ensure that the command has the correct semantics, we should change ops.Find to use an insertion-ordered map once it's implemented instead of a bson.D and ensure that the last option in the list has precedence. |
| Comments |
| Comment by Samuel Rossi (Inactive) [ 23/Feb/18 ] |
|
The introduction of the new BSON library has fixed this issue. |
| Comment by David Golden [ 25/Oct/17 ] |
|
Blocked pending implementation of higher-performance insertion ordered map |