[teiid-issues] [JBoss JIRA] (TEIID-5482) Dynamic SQL: Executing Dynamic SQL Throws an Error
[
https://issues.jboss.org/browse/TEIID-5482?page=com.atlassian.jira.plugin...
]
dalex dalex edited comment on TEIID-5482 at 9/25/18 12:32 PM:
--------------------------------------------------------------
[~shawkins] very sorry for the late reply but I have only stacktrace which I can see in
debug mode
!TEIID_5482_stacktrace.jpg|thumbnail!
when running the:
{code:sql}
BEGIN
declare clob sql_query = 'select 1';
execute immediate sql_query;
END ;;
{code}
via SQuirrel. You can see that resultMode has EITHER value. I have suspicious that
it's set via either StatementImpl.submitExecute or StatementImpl.execute methods in
JDBC driver.
was (Author: dalex005):
[~shawkins] very sorry for the late reply but I have only stacktrace which I can see in
debug mode
!TEIID_5482_stacktrace.jpg|thumbnail!
when running the:
{code:sql}
BEGIN
declare clob sql_query = 'select 1';
execute immediate sql_query;
END ;;
{code}
via SQuirrel. You can see that resultMode has EITHER value. I suspicious that it's set
via either StatementImpl.submitExecute or StatementImpl.execute methods in JDBC driver.
Dynamic SQL: Executing Dynamic SQL Throws an Error
--------------------------------------------------
Key: TEIID-5482
URL: https://issues.jboss.org/browse/TEIID-5482
Project: Teiid
Issue Type: Bug
Components: Query Engine
Affects Versions: 11.1
Environment: teiid-11.1.0 (from 01.09.2018) on WildFly Full 11.0.0.Final (WildFly
Core 3.0.8.Final)
Reporter: dalex dalex
Assignee: Steven Hawkins
Attachments: TEIID_5482_stacktrace.jpg
When running the following query:
{code:sql}
BEGIN
declare clob sql_query = 'select 1';
execute immediate sql_query;
END ;;
{code}
in result set can see only:
{code:noformat}
Error: 0
SQLState: 38000
ErrorCode: 0
{code}
but running the following query just adding the "as cnt string":
{code:sql}
BEGIN
declare clob sql_query = 'select 1';
execute immediate sql_query as cnt string;
END ;;
{code}
can see correct "1" in result set. I don't know if it's a correct
behavior, maybe it's related to how SQuirrel handles result set.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)