[SERVER-25954] Support more granular collation specification Created: 02/Sep/16 Updated: 26/Dec/23 |
|
| Status: | Backlog |
| Project: | Core Server |
| Component/s: | Querying |
| Affects Version/s: | 3.4.0 |
| Fix Version/s: | None |
| Type: | New Feature | Priority: | Major - P3 |
| Reporter: | Jeffrey Yemin | Assignee: | Backlog - Query Execution |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | read-only-views | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||||||||||||||||||||||
| Assigned Teams: |
Query Execution
|
||||||||||||||||||||||||
| Participants: | |||||||||||||||||||||||||
| Case: | (copied to CRM) | ||||||||||||||||||||||||
| Description |
|
Additional use cases for collation would be enabled if it could be specified at a more granular level than per-operation. Some examples:
|
| Comments |
| Comment by David Percy [ 11/Jun/21 ] |
Just to clarify, I think this ticket is proposing a way to avoid introducing those security leaks. We definitely don't want a view definition to change its meaning based on how you query it. If we could attach a collation to each stage separately, then a query specifying collation A, running on a view defined with collation B, could all run correctly (each stage using the appropriate collation). |
| Comment by Asya Kamsky [ 13/Sep/16 ] |
|
All of these except the last bullet are reasonable requests. The last bullet seems to enable some security leaks. |