Uploaded image for project: 'Calcite'
  1. Calcite
  2. CALCITE-740

Redundant WHERE clause causes wrong result in MongoDB adapter

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: 1.2.0-incubating
    • Fix Version/s: 1.4.0-incubating
    • Component/s: None
    • Labels:
      None

      Description

      Running a query with the 'where' clause:
      where (pop > 8000 and pop > 9000)
      does not produce the same result as:
      where pop > 9000
      instead it produces the same result as:
      where pop > 8000

      This was run using calcite-mongo's zips collection.

      The interpreter appears to treat the 'and' as an 'or'. This despite the fact that queries like:
      where (pop > 8000 and pop < 9000)
      work as you would expect.

      Tried this on other data stores and did not see the same problem. Just calcite-mongo.

        Attachments

          Activity

            People

            • Assignee:
              julianhyde Julian Hyde
              Reporter:
              rantonucci Robert Antonucci
            • Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: