[
https://issues.jboss.org/browse/TEIID-2577?page=com.atlassian.jira.plugin...
]
Mark Addleman commented on TEIID-2577:
--------------------------------------
The connection disables explicit transaction control, switching the
user, and close.
Do the appropriate JDBC methods throw IllegalState (or some other
exception) in this case? Although I don't expect to use any of these features, it
would be nice to know if we inadvertently trip over a disabled feature.
Each connection obtained off of the command context is unique and any
client state will not be shared (and any client state from the initial user connection
won't be available either).
Client state? Are you referring to Teiid internals
or something that's exposed through JDBC like client info?
Translator API to provide session backed connection
---------------------------------------------------
Key: TEIID-2577
URL:
https://issues.jboss.org/browse/TEIID-2577
Project: Teiid
Issue Type: Feature Request
Components: Connector API
Reporter: Mark Addleman
Assignee: Steven Hawkins
Fix For: 8.6
Provide an API (probably from an ExecutionContext) to obtain a JDBC connection to the
same Teiid instance under the client's session.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira