[ https://issues.jboss.org/browse/TEIID-196?page=com.atlassian.jira.plugin.... ] Steven Hawkins commented on TEIID-196: -------------------------------------- I think it's best to not address the ease of use for a teiid temporary table for the 8.3 release. The most likely usage pattern to replace an internal temporary table would look like: {code} //- create the source table source.native("CREATE [GLOBAL] TEMPORARY TABLE name IF NOT EXISTS ON COMMIT [DELETE ROWS | DROP]"); //- bring the table into Teiid CREATE FOREIGN TEMPORARY TABLE name ... //- use the table {code} For this to be correctly handled with a GLOBAL temporary table, the table name would need to be unique or the GLOBAL / table definition would need to be the same for all sessions with session specific data scoping (such as Oracle) - or the source would need to support session scoped temporary tables (such as PostgreSQL). It would also need to be accessed under a transaction so that: * the on commit behavior could ensure clean-up - as a Teiid drop is not guaranteed to occur (in some exception cases, loss of db connectivity, hard shutdown, etc.) * the source pool when using track connections by transaction will ensure that multiple uses of that source by Teiid will use the same connection/session and thus the same temporary table/data. -- 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