Thanks Jackie,
I think the IN() operator will do the trick, I was just using it wrong.
Does anyone know what the character limit of the filter string is? I am
thinking that even with the IN() operater I could run into the limit, in
which case I might have to go with your suggestions after all. This however
brings up the next question: How does an array translate to a filter?
Jackie, could you provide us with a bit of sample code on how you would
implement your suggestion?
Thanks,
Sierk
Jackie Ng wrote
>
> If stringing logical -OR- conditions together is the only supported way to
> filter, then a way to work around the filter limit is to query your
> features in batches. So if you have say 100 hydrants to filter out, you
> could do 4 queries each with 25 different hydrant -OR- conditions.
>
> If you're using .net constructing such a filter is easy. Store the
> individual conditions in a List<string> then a string.join(" OR ",
> yourList.ToArray()) will give you the combined filter.
>
> - Jackie
>
--
View this message in context:
http://osgeo-org.1803224.n2.nabble.com/Query-features-based-on-a-list-or-array-of-attribute-values-tp7025060p7043267.html
Sent from the MapGuide Users mailing list archive at Nabble.com.
_______________________________________________
mapguide-users mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/mapguide-users
