Andrew, I encourage you to persist with the list (I'm copying this mail back onto it). No doubt others will run into the same problem sooner or later. This might be an ArcSDE-specific error, in which case you will find more ArcSDE users on the list. If not, it may well be something deep in the SQL generation that will be of general interest, and you will need the SQL gurus.
There is a nasty gotcha in the standard Java libraries that a calendar with uninitialized fields gets those fields initialized to the local time. The error you are seeing looks a bit like one of these. I see you created a Jira issue: http://jira.codehaus.org/browse/GEOT-3507 Please reply on your original thread to let Gabriel know that you have created the Jira issue he requested. Jira-generated email can get lost in the flood. Kind regards, Ben. On 18/04/11 14:05, andrew walsh wrote: > Hi Ben and Miles, > > I am getting this bug with Geoserver for which I have had a conversation > on the geoserver users list but so far no real help. So I thought I'd > better send to you guys as it may have slipped your attention through > the hundreds of emails on the list. > > We are using Geoserver 2.0.1 with an ARSCDE-Oracle (ESRI) data > store. I have a simple table (point features) that has a time series of SST > and > a column with a Oracle DATE type called OBS_DATE_TIME. I want > to filter the data by inclusive date range using>= and<= but its > not working. Seems only> and< operators work which isn't good > enough. > > For example try this URL > (filter is: Bilgola and>=2010-12-12 08:58:00 and =< 2011-01-06 09:12:00 ) > and you will 1 feature back in GML but you should get 2 features, 1 at > 2010-12-12 08:58:00 and > the other at 2011-01-06 09:12:00 > > http://www.metoc.gov.au/geoserver/wfs?&VERSION=1.1.0&SERVICE=WFS&REQUEST=GetFeature&; > TYPENAME=test:TEST.BEACH_TEMPS&Filter=<Filter><And><PropertyIsEqualTo><PropertyName>LOCATION</PropertyName> > <Literal>Bilgola</Literal></PropertyIsEqualTo><PropertyIsGreaterThanOrEqualTo><PropertyName>OBS_DATE_TIME</PropertyName><Function > name="dateParse"><Literal>yyyy-MM-dd HH:mm:ss</Literal><Literal>2010-12-12 > 08:58:00</Literal></Function></PropertyIsGreaterThanOrEqualTo><PropertyIsLessThanOrEqualTo><PropertyName>OBS_DATE_TIME</PropertyName><Function > name="dateParse"><Literal>yyyy-MM-dd HH:mm:ss</Literal><Literal>2011-01-06 > 09:12:00</Literal></Function></PropertyIsLessThanOrEqualTo></And></Filter> > > One vague theory I have is that a random 1/1000 second value is being added to > timestamp > i.e see the GML it says 2010-12-12T08:58:00.567 but database is 2010-12-12 > 08:58:00 > which is causing the = comparison operation to return false. Actually I think > it > shouldn't be adding > the 1/1000 seconds bit and the GML you get back should be > '2010-12-12T08:58:00.000' > > Any ideas about this would be greatly appreciated. > Any other time range filters out there with Geoserver out that work? > > Andrew Walsh > Data Facilitator AODN > > -- Ben Caradoc-Davies <[email protected]> Software Engineering Team Leader CSIRO Earth Science and Resource Engineering Australian Resources Research Centre ------------------------------------------------------------------------------ Benefiting from Server Virtualization: Beyond Initial Workload Consolidation -- Increasing the use of server virtualization is a top priority.Virtualization can reduce costs, simplify management, and improve application availability and disaster protection. Learn more about boosting the value of server virtualization. http://p.sf.net/sfu/vmware-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
