Hi all,
Recently a client attempting to upgrade to gs 2.1 RC4 reported an issue with
cql filter handling. Long story short they are trying to use an attribute
named "id" (not a primary key) in a simple comparison filter and the ecql
parser chokes on it. I recall conversation around ecql and the handling of
attributes named "id" regarding the fact that ecql can do feature ids. But
can't find much in the docs or in jira.
I guess the question is this is intended with the switch to ecql? I would
assume not as it seems a regression. An easy fix would be to mirror ogc
filter parsing where we fall back onto the old filter parser if the new one
fails. We could do the same with the ECQL/CQL parsers.
Thoughts?
-Justin
--
Justin Deoliveira
OpenGeo - http://opengeo.org
Enterprise support for open source geospatial.
------------------------------------------------------------------------------
Xperia(TM) PLAY
It's a major breakthrough. An authentic gaming
smartphone on the nation's most reliable network.
And it wants your games.
http://p.sf.net/sfu/verizon-sfdev
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
