Permalink
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Browse files
Instead of double-iterating over features caused by calling
QgsVectorLayer::minimumValue and then QgsVectorLayer::maximumValue when we need BOTH the min and max value for a field, add an optimised QgsVectorLayer::minimumAndMaximumValue() method which can calculate both min and max at the same time in a single iteration. Potentially halves the cost of calculating these values whenever we are forced to do a full iteration to calculate them.
- Loading branch information
Showing
with
283 additions
and 67 deletions.
- +56 −6 python/core/auto_generated/vector/qgsvectorlayer.sip.in
- +5 −2 src/core/classification/qgsclassificationmethod.cpp
- +3 −2 src/core/qgsvectorfilewriter.cpp
- +52 −32 src/core/vector/qgsvectorlayer.cpp
- +37 −3 src/core/vector/qgsvectorlayer.h
- +27 −10 src/core/vector/qgsvectorlayertemporalproperties.cpp
- +3 −2 src/gui/editorwidgets/qgsrangeconfigdlg.cpp
- +6 −2 src/gui/qgspropertyassistantwidget.cpp
- +7 −2 src/gui/symbology/qgsgraduatedsymbolrendererwidget.cpp
- +15 −6 src/server/qgsserverapiutils.cpp
- +11 −0 tests/src/core/testqgsvectorlayer.cpp
- +61 −0 tests/src/python/test_qgsvectorlayer.py
Oops, something went wrong.