Hi,
I prepared a pull request for the subject:
https://github.com/geotools/geotools/pull/470
I used tha approach described in my last email.
As an additional note, I also added a preserveOrder flag to help pagination
be consistent.
With this flag the visitor set mantains the order in which items h
On Fri, May 30, 2014 at 6:58 PM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> Hi,
> moving on on this, I tried the following approach:
> - created a new LimitingVisitor interface with getStartIndex and
> getMaxFeatures methods, to be used by visitor aware stores
> - changed
Hi,
moving on on this, I tried the following approach:
- created a new LimitingVisitor interface with getStartIndex and
getMaxFeatures methods, to be used by visitor aware stores
- changed UniqueVisitor to implement this interface and added pagination
capabilities to the visitor if those two prop
On Mon, May 19, 2014 at 5:16 PM, Mauro Bartolomeoli <
mauro.bartolome...@geo-solutions.it> wrote:
> Hi,
> recently we tried to implement a WPS process to do paginated extraction of
> sorted unique attribute values from features.
>
> The approach was to apply a UniqueVisitor to a Query object with
Hi,
recently we tried to implement a WPS process to do paginated extraction of
sorted unique attribute values from features.
The approach was to apply a UniqueVisitor to a Query object with sortBy and
limits applied.
The problem with this approach is that the current semantic for such
implementati
