On Tue, Jun 11, 2013 at 6:22 PM, Martin Davis <[email protected]> wrote:

> If using the "inX" functions is still too verbose, or if it's awkward to
> split up the blocks of IDs, and depending on how much effort you want to
> spend...
>
> You could look at writing a custom filter function   "inList(int,
> String)", where the second argument is a string literal which represents
> the list of IDs in some way (e.g. such as "1,2,3,4").
>

One thing to notice though, the original filters are long but are going to
get encoded into SQL,
whist filter function are not unless someone changes the code in the SQL
encoders to recognize them,
or patches the SimplifyingFilterVisitor to expand the filter function into
a regular list of filters.

Cheers
Andrea

-- 
==
Our support, Your Success! Visit http://opensdi.geo-solutions.it for more
information.
==

Ing. Andrea Aime
@geowolf
Technical Lead

GeoSolutions S.A.S.
Via Poggio alle Viti 1187
55054  Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 1660272
mob: +39  339 8844549

http://www.geo-solutions.it
http://twitter.com/geosolutions_it

-------------------------------------------------------
------------------------------------------------------------------------------
This SF.net email is sponsored by Windows:

Build for Windows Store.

http://p.sf.net/sfu/windows-dev2dev
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to