[JBoss JIRA] (TEIIDDES-2500) Problems with model created via import from Salesforce when using JOIN query
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2500?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2500:
-----------------------------------
Fix Version/s: (was: 8.6.2)
> Problems with model created via import from Salesforce when using JOIN query
> ----------------------------------------------------------------------------
>
> Key: TEIIDDES-2500
> URL: https://issues.jboss.org/browse/TEIIDDES-2500
> Project: Teiid Designer
> Issue Type: Bug
> Affects Versions: 9.0.1
> Reporter: Matus Makovy
> Assignee: Mark Drilling
> Fix For: 9.0.4, 9.2
>
> Attachments: log, salesdynamic-vdb.xml, SalesforceTD.zip
>
>
> Discovered this issue when trying to verify TEIID-3112
> I am trying to execute this query on VDB created via import from SalesForce in Teiid Designer.
> {quote}
> select distinct YEAR("Opportunity"."CloseDate") as "Opportunity_CloseDate1" from "SalesForceSource".salesforce.Campaign AS "Campaign" LEFT OUTER JOIN "SalesForceSource".salesforce.Opportunity AS "Opportunity" ON Campaign."Id" = Opportunity."CampaignId" order by YEAR("Opportunity"."CloseDate") ASC LIMIT 0 , 32
> {quote}
> And I get this exception:
> {quote}
> org.teiid.runtime.client.TeiidClientException: java.lang.RuntimeException: Remote org.teiid.core.TeiidException: Invalid QName in mapping: sf:INVALID_TYPE
> {quote}
> Log attached
> With dynamic VDB created manually or with import using Teiid Connection Importer via Designer everything works.
> Project from Designer + dynamic VDB attached
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2436) StackOverflow Exception Importing VDB via JDBC Importer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2436?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2436:
-----------------------------------
Fix Version/s: (was: 8.6.2)
(was: 8.6.2 Beta1)
> StackOverflow Exception Importing VDB via JDBC Importer
> -------------------------------------------------------
>
> Key: TEIIDDES-2436
> URL: https://issues.jboss.org/browse/TEIIDDES-2436
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Ted Jones
> Assignee: Barry LaFond
> Priority: Critical
> Fix For: 9.0.4, 9.2
>
> Attachments: import-vdb.png, JdbcImoprtObjectsPage_TEIIDDES_2436.patch
>
>
> Receiving StackOverflow exception importing a VDB via the JDBC importer using the following steps:
> 1. Import a JDBC source (any source)
> a. On page 3, select "Show Selected Schemas".
> 2. Now try importing a deployed VDB. You will receive a StackOverflow exception.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2570) RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2570?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2570:
-----------------------------------
Fix Version/s: 9.2
> RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2570
> URL: https://issues.jboss.org/browse/TEIIDDES-2570
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Paul Richardson
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> While round tripping DDL import and export, the RelationalTable is used to store table unique constraint. The DDL Importer stores the new constraints in the uniqueConstraints collection. However, when saving the model to the BasicTableImpl instance, it actually only looks at the single uniqueConstraint so values are lost.
> Dynamic Vdb work has united these fields but retained the getUniqueConstraint() and setUniqueConstraint() methods for backward compatibility with the RelationalTableEditorPanel and ViewTableEditorPanel. These methods are deprecated and the panels should be fixed to support entering multiple unique constraints.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2570) RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2570?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2570:
--------------------------------------
Assignee: Barry LaFond
> RelationalTable contains methods for single UniqueConstraint and collection of UniqueConstraints
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2570
> URL: https://issues.jboss.org/browse/TEIIDDES-2570
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.1
> Reporter: Paul Richardson
> Assignee: Barry LaFond
> Fix For: 9.2
>
>
> While round tripping DDL import and export, the RelationalTable is used to store table unique constraint. The DDL Importer stores the new constraints in the uniqueConstraints collection. However, when saving the model to the BasicTableImpl instance, it actually only looks at the single uniqueConstraint so values are lost.
> Dynamic Vdb work has united these fields but retained the getUniqueConstraint() and setUniqueConstraint() methods for backward compatibility with the RelationalTableEditorPanel and ViewTableEditorPanel. These methods are deprecated and the panels should be fixed to support entering multiple unique constraints.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months