This timezone issue is related to date datatypes. This issue will affect you only if your application has time data from multiple timezones (typically timetables).

ISSUE: OpenROAD 3.5 uses absolute timezone handling based on the Ingres 6.4 model; this has certain built-in inaccuracies, and later versions of Ingres (and OpenROAD 4.0 onward) use timezone information tables that are accurate.

Consequently, OpenROAD 3.5 applications handling time data as described previously typically have workaround code to correct the client data (otherwise a French train leaves an hour before the English client application says it will).

RESOLUTION: Upgrades to the latest version of OpenROAD must disable the workarounds wherever they occur in the code.