[JBoss JIRA] (TEIIDDES-1812) Remove Result Actions are not working on SQL Results View
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1812?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1812 at 7/31/13 4:23 PM:
-----------------------------------------------------------------
Closing and re-opening the Results View will force a refresh and the removed items will be gone.
I tested with basic JBDS install and previewed using Data Tools Explorer's Data > Sample Contents action. Same issue.
Guess datatools changed the event handling in some way that broke their refresh
was (Author: blafond):
Closing and re-opening the Results View will force a refresh and the removed items will be gone.
Guess datatools changed the event handling in some way that broke their refresh
> Remove Result Actions are not working on SQL Results View
> ---------------------------------------------------------
>
> Key: TEIIDDES-1812
> URL: https://issues.jboss.org/browse/TEIIDDES-1812
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution, Views
> Affects Versions: 8.2
> Reporter: Mark Drilling
>
> After running several preview queries, I attempted to remove some of the items from the SQL Results history list. The context and toolbar 'Remove Result' and 'Remove All' actions had no effect - results were not removed.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1692) Update test script for updating 2 data sources
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1692?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1692:
-----------------------------------
Summary: Update test script for updating 2 data sources (was: Old test script for updating 2 data sources, still applicable?)
> Update test script for updating 2 data sources
> ----------------------------------------------
>
> Key: TEIIDDES-1692
> URL: https://issues.jboss.org/browse/TEIIDDES-1692
> Project: Teiid Designer
> Issue Type: Bug
> Components: Documentation
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: Future
>
> Attachments: E2eUpdateTwoSourcesTestScript.pdf
>
>
> The ['Updating Two Data Sources'|^E2eUpdateTwoSourcesTestScript.pdf] test script describes the insertion of SQL transformations for insertion and deletion of data in the underlying data sources.
> Trying to insert these transformations into Designer results in errors such as:
> {quote}
> TEIID31119 Symbol "INPUT".SUPPLIER_ID is specified with an unknown group context partsupplierView.xmi /partsupplier/views updates Problem
> {quote}
> * Does Teiid now do much of what this script is trying to do?
> * Can / should these transformations still be included albeit in a modified form?
> * Is this test script's purpose still appropriate for Designer?
> Requests for comments please.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1692) Old test script for updating 2 data sources, still applicable?
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1692?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1692:
-----------------------------------
Fix Version/s: Future
(was: 8.2)
> Old test script for updating 2 data sources, still applicable?
> --------------------------------------------------------------
>
> Key: TEIIDDES-1692
> URL: https://issues.jboss.org/browse/TEIIDDES-1692
> Project: Teiid Designer
> Issue Type: Bug
> Components: Documentation
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: Future
>
> Attachments: E2eUpdateTwoSourcesTestScript.pdf
>
>
> The ['Updating Two Data Sources'|^E2eUpdateTwoSourcesTestScript.pdf] test script describes the insertion of SQL transformations for insertion and deletion of data in the underlying data sources.
> Trying to insert these transformations into Designer results in errors such as:
> {quote}
> TEIID31119 Symbol "INPUT".SUPPLIER_ID is specified with an unknown group context partsupplierView.xmi /partsupplier/views updates Problem
> {quote}
> * Does Teiid now do much of what this script is trying to do?
> * Can / should these transformations still be included albeit in a modified form?
> * Is this test script's purpose still appropriate for Designer?
> Requests for comments please.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1692) Old test script for updating 2 data sources, still applicable?
by Ramesh Reddy (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1692?page=com.atlassian.jira.plu... ]
Ramesh Reddy commented on TEIIDDES-1692:
----------------------------------------
Does Teiid now do much of what this script is trying to do?
It always did the execution/runtime portion of it; previously Designer was the only source of metadata; it is not the case anymore.
Is this test script's purpose still appropriate for Designer?
No. Transactions is something should be unit/integration tested with Teiid proper, not for Designer to write a test. At best the above script will work as what is designed, a end to end test, that is to be run manually for testing various different features in Designer along with Teiid.
> Old test script for updating 2 data sources, still applicable?
> --------------------------------------------------------------
>
> Key: TEIIDDES-1692
> URL: https://issues.jboss.org/browse/TEIIDDES-1692
> Project: Teiid Designer
> Issue Type: Bug
> Components: Documentation
> Reporter: Paul Richardson
> Assignee: Steven Hawkins
> Fix For: 8.2
>
> Attachments: E2eUpdateTwoSourcesTestScript.pdf
>
>
> The ['Updating Two Data Sources'|^E2eUpdateTwoSourcesTestScript.pdf] test script describes the insertion of SQL transformations for insertion and deletion of data in the underlying data sources.
> Trying to insert these transformations into Designer results in errors such as:
> {quote}
> TEIID31119 Symbol "INPUT".SUPPLIER_ID is specified with an unknown group context partsupplierView.xmi /partsupplier/views updates Problem
> {quote}
> * Does Teiid now do much of what this script is trying to do?
> * Can / should these transformations still be included albeit in a modified form?
> * Is this test script's purpose still appropriate for Designer?
> Requests for comments please.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1502) Failure to access Oracle data source with column names enclosed in double quotes
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1502?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1502 at 7/31/13 3:13 PM:
-----------------------------------------------------------------
Because the PK/FK/Index creation methods use NameInSource as the key to the column name map, these column references are not being set during processing. This is regression.
The following code change seems to work. Not sure why the NIS was being used as the key first (if exists) and column name if NIS doesn't exist. The change is to use column name all the time.
NOTE: ExcelModelProcessor.java also uses this call to locate columns for primary keys
{code:title=RelationalModelProcessorImpl.java}
protected Map createColumnMapKeyedByNames( final Table table ) {
// Build a map of the columns by their name so they can be found much more quickly ...
final Map columnsByName = new HashMap();
final Iterator iter = table.getColumns().iterator();
while (iter.hasNext()) {
final Column column = (Column)iter.next();
String columnName = column.getName();
// String columnName = column.getNameInSource();
// if (columnName == null || columnName.trim().length() == 0) {
// columnName = column.getName();
// }
columnsByName.put(columnName, column);
}
return columnsByName;
}
{code}
was (Author: blafond):
Because the PK/FK/Index creation methods use NameInSource as the key to the column name map, these column references are not being set during processing. This is regression.
The following code change seems to work. Not sure why the NIS was being used as the key first (if exists) and column name if NIS doesn't exist. The change is to use column name all the time.
{code:title=RelationalModelProcessorImpl.java}
protected Map createColumnMapKeyedByNames( final Table table ) {
// Build a map of the columns by their name so they can be found much more quickly ...
final Map columnsByName = new HashMap();
final Iterator iter = table.getColumns().iterator();
while (iter.hasNext()) {
final Column column = (Column)iter.next();
String columnName = column.getName();
// String columnName = column.getNameInSource();
// if (columnName == null || columnName.trim().length() == 0) {
// columnName = column.getName();
// }
columnsByName.put(columnName, column);
}
return columnsByName;
}
{code}
> Failure to access Oracle data source with column names enclosed in double quotes
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-1502
> URL: https://issues.jboss.org/browse/TEIIDDES-1502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7
> Reporter: Hisanobu Okuda
> Assignee: Mark Drilling
> Priority: Minor
> Fix For: 8.2
>
>
> EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when I run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error.
> {code}
> java.sql.SQLSyntaxErrorException: ORA-00922: missing or invalid option
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
> at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
> at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)
> at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)
> at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
> at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:58)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:560)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:364)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:402)
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:225)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:689)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:228)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:56)
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:184)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:207)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> {code}
> JDBC Importer should be identify this scenario and automatically enclose in double quotes, instead of we manually add double-quotes for these type of scenarios.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1811:
----------------------------------------
Could not reproduce....
I tested importing from our test BQT2 Oracle instance and was able to
* import procedure with a parameter
* delete the parameter or procure
* re-import replaced the missing parameter or procedure
* delete the parameter
* perform Metadata > Update From Source action
* parameter was replaced
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Critical
> Fix For: 8.2
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1502) Failure to access Oracle data source with column names enclosed in double quotes
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1502?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1502 at 7/31/13 1:50 PM:
-----------------------------------------------------------------
Because the PK/FK/Index creation methods use NameInSource as the key to the column name map, these column references are not being set during processing. This is regression.
The following code change seems to work. Not sure why the NIS was being used as the key first (if exists) and column name if NIS doesn't exist. The change is to use column name all the time.
{code:title=RelationalModelProcessorImpl.java}
protected Map createColumnMapKeyedByNames( final Table table ) {
// Build a map of the columns by their name so they can be found much more quickly ...
final Map columnsByName = new HashMap();
final Iterator iter = table.getColumns().iterator();
while (iter.hasNext()) {
final Column column = (Column)iter.next();
String columnName = column.getName();
// String columnName = column.getNameInSource();
// if (columnName == null || columnName.trim().length() == 0) {
// columnName = column.getName();
// }
columnsByName.put(columnName, column);
}
return columnsByName;
}
{code}
was (Author: blafond):
Because the PK/FK/Index creation methods use NameInSource as the key to the column name map, these column references are not being set during processing. This is regression.
> Failure to access Oracle data source with column names enclosed in double quotes
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-1502
> URL: https://issues.jboss.org/browse/TEIIDDES-1502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7
> Reporter: Hisanobu Okuda
> Assignee: Mark Drilling
> Priority: Minor
> Fix For: 8.2
>
>
> EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when I run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error.
> {code}
> java.sql.SQLSyntaxErrorException: ORA-00922: missing or invalid option
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
> at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
> at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)
> at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)
> at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
> at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:58)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:560)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:364)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:402)
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:225)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:689)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:228)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:56)
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:184)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:207)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> {code}
> JDBC Importer should be identify this scenario and automatically enclose in double quotes, instead of we manually add double-quotes for these type of scenarios.
--
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
10 years, 9 months
[JBoss JIRA] (TEIIDDES-1502) Failure to access Oracle data source with column names enclosed in double quotes
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1502?page=com.atlassian.jira.plu... ]
Barry LaFond reopened TEIIDDES-1502:
------------------------------------
Because the PK/FK/Index creation methods use NameInSource as the key to the column name map, these column references are not being set during processing. This is regression.
> Failure to access Oracle data source with column names enclosed in double quotes
> --------------------------------------------------------------------------------
>
> Key: TEIIDDES-1502
> URL: https://issues.jboss.org/browse/TEIIDDES-1502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.7
> Reporter: Hisanobu Okuda
> Assignee: Mark Drilling
> Priority: Minor
> Fix For: 8.2
>
>
> EDS is throwing an error when accessing Oracle data source with column names enclosed in double quotes. I am able to import the metadata, test through Datasource explorer but when I run the query against VDB, it is not interpreting correctly to send double-quotes to the column name in this case, causing below error.
> {code}
> java.sql.SQLSyntaxErrorException: ORA-00922: missing or invalid option
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
> at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
> at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
> at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
> at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
> at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
> at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
> at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)
> at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
> at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)
> at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)
> at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
> at org.jboss.resource.adapter.jdbc.CheckValidConnectionSQL.isValidConnection(CheckValidConnectionSQL.java:58)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnectionFactory.isValidConnection(BaseWrapperManagedConnectionFactory.java:560)
> at org.jboss.resource.adapter.jdbc.BaseWrapperManagedConnection.checkValid(BaseWrapperManagedConnection.java:364)
> at org.jboss.resource.adapter.jdbc.local.LocalManagedConnectionFactory.matchManagedConnections(LocalManagedConnectionFactory.java:402)
> at org.jboss.resource.connectionmanager.InternalManagedConnectionPool.getConnection(InternalManagedConnectionPool.java:225)
> at org.jboss.resource.connectionmanager.JBossManagedConnectionPool$BasePool.getConnection(JBossManagedConnectionPool.java:689)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.getManagedConnection(BaseConnectionManager2.java:404)
> at org.jboss.resource.connectionmanager.TxConnectionManager.getManagedConnection(TxConnectionManager.java:424)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2.allocateConnection(BaseConnectionManager2.java:496)
> at org.jboss.resource.connectionmanager.BaseConnectionManager2$ConnectionManagerProxy.allocateConnection(BaseConnectionManager2.java:941)
> at org.jboss.resource.adapter.jdbc.WrapperDataSource.getConnection(WrapperDataSource.java:89)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:228)
> at org.teiid.translator.jdbc.JDBCExecutionFactory.getConnection(JDBCExecutionFactory.java:56)
> at org.teiid.translator.ExecutionFactory.getConnection(ExecutionFactory.java:184)
> at org.teiid.dqp.internal.datamgr.ConnectorWorkItem.execute(ConnectorWorkItem.java:207)
> at org.teiid.dqp.internal.process.DataTierTupleSource.getResults(DataTierTupleSource.java:354)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:143)
> at org.teiid.dqp.internal.process.DataTierTupleSource$1.call(DataTierTupleSource.java:140)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
> at java.util.concurrent.FutureTask.run(FutureTask.java:138)
> at org.teiid.dqp.internal.process.DQPCore$FutureWork.run(DQPCore.java:120)
> at org.teiid.dqp.internal.process.DQPWorkContext.runInContext(DQPWorkContext.java:240)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$RunnableWrapper.run(ThreadReuseExecutor.java:122)
> at org.teiid.dqp.internal.process.ThreadReuseExecutor$3.run(ThreadReuseExecutor.java:292)
> at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
> {code}
> JDBC Importer should be identify this scenario and automatically enclose in double quotes, instead of we manually add double-quotes for these type of scenarios.
--
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
10 years, 9 months