Hi Ian, what exactly are you meaning with 'make the column a timestamp'? Because in GeoServer I already tried to change the data type to 'Timestamp' and that doesn't change anything. And in the Oracle database the DATE type also stores time values. From the documentation: "The fields that apply to all Oracle Database datetime and interval data types are: YEAR MONTH DAY HOUR MINUTE SECOND." (https://docs.oracle.com/en/database/oracle/oracle-database/23/nlspg/datetime-data-types-and-time-zone-support.html#GUID-789689BF-5682-4577-8ADE-8105C652CBB7)
So would it be necessary to change the data type inside the database? And why are values on the afternoon or evening set to noon instead of midnight if only year, month and day are preserved? Thank you Daniel From: Ian Turton <ijtur...@gmail.com> Sent: Donnerstag, 18. April 2024 12:12 To: Calliess Daniel Ing. <daniel.calli...@stadt-salzburg.at> Cc: geoserver-users@lists.sourceforge.net Subject: [EXTERN!]: Re: [Geoserver-users] Wrong time values for Oracle DATE columns 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<mailto:daniel.calli...@stadt-salzburg.at>> wrote: 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 03:17:05 becomes 1.1.2024 00:00:00 This happens only when I'm publishing a complete table, not when I'm defining an SQL view. Directly after creating the new layer, the column type is set to the Java data type 'Date'. Comparing to an SQL view I saw that there the column is defined as 'Timestamp'. But also changing the data type using the 'Customize attributes' function to 'Timestamp' or 'Time' doesn't help. This happend in GeoServer 2.23.0 and also 2.25.0. Does anybody have an idea what's going on here. Thank you and best regards Daniel _______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net<mailto:Geoserver-users@lists.sourceforge.net> https://lists.sourceforge.net/lists/listinfo/geoserver-users -- Ian Turton
_______________________________________________ Geoserver-users mailing list Please make sure you read the following two resources before posting to this list: - Earning your support instead of buying it, but Ian Turton: http://www.ianturton.com/talks/foss4g.html#/ - The GeoServer user list posting guidelines: http://geoserver.org/comm/userlist-guidelines.html If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer Geoserver-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geoserver-users
