[
https://jira.jboss.org/jira/browse/TEIID-866?page=com.atlassian.jira.plug...
]
Ramesh Reddy commented on TEIID-866:
------------------------------------
That is correct, when it sees a SQL command starts with "SELECT" it assumes that
it is always returns resultset. It is not smart enough to parse through to see that it can
be a callable statement. Seems like this solvable by using " boolean execute(String
sql) " call on the Statement object.
AdminShell is not able to handle SELECT * INTO #TEMP FROM foo;
(statement does not return a result set)
-------------------------------------------------------------------------------------------------------
Key: TEIID-866
URL:
https://jira.jboss.org/jira/browse/TEIID-866
Project: Teiid
Issue Type: Bug
Components: Tools
Affects Versions: 6.2.0
Environment: Fedora 10, 6.2 Stable (GA)
Reporter: Paul Nittel
Fix For: 6.3
Here's the crux of the issue:
select * into #temp from bqt1.smalla;
// Error: // Uncaught Exception: TargetError : at Line: 165 : in file: URL:
jar:file:/home/pnittel/teiid62/adminshell/lib/teiid-adminshell-6.2.0.jar!/scripts/jdbc.bsh
: throw e ;
Target exception: com.metamatrix.jdbc.MMSQLException: Statement does not return a result
set.
Steve H. put it this way:
"The into clause turns the statement into an insert, which does not have a result
set - it only returns an update count. It does seem like AdminShell should handle that
case. It's probably doing some parsing of the command and expecting it to return a
resultset..."
This same statement works fine in SQL Explorer.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira