Hi Ian,
I'm guessing that the code path that optimizes out the visitor functions
is not checking if the filter is fully supported... the filter needs to be
either
fully supported, or the SQL optimization must be skipped.
There is plenty of testing but at an integration level, rather than at the
While taking a quick look at
https://osgeo-org.atlassian.net/browse/GEOT-7161 I can't find any tests for
the org.geotools.jdbc.JDBCDataStore.doSelectAggregateSQL(String,
List, List, SimpleFeatureType, Query,
LimitingVisitor, StringBuffer)
or