On Mon, Jul 4, 2011 at 7:40 PM, Andrea Aime <[email protected]>wrote:
> Actually, thinking about it the security case is a bit different, in that
> mixing
> two attribute lists I need to have the security one act as the only
> possible
> set of values, thus pick the intersection, not the sum, so I need to roll
> some custom bits anyways.
>
Hmmm... which makes me think... mixQuery intersects the filters of the
two queries, takes the smaller of the "maxFeatures" values... and then
adds the attributes of both queries?
Should'nt it intersect the attribute sets too?
Or maybe we should have two new methods, intersectQueries and
addQueries, one with or-ing behavior and one with and-ing behavior?
Cheers
Andrea
--
-------------------------------------------------------
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy
phone: +39 0584 962313
fax: +39 0584 962313
http://www.geo-solutions.it
http://geo-solutions.blogspot.com/
http://www.youtube.com/user/GeoSolutionsIT
http://www.linkedin.com/in/andreaaime
http://twitter.com/geowolf
-------------------------------------------------------
------------------------------------------------------------------------------
All of the data generated in your IT infrastructure is seriously valuable.
Why? It contains a definitive record of application performance, security
threats, fraudulent activity, and more. Splunk takes this data and makes
sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-d2d-c2
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
