Hi,
We could not say then years ago if Geoserver did something wrong or if it was
only because we could not handle the dates right with Oracle. If I remember
right it was somehow messy with all the NLS settings etc. and it was something
like Oracle 8 or 9 then. Perhaps we had also some trouble with the Oracle DATEs
and TIMESTAMPs and how they were converted into XML elements. So I can’t say
that it does not work, only that we found it difficult and decided to cast
times to strings.
-Jukka Rahkonen-
Jérémie Fortin-Groulx wrote:
Thanks all for your answers! I just wanted to be sure that there is no fix for
this issue. We will see if we can live with this workaround with string. If we
opt for a Geoserver architecture for the Town of Montreal, it will be a good
idea to funding this feature.
Cheers!
Jeremie
Geomatics engineer
------------------------------------------------------------------------------
Want excitement?
Manually upgrade your production database.
When you want reliability, choose Perforce.
Perforce version control. Predictably reliable.
http://pubads.g.doubleclick.net/gampad/clk?id=157508191&iu=/4140/ostg.clktrk
_______________________________________________
Geoserver-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-users
