[
https://issues.jboss.org/browse/TEIID-5624?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-5624:
---------------------------------------
This is difficult for us to map to... There is no such thing as an ephemeral lob for pg.
It has to be when you select a lob from a table, you are actually getting the oid.
We have effectively ephemeral lobs scoped to the resultset. A way to make this work is to
provide some mapping of lob (resultset/streaming id) to an integer lob id. Then we'd
use that as the id for lo_open and provide another integer id as the file descriptor for
the open lob. However clients that don't support lo or aren't specifically
expecting Teiid behavior will need to be able to turn off this behavior and get the
equivalent bytea and text values.
We may not be able to simply reuse the internal streaming id as we do inline our lobs - or
I'd need to add turn that off on a per session/basis.
Implement LO function support for pg/ODBC
-----------------------------------------
Key: TEIID-5624
URL:
https://issues.jboss.org/browse/TEIID-5624
Project: Teiid
Issue Type: Feature Request
Components: ODBC
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 12.2
The current logic maps lobs to bytea and text types and caps their length by default to
2MB. We should add actual lob support using the LO functions.
--
This message was sent by Atlassian Jira
(v7.12.1#712002)