![]() Leave the field's data type as TIMESTAMP and change the data source's time zone to be "UTC". For this scenario, you could do either of the following:Ĭhange the field's data type to be TIMESTAMP WITH TIME ZONE and leave "Use database settings" for the data source's time zone property Then, if you login with CET time zone, you'd see 13:37:00 in the Winter. So, 12:37:00 UTC in the database would be treated as 13:37:00 CET or 14:37:00 CEST in JasperReports Server. Then, if you specified "Use database settings" for the data source setup, the TIMESTAMP WITH TIME ZONE values coming from the database would have a time zone value in them and JasperReports Server would convert them to the time zone JasperReports Server is in (CET/CEST). The behavior would differ if the field's datatype was TIMESTAMP WITH TIME ZONE. So, if you select CET as the time zone on the login page, and it's Winter, you will see 12:37:00 in your report. So, if the TIMESTAMP value from the database has 12:37:00, then JasperReports Server treats this value as 12:37:00 CET/CEST. Procedure Configuring Summer Time (Daylight Saving Time) You can configure when summer time, or daylight saving time, is in effect for the device and the offset in minutes. Since you specified "Use database settings", then the TIMESTAMP values coming from the database will be trusted, and JasperReports Server will internally treat these values as the same time zone as JasperReports Server (CET/CEST). You can configure the time zone to offset the device clock time from UTC. The data type for this field is TIMESTAMP.ĬET is UTC+1 in the Winter, and CEST is UTC+2 in the Summer. ![]() The data source configuration in JasperReports Server has "Use database settings" for the time zone. The JasperReports Server is installed in CET/CEST, and I choose the time zone on the JasperReports Server login page as Europe/Paris. The times are stored in UTC in the database, and I am located in CET (Winter)/CEST (Summer). I am using an Oracle database for my reports, and one of the time fields is returning the wrong values when I run the report in my local time zone. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |