[
https://issues.jboss.org/browse/TEIID-5236?page=com.atlassian.jira.plugin...
]
Steven Hawkins edited comment on TEIID-5236 at 1/29/18 2:22 PM:
----------------------------------------------------------------
It appears that most of the issues were due to the driver itself -
in addition to the support mentioned in the previous comments, we were also affected by
https://github.com/pgjdbc/pgjdbc/pull/745 which showed that we were putting the wrong
string form of boolean values into results but the previous driver version was tolerant.
I've now successfully tested 2.8 and converted the Teiid source to test with the
latest 42.1 driver. Still need to validate the latest geoserver release.
was (Author: shawkins):
It appears that most of the issues were due to the driver itself. I've now
successfully tested 2.8 and converted the Teiid source to test with the latest 42.1
driver. Still need to validate the latest geoserver release.
Document and update GeoServer/PG JDBC compatibility
---------------------------------------------------
Key: TEIID-5236
URL:
https://issues.jboss.org/browse/TEIID-5236
Project: Teiid
Issue Type: Quality Risk
Components: Documentation, ODBC, Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 10.2
It is not documented on the geoserver integration page, but most of the initial work was
done against versions between 2.6 and 2.8. It appears that even 2.8 can have issues as it
can use the 9.4 postgresql driver, which expects additional syntax support for type
metadata.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)