Eliminate one collection size call in WFS 2.0, when context allows
Description
Right now we are making a second size call even if the size returned when running the first query is less than the maxfeatures coming from the request/configuration. But in that case we can just take the size returned, as we are sure there are no extra records shaved off by the maxfeatures bit.
Environment
None
Activity
Andrea Aime
February 15, 2017 at 11:47 AM
Mass closing all resolved issues not modified in the last 4 weeks
Right now we are making a second size call even if the size returned when running the first query is less than the maxfeatures coming from the request/configuration.
But in that case we can just take the size returned, as we are sure there are no extra records shaved off by the maxfeatures bit.