IIRC we have switched from the ‘CQL2’ CQL module to the ‘ECQL’ one in GeoServer trunk. It seems that the older module (which you are still using) does not allow functions (only property names) as the left-hand-side of a ‘LIKE’ comparison.
I think updating to GeoServer 2.1 (not yet released, but in RC status) would allow you to use this filter. Alternatively, you can rewrite your filter using nested functions instead:
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
Thank you David for your reply and time but this didn't work either. I have
stable version in production so I am afraid if I can do anything to improve
search. I'll install 2.1 RC to see if this works there.
Its strange that documentation for 2.0 still mentions to use cql filter
function while they don't work.
David Winslow-5 wrote:
IIRC we have switched from the 'CQL2' CQL module to the 'ECQL' one in
GeoServer trunk. It seems that the older module (which you are still
using)
does not allow functions (only property names) as the left-hand-side of a
'LIKE' comparison.
I think updating to GeoServer 2.1 (not yet released, but in RC status)
would
allow you to use this filter. Alternatively, you can rewrite your filter
using nested functions instead:
Thank you David for your reply and time but this didn’t work either. I have
stable version in production so I am afraid if I can do anything to improve
search. I’ll install 2.1 RC to see if this works there.
Its strange that documentation for 2.0 still mentions to use cql filter
function while they don’t work.
David Winslow-5 wrote:
IIRC we have switched from the ‘CQL2’ CQL module to the ‘ECQL’ one in
GeoServer trunk. It seems that the older module (which you are still
using)
does not allow functions (only property names) as the left-hand-side of a
‘LIKE’ comparison.
I think updating to GeoServer 2.1 (not yet released, but in RC status)
would
allow you to use this filter. Alternatively, you can rewrite your filter
using nested functions instead:
Sent from the GeoServer - User mailing list archive at Nabble.com.
Free Software Download: Index, Search & Analyze Logs and other IT data in
Real-Time with Splunk. Collect, index and harness all the fast moving IT data
generated by your applications, servers and devices whether physical, virtual
or in the cloud. Deliver compliance at lower cost and gain new business
insights. http://p.sf.net/sfu/splunk-dev2dev
Thank you David for your reply and time but this didn’t work either. I have
stable version in production so I am afraid if I can do anything to improve
search. I’ll install 2.1 RC to see if this works there.
Its strange that documentation for 2.0 still mentions to use cql filter
function while they don’t work.
The functions do work, as David alreayd explained what you’re seeing is a limitation of the official
OGC CQL language (which is documented in its own OGC standard, I think it’s
the catalog one).
A CQL comparison can only have this structure:
whilst yours is
GeoServer 2.1 uses ECQL (extended CQL), a home grown set of extensions
on top of the standard CQL that makes the language more similar to SQL and
allows, among others, for the
form to be parsed successfully
Hope this helps
Cheers
Andrea
–
Ing. Andrea Aime
GeoSolutions S.A.S.
Tech lead
Via Poggio alle Viti 1187
55054 Massarosa (LU)
Italy