[SERVER-660] ordering & nonsingularity of elemMatch and regex options shouldn't interfere with FieldRangeSet bounds Created: 23/Feb/10  Updated: 12/Jul/16  Resolved: 23/Feb/10

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: 1.3.3

Type: Bug Priority: Major - P3
Reporter: Aaron Staple Assignee: Aaron Staple
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Participants:

 Comments   
Comment by auto [ 24/Feb/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: Revert "SERVER-660 debug"

This reverts commit 439a43f876e40f357c2d263c3775a80e65e09cdf.
http://github.com/mongodb/mongo/commit/c0e6f059435869604765b4059e6188c9e5b2a357

Comment by auto [ 24/Feb/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-660 debug
http://github.com/mongodb/mongo/commit/439a43f876e40f357c2d263c3775a80e65e09cdf

Comment by auto [ 23/Feb/10 ]

Author:

{'login': 'astaple', 'name': 'Aaron', 'email': 'aaron@10gen.com'}

Message: SERVER-660 more flexible in terms of ordering and nonsingularity of elemMatch and regex
http://github.com/mongodb/mongo/commit/22ed9e154c2d28cdcd84ae4966a0b886b3ae89fd

Generated at Thu Feb 08 02:54:48 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.