Correctly handle $options when $regex is a regular expression

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Unresolved
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Query
    • None
    • None
    • None
    • None
    • None
    • None

      When $regex is given a regular expression, and $options are given, we run into an issue because our BSON regular expressions always have the m flag set and the server does not allow flags to be given in both the regexp argument to $regex and $options.

      As part of this ticket we may need to redesign how bson regular expressions handle their option arguments, which could go into bson 5 or 6.

              Assignee:
              Unassigned
              Reporter:
              Oleg Pudeyev (Inactive)
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: