Move enforcement of non-negative and positive integer constraints to the grammar

XMLWordPrintableJSON

    • Type: Task
    • Resolution: Won't Do
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Query Optimization
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      For pipeline stages like $skip or $limit that take a numeric argument, there is a restriction that the argument is non-negative. This is currently done after parsing to the CST, but ideally should be enforced in the grammar rule itself.

            Assignee:
            [DO NOT USE] Backlog - Query Optimization
            Reporter:
            Nicholas Zolnierz
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: