[GODRIVER-798] URI options should have precedence over client options Created: 31/Jan/19 Updated: 27/Oct/23 Resolved: 12/Feb/19 |
|
| Status: | Closed |
| Project: | Go Driver |
| Component/s: | Options & Configuration |
| Affects Version/s: | None |
| Fix Version/s: | None |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | David Golden | Assignee: | Unassigned |
| Resolution: | Gone away | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Description |
|
Kris mentioned that URI does not have precedence, which is not consistent with the spec recommendation. The spec rationale for precedence order specifically notes that it's a recommendation not a requirement for back compatibility reasons. As a new driver, the Go driver should honor the spec recommendation to be consistent with compliant drivers. This will help TSE provide consistent answers to user questions. |
| Comments |
| Comment by Kristofer Brandow (Inactive) [ 12/Feb/19 ] |
|
Once |
| Comment by David Golden [ 04/Feb/19 ] |
|
If we think that's a good idea, I think it should be spec'd for all drivers. |
| Comment by Ian Whalen (Inactive) [ 04/Feb/19 ] |
|
plan to implement such that it's not URI by precedence but that users will get to specify ordering. |