[
https://issues.jboss.org/browse/TEIID-2586?page=com.atlassian.jira.plugin...
]
Steven Hawkins commented on TEIID-2586:
---------------------------------------
With the TEIID-2067 change the local keyword was made optional for both the create local
temporary and create foreign temporary cases. The rationale is that our interpretation of
local differs with the spec, so it's optional if we keep the keyword. It's also
unlikely that we'll over the same type of session visibility (such that called
procedures can see any session local temp table) and even if we need to offer that
functionality it can be done with the declare style syntax used by other databases like
db2. I don't believe it's necessary to pull these changes back to 8.4.1.
foreign temporary table consistency
-----------------------------------
Key: TEIID-2586
URL:
https://issues.jboss.org/browse/TEIID-2586
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Affects Versions: 8.3
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Fix For: 8.4.1, 8.5
When creating a foreign temporary table the local keyword is omitted. This was done to
cut out some of the verboseness, however it's not consistent with non-foreign tables.
--
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