foam-framework / foam-framework/foam

Query Optimizer bug when range selection used in combination with skip and limit

Open
#77 1 comment 0 reactions 1 assignee Claimed by @bshepherdson View on GitHub
bug imported
Dominant language
JavaScript
Stars
783
Forks
51
PR merge metrics
No merged PRs in 30d

Description

_From [k...@chromium.org](https://code.google.com/u/101260952816761938100/) on November 13, 2013 10:47:27_

Performing a range query on an MDAO (ie, when you specify either GT or GTE and LT or LTE) doesn't work properly when used with skip() and limit() because the range query is converted at the low-level to skip() and limit() calls, but this doesn't work properly if those setting are already being used.

_Original issue: http://code.google.com/p/foam-framework/issues/detail?id=77_

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.