Hi,

Date datatypes in Oracle are somewhat painful and local settings have an effect 
on what you get back when you do "SELECT date_attribute FROM table"

http://docs.oracle.com/cd/B28359_01/olap.111/b28126/dml_commands_1029.htm
http://docs.oracle.com/cd/B28359_01/olap.111/b28126/dml_expression001.htm#BABFDAEI

However, if the date format was OK with Geoserver 2.2.3 it should be good also 
after changing to 2.4 if the Oracle database is the same. It is hard to guess 
what is differently now. What you can do it to turn Geoserver  logging to 
Geotools developer level and check from the log what queries Geoserver is 
actually doing.

If you want to make a robust system, don't publish the Oracle date column at 
all in WFS but create a view and convert dates into strings by using SELECT 
TO_CHAR....

Did you mean that before you got out something like "2013-10-23Z"? That looks 
also odd to me because timezone does not make much sense for dates. With time 
included it is of course fine "2013-10-23T05:02Z"

-Jukka Rahkonen-


Lähettäjä: Chamberland, Martin [mailto:martin.chamberl...@fadq.qc.ca]
Lähetetty: 23. lokakuuta 2013 19:51
Vastaanottaja: 'gmi...@library.berkeley.edu'
Kopio: geoserver-users@lists.sourceforge.net
Aihe: Re: [Geoserver-users] date BUG 2.4 Geoserver

We run Geoserver 2.4 on Debian Wheezy 7.2 server. (in fact still not up to 
date,  7.1 server)

bye

De : Garey Mills [mailto:gmi...@library.berkeley.edu]
Envoyé : 23 octobre 2013 11:21
À : Chamberland, Martin
Cc : Jonathan Moules; 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver

I believe the problem that Martin is having is that all the dates are the epoch 
(1969-12-31), in other words, the app is not reading the system time, or the 
system time (use 'date' on a Unix system) is seriously messed up. The problem 
is probably going to me in whatever code is accessing system time (new Date() 
for example. Did geoserver change anything about accessing system time in the 
2.4 release?

On Wed, Oct 23, 2013 at 5:40 AM, Chamberland, Martin 
<martin.chamberl...@fadq.qc.ca<mailto:martin.chamberl...@fadq.qc.ca>> wrote:
It's pretty hard for me to explain correctly because english in not my first 
language.  Let's try my best.

We where running geoserver 2.2.3 for a long time and everything was running 
fine. The only problem (that is not one) we had was  that in the output date, 
there was a "Z" after all date.
So we were sure that is was a bug, so we decide to update to geoserver 2.4 
(latest one) to fix the issue. Meantine (continuing searching) we discover that 
it's not a bug but just normal that the "Z" appear there. But as we where now 
running 2.4, now all date that we output from our Oracle database are  
"1969-12-31",   every date are the same.

I hope i was enough clear,   sorry again for poor English explanation.

Martin C.


De : Jonathan Moules 
[mailto:jonathanmou...@warwickshire.gov.uk<mailto:jonathanmou...@warwickshire.gov.uk>]
Envoyé : 22 octobre 2013 09:50
À : Chamberland, Martin
Cc : 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver

Hi Martin,
I'm not sure what you're asking here - without further information I suspect 
you won't get any help as it's not clear what you want.

Jonathan


On 22 October 2013 14:32, Chamberland, Martin 
<martin.chamberl...@fadq.qc.ca<mailto:martin.chamberl...@fadq.qc.ca>> wrote:
Did you have time to take a look at our problem ?

Thank's!

Martin C.

De : Jonathan Moules 
[mailto:jonathanmou...@warwickshire.gov.uk<mailto:jonathanmou...@warwickshire.gov.uk>]
Envoyé : 21 octobre 2013 08:40
À : Chamberland, Martin
Cc : 
geoserver-users@lists.sourceforge.net<mailto:geoserver-users@lists.sourceforge.net>
Objet : Re: [Geoserver-users] date BUG 2.4 Geoserver

Hi Martin,
That's the ISO standard for date formatting. 
https://en.wikipedia.org/wiki/ISO_8601

Could you be clearer what the problem is for you?

Jonathan


On 17 October 2013 19:38, Chamberland, Martin 
<martin.chamberl...@fadq.qc.ca<mailto:martin.chamberl...@fadq.qc.ca>> wrote:
Hi there,

We just install the new version Geoserver 2.4  and from now we seem to receive 
some strange date format in our request.

All date output create by our trigger look like this:   1969-12-31.

Is there maybe a bug in the 2.4 version ?

Martin C.


------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135031&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users


This transmission is intended for the named addressee(s) only and may contain 
sensitive or protectively marked material up to RESTRICTED and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this transmission in error please notify the 
sender immediately. All email traffic sent to or from us, including without 
limitation all GCSX traffic, may be subject to recording and/or monitoring in 
accordance with relevant legislation.


This transmission is intended for the named addressee(s) only and may contain 
sensitive or protectively marked material up to RESTRICTED and should be 
handled accordingly. Unless you are the named addressee (or authorised to 
receive it for the addressee) you may not copy or use it, or disclose it to 
anyone else. If you have received this transmission in error please notify the 
sender immediately. All email traffic sent to or from us, including without 
limitation all GCSX traffic, may be subject to recording and/or monitoring in 
accordance with relevant legislation.

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net>
https://lists.sourceforge.net/lists/listinfo/geoserver-users

------------------------------------------------------------------------------
October Webinars: Code for Performance
Free Intel webinars can help you accelerate application performance.
Explore tips for MPI, OpenMP, advanced profiling, and more. Get the most from 
the latest Intel processors and coprocessors. See abstracts and register >
http://pubads.g.doubleclick.net/gampad/clk?id=60135991&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users

Reply via email to