[
https://issues.jboss.org/browse/TEIID-1928?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-1928:
---------------------------------------
By works just fine over JDBC, you mean that through Teiid JDBC correct? That can be
because either you are pulling the value as timestamp or string without any conversion
along the way. In the PG case you are converting from string to timestamp. You would not
receive an error in the PG layer if it did the same thing - pull the value as a string or
a timestamp without a conversion. You'll want to check the types for the column
through out.
PSQL emulation layer has problems converting timestamp '0000
------------------------------------------------------------
Key: TEIID-1928
URL:
https://issues.jboss.org/browse/TEIID-1928
Project: Teiid
Issue Type: Bug
Affects Versions: 7.6
Environment: java version "1.6.0_20"
OpenJDK Runtime Environment (IcedTea6 1.9.10) (rhel-1.23.1.9.10.el5_7-x86_64)
OpenJDK 64-Bit Server VM (build 19.0-b09, mixed mode)
on
Red Hat Enterprise Linux Server
Teiid 7.6
Perl client running on either Fedora 16 or RHEL 5.7
Using perl-DBD-Pg-2.18.0-3.fc16.x86_64
Reporter: Graeme Gillies
Assignee: Steven Hawkins
When we attempt to run the following query against our teiid 7.6 install we get an error
about converting timestamps. Note this only seems to affect the PSQL emulation layer, jdbc
layer is fine
{noformat}
EngVDBF=> select * from orgchart2s.history;
ERROR: Error Code:S1009 Message:OrgChart2DS: Error Code:S1009 Message:Unexpected
exception while translating results: Cannot convert value '0000-00-00 00:00:00'
from column 6 to TIMESTAMP.
DETAIL: org.teiid.jdbc.TeiidSQLException: Error Code:S1009 Message:OrgChart2DS: Error
Code:S1009 Message:Unexpected exception while translating results: Cannot convert value
'0000-00-00 00:00:00' from column 6 to TIMESTAMP.
EngVDBF=>
{noformat}
It looks like there is a problem converting a timestamp of '0000-00-00 00:00:00'
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira