+1 - agreed that this seems like the "simplest" way forward.
On Thu, Nov 19, 2015 at 10:08 AM, cheesybiscuits <[email protected]> wrote: > Wow, that is a long thread! > > I read / skimmed through the full conversation and what I take from it is > there are numerous ways this could be done that would increase complexity, > deviate from GeoServer's UI philosophy, and consume lots of developer time, > but that Andrea's original suggestion - to not append an SDO_FILTER clause > if a spatial index doesn't exist for the geometry column - is the most > suitable. It can simply be the Oracle function / procedure writer's > responsibility to ensure their code filters output features to the queried > bbox. > > Ideally GeoServer would make minx, miny, maxx, and maxy of the query > available by default (e.g. accessible in your SQL View via %%minx%%) so > that > these would not have to be provided by viewparams. > > There is a lot of documentation on starting GeoServer development but I > have > previously been confused about how to get involved in extension > development. > Any pointers for the best way to get started in this? > > > > > -- > View this message in context: > http://osgeo-org.1560.x6.nabble.com/GeoServer-s-spatial-filter-preventing-SQL-view-layer-from-working-tp5237269p5237488.html > Sent from the GeoServer - User mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > _______________________________________________ > Geoserver-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-users >
------------------------------------------------------------------------------
_______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
