Hi,
currently, ogc:PropertyIsEqualTo and ogc:PropertyIsLike filters are case sensitive in GeoServer. Wouldn't it make sense to make at least ogc:PropertyIsLike case insensitive? The filter encoding spec says nothing about case sensitivity, but IMO keyword searches would be much more convenient if filters would be case insensitive.
At least it would be nice if I could configure case sensitivity on a per-layer or per-instance base.
What do others think?
Regards,
Andreas.
--
Andreas Hocevar
OpenGeo - http://opengeo.org/
Expert service straight from the developers.
Hi Andreas,
Actually in Filter 1.1 PropertyIsEqualTo and PropertyIsNotEqualTo have a "matchCase" flag, so you can trigger case insensitive filters. Unfortunately its not supported on PropertyIsLike however.
But... I wonder if it is worth supporting it anyways as an "extension" to the spec.
I guess the question is: is it useful to you even though its not supported by the spec. Sounds like it might be.
What do others think?
-Justin
Andreas Hocevar wrote:
Hi,
currently, ogc:PropertyIsEqualTo and ogc:PropertyIsLike filters are case sensitive in GeoServer. Wouldn't it make sense to make at least ogc:PropertyIsLike case insensitive? The filter encoding spec says nothing about case sensitivity, but IMO keyword searches would be much more convenient if filters would be case insensitive.
At least it would be nice if I could configure case sensitivity on a per-layer or per-instance base.
What do others think?
Regards,
Andreas.
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
Justin Deoliveira ha scritto:
Hi Andreas,
Actually in Filter 1.1 PropertyIsEqualTo and PropertyIsNotEqualTo have a "matchCase" flag, so you can trigger case insensitive filters. Unfortunately its not supported on PropertyIsLike however.
But... I wonder if it is worth supporting it anyways as an "extension" to the spec.
I guess the question is: is it useful to you even though its not supported by the spec. Sounds like it might be.
What do others think?
I'm not opposed to adding this kind of functionality, seems like
a good one.
If we want to implement this we'll also have to talk at the gt2
level, since that will require a change in the filter api and
possibly in GeoApi as well.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.