Re: [Geoserver-users] Wrong time values for Oracle DATE columns

2024-04-23 Thread Calliess Daniel Ing .
Aime Sent: Freitag, 19. April 2024 09:26 To: Calliess Daniel Ing. Cc: geoserver-users@lists.sourceforge.net Subject: [EXTERN!]: Re: [Geoserver-users] Wrong time values for Oracle DATE columns Hi Daniel, the Oracle datastore tests seem to confirm what Ian says, they create a table to store

Re: [Geoserver-users] Wrong time values for Oracle DATE columns

2024-04-21 Thread mark
Op 18-04-2024 om 11:39 schreef Calliess Daniel Ing.: Hi, I just discovered that GeoServer is rounding Oracle DATE attribute values down to zero or twelve hours when I'm publishing data from a 'Oracle NG (OCI)' data store. Examples: 1.1.2024 17:34:12 becomes 1.1.2024 12:00:00 or 1.1.2024

Re: [Geoserver-users] Wrong time values for Oracle DATE columns

2024-04-19 Thread Andrea Aime
Hi Daniel, the Oracle datastore tests seem to confirm what Ian says, they create a table to store a date, a timestamp, and a time column (some databases can handle the three types as separate) and the syntax is the following: CREATE TABLE DATES (D DATE, DT TIMESTAMP, T TIMESTAMP) and then they

Re: [Geoserver-users] Wrong time values for Oracle DATE columns

2024-04-18 Thread Ian Turton
That's the expected behaviour - if you need to preserve the time of the date make the column a timestamp (preferably with timezone) rather than a data which only stores the year, month and day. Ian On Thu, 18 Apr 2024 at 10:56, Calliess Daniel Ing. < daniel.calli...@stadt-salzburg.at> wrote: >