[
https://issues.redhat.com/browse/TEIID-5844?page=com.atlassian.jira.plugi...
]
Steven Hawkins resolved TEIID-5844.
-----------------------------------
Resolution: Done
Corrected the insert handling to use the into target columns, rather than the dynamic
command columns - as this is how it's being validated. Opted against adding a hard
validation that the table must be temp - it makes very little difference in the logic
whether it's an existing temp or an actual table. Added a doc note about the
positional insert as well.
Dynamic into issues
-------------------
Key: TEIID-5844
URL:
https://issues.redhat.com/browse/TEIID-5844
Project: Teiid
Issue Type: Quality Risk
Components: Query Engine
Reporter: Steven Hawkins
Assignee: Steven Hawkins
Priority: Major
Fix For: 14.0
The documentation states that a temp table must be the target of a dynamic execute into,
but there is nothing preventing that. There is also the assumption that the insert must
supply all columns and is positional - but that generally only makes sense if the temp
table has not yet been defined. If it already exists, then one could expect that the
insert would happen based upon matching the column names - but it does not. That needs to
be clear in the code/docs.
--
This message was sent by Atlassian Jira
(v7.13.8#713008)