]
Steven Hawkins reopened TEIID-2112:
-----------------------------------
This is specific to xmltable even though the timestamp code is shared due to Saxon calling
cal.setGregorianChange(new Date(Long.MIN_VALUE));
consistent handling of local timezone on xsd:date, xsd:datetime, and
xsd:time values that have no timezone specified.
---------------------------------------------------------------------------------------------------------------------
Key: TEIID-2112
URL:
https://issues.jboss.org/browse/TEIID-2112
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 7.1
Reporter: Johnathon Lee
Assignee: Steven Hawkins
Fix For: 7.4.4, 8.1
The server is taking the incoming ts string and converting it to a Z value via the server
timezone (handled by STax). When the response document is delivered Saxon converts a
non-timezoned value into an assumed Z value - which is not consistent with the STax
handling. This is within the bounds of XML processing as the absence of timezone
information leaves the timezone interpretation up to the implementation - "timezone
of some unspecified locality as prescribed by the appropriate legal authority".
However, these two paths should be consistent,so a patch would set the local timezone on
xsd:date, xsd:datetime, and xsd:time values that have no timezone specified.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: