[ https://issues.jboss.org/browse/TEIID-2577?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2577. ----------------------------------- Resolution: Done Added the initial implementation available via CommandContext.getConnection It's probably best to leave this as a somewhat experimental/undocumented feature at this point. The connection disables explicit transaction control, switching the user, and close. 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). At least for socket connections since we store the useCallingThread on the DQPWorkContext this means that the resulting internal connections will consume an additional processing thread, which can be addressed later on. -- 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