myFilter attempts
"bm_end>='2010-04-23'" OR
"bm_end>='2010-04-23' && owner_id<>1" OR
"bm_end>='2010-04-23' && owner_id!=1"
Neither of the filters above seem to be working properly - no errors but not the correct results either.
Is the date format correct?
Where is this stuff documented including date comparisons?
What am I doing wrong?
Thanks,
Joe
I'm not very familiar with GeoServer's implementation of CQL, but there's a good description of the basic CQL language itself at http://zing.z3950.org/cql/intro.html.
I think that GeoServer uses CQL-Java, http://zing.z3950.org/cql/java/. You'd probably have to dig in more there to find out about what kinds of date operations it supports.
There's also some interesting discussion at http://zing.z3950.org/cql/profiles.html about extending CQL outside of its bibliographic roots. (CQL originated as a query language for library resources.) Spatial and date searches are mentioned specifically.
myFilter attempts
"bm_end>='2010-04-23'" OR
"bm_end>='2010-04-23' && owner_id<>1" OR
"bm_end>='2010-04-23' && owner_id!=1"
Neither of the filters above seem to be working properly - no errors but not the correct results either.
Is the date format correct?
Where is this stuff documented including date comparisons?
What am I doing wrong?
Thanks,
Joe
I'm not very familiar with GeoServer's implementation of CQL, but there's a good description of the basic CQL language itself at ZING - A Gentle Introduction to CQL.
I think that GeoServer uses CQL-Java, ZING - CQL-Java: a free CQL compiler for Java. You'd probably have to dig in more there to find out about what kinds of date operations it supports.
There's also some interesting discussion at ZING - CQL - Profiling New Relations and Modifiers about extending CQL outside of its bibliographic roots. (CQL originated as a query language for library resources.) Spatial and date searches are mentioned specifically.
alex
alex
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
When I use the same URL for an AjaxRequest in javascript it fails.
StartAjaxRequest("loadBiomassVectorLayer");
ajaxRequest.open("GET", theWFS + encodeURIComponent(myrequest), true);
ajaxRequest.send(null);
if I display an alert in loadBiomassVectorLayer() for ajaxRequest.readyState == 1 I usually get the exception:
--> loadBiomassVectorLayer() parse failed:
--> e.message: parseJSON
--> ajaxRequest.responseText: Some unexpected error occurred. Error text was: HTTP Error 400: Bad Request
If I do NOT display the alert then most of the time the parser generates an uncaught exception. If the parser does succeed the result is only ONE record where owner_id=7 (the filter was owner_id<>7)
The other problem I'm having is that it gets to loadBiomassVectorLayer() three times where ajaxRequest.readyState == 4
Do you know what is going on here?
Thanks,
Joe
On 04/26/10, Jody Garnett <jody.garnett@anonymised.com> wrote:
The implementation is part of the geotools project.
When I use the same URL for an AjaxRequest in javascript it fails.
StartAjaxRequest("loadBiomassVectorLayer");
ajaxRequest.open("GET", theWFS + encodeURIComponent(myrequest), true);
ajaxRequest.send(null);
if I display an alert in loadBiomassVectorLayer() for ajaxRequest.readyState == 1 I usually get the exception:
--> loadBiomassVectorLayer() parse failed:
--> e.message: parseJSON
--> ajaxRequest.responseText: Some unexpected error occurred. Error text was: HTTP Error 400: Bad Request
If I do NOT display the alert then most of the time the parser generates an uncaught exception. If the parser does succeed the result is only ONE record where owner_id=7 (the filter was owner_id<>7)
The other problem I'm having is that it gets to loadBiomassVectorLayer() three times where ajaxRequest.readyState == 4
Do you know what is going on here?
Thanks,
Joe
On 04/26/10, Jody Garnett<jody.garnett@anonymised.com> wrote:
The implementation is part of the geotools project.