FIX: correctly ignore fields when reading data #391
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Resolves #388
Drivers will return inconsistent results when
columns
does not include the columns referenced inwhere
expression. For some drivers, this will either return 0 results or raise an exception; other drivers appear to work without issue (GPKG, GeoJSON). Added documentation to indicate that users should include the column used bywhere
in their list of columns.The test added here verifies that fields are indeed ignored by GDAL (previously they weren't properly ignored).