[SERVER-7804] compareElementValues for CodeWScope is broken Created: 29/Nov/12 Updated: 23/Jan/15 Resolved: 09/Jan/15 |
|
| Status: | Closed |
| Project: | Core Server |
| Component/s: | Index Maintenance, Querying |
| Affects Version/s: | None |
| Fix Version/s: | 2.8.0-rc5 |
| Type: | Bug | Priority: | Major - P3 |
| Reporter: | Mathias Stearn | Assignee: | Mathias Stearn |
| Resolution: | Done | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Issue Links: |
|
||||
| Backwards Compatibility: | Minor Change | ||||
| Operating System: | ALL | ||||
| Participants: | |||||
| Description |
|
f = strcmp( l.codeWScopeScopeDataUnsafe() , r.codeWScopeScopeDataUnsafe() ); 1) codeWScopeScopeDataUnsafe is deprecated because it is broken Unfortunately this requires an index rev bump to fix since someone (probably mistakenly) might have indexed a field containing CodeWScope. |
| Comments |
| Comment by Githook User [ 07/Jan/15 ] |
|
Author: {u'username': u'RedBeard0531', u'name': u'Mathias Stearn', u'email': u'mathias@10gen.com'}Message: Make BSONObj::woCompare a total ordering Changes:
There should be no changes in any of the cases where woCompare defined a Related tickets:
Changes to the comparison function for aggregation will be handled separately |
| Comment by Mathias Stearn [ 29/Nov/12 ] |
|
Related: if we are going to change the compare order for CodeWScope, we should also give it the same canonicalType as Code so that a CodeWScope with an empty scope compares equal to a regular Code with the same text. |