Closed
Description
We should make our comparison and sorting of scalar values, arrays, and documents work the same way as in MongoDB (excluding values we don't support, like NaNs and nested arrays).
- Simplify array comparison, remove
[]CompareResult
#1449 - Move more query tests to compat tests #1450
- Implement document comparison #1521
- Remove
types.Incomparable
#1522 - Comparison with unset fields works incorrectly #1023
Compat newly discovered issues:
- Query
Find
does not return error on invalid value of$size
operator #1539 - No error on Find query using top level operator inside
$elemMatch
#1542 - Greater than comparison with array of integer returns unexpected result #1569
- Add numbers to Scalar datasets for
$mod
compat test #1577 - Move findOne projection tests to compat tests #1578
- Compat test fails when adding shareddata with array containing many different type #1607
- Fix sorting #1637
- comparison of documents without reflection;
- comparison of
[]
,[null]
arrays; - comparison of arrays with a different element order;
- comparison of arrays with a different element types;
- comparison of documents with missing fields and nulls;
- comparison of documents with different fields order;
- comparison of documents with different fields types;
- ascending and descending sorting:
- scalars;
- documents;
- arrays;
- check that changes are ported to
findAndModify
.
We might have some of that tested already, but we should check that, add missing tests, and fix bugs.
Metadata
Assignees
Projects
Status
Done