[ https://issues.jboss.org/browse/TEIID-2577?page=com.atlassian.jira.plugin... ] Mark Addleman commented on TEIID-2577: -------------------------------------- Ramesh - The motivation isn't so much that we didn't want caching in the translator layer. The issue is that the client doesn't know the *logical* schema of the stored procedure. The *logical* schema is determined by the translator & data source. Therefore, we need a level of indirection and a way to implement that indirection. Using traditional SQL constructs, we were trying to implement the indirection by a VARCHAR column containing a SELECT statement. The SELECT statement could have been a constant UNION of all the rows returned by the data source but, obviously, that would be unwieldy. Instead, we thought to have the translator populate a temp table and return a SELECT statement against that temp table. Ultimately, I think this is entirely the wrong approach. Instead, our stored procedure should return an XML document of the result set from the data source. Then, the client can populate a temp table with the results. -- 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