[ https://issues.jboss.org/browse/TEIID-4205?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-4205: --------------------------------------- The change to allow results to flow under a transaction are easy but reverted due to: * lob values cannot be read concurrently with the usage of their underlying connection, which is easy to workaround by copying the lob, or alternatively we can move the processing onto the main workitem * there isn't a good notion of statement completeness. from the spec there are competing definitions of when a statement is complete - either when the result set has been fully read or when the result set has been closed. In our case "when the result set is closed" is somewhat inconsistent as we are proactively producing some number of rows (although this could be explained as an extension of the fetch size). The current behavior of completing processing ensures statement completeness in a way that does not depend on how much of result set the client reads. In the xa/local case we may also need to account for commits that happen concurrently with processing - which doesn't happen now either. -- This message was sent by Atlassian JIRA (v6.4.11#64026)