[ https://issues.jboss.org/browse/TEIID-2495?page=com.atlassian.jira.plugin... ] Steven Hawkins resolved TEIID-2495. ----------------------------------- Resolution: Done Took the first path. Any single insert statement for each row plan will be converted into the equivalent single insert statement, which allows for batching or bulk passing to pass through if possible. However multiple inserts or complex processing will result in the default for each row behavior. A more general enhancement would look at for each row plans containing nothing but a series of update statements and turn that into a batched update plan. That too though is somewhat limiting, so I'd next pursue the general approach based upon the transaction layer, but that gets quite hairy - tracking updates by source, flushing when another access occurs, appropriately handling generated keys or update counts that are requested immediately, etc. Also elevated the internal notion of atomic to the entire for each row update, rather than for each row. A separate issue can be logged if needed for treating this in a more lax manner. -- 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