[JBoss JIRA] (TEIIDDES-2467) Query Results Table Hides Query Results
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2467?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2467:
-----------------------------------
Fix Version/s: 9.2
9.0.3
(was: 8.6.2)
(was: 9.1)
(was: 9.0.2)
> Query Results Table Hides Query Results
> ---------------------------------------
>
> Key: TEIIDDES-2467
> URL: https://issues.jboss.org/browse/TEIIDDES-2467
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0
> Reporter: Debbie Steigner
> Fix For: 9.2, 9.0.3
>
>
> The query results table hides results for queries that have a number of rows that would fit inside of the window. After a query was updated, the Result hides the first row, and the user can not scroll up to see that row.
> This appears to occur on tables where the number of rows will all fit within the view without scrolling. In these situations the results are available only by clicking on the result tab content and scrolling up with the keyboard. Scrolling with the mouse does not work to show these hidden rows.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2460) JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2460?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2460:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> JDBC Importer changes integer type to biginteger type when importing schema (reusing) from VDB
> -----------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2460
> URL: https://issues.jboss.org/browse/TEIIDDES-2460
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Barry LaFond
> Assignee: Mark Drilling
> Fix For: 9.2, 9.0.3
>
> Attachments: ErrorDialog.png
>
>
> When the JDBC importer is used to import a schema from an existing VDB integer types will be converted into biginterger types. This error is similar to Bug 1026892 except no exception is raised
> Version-Release number of selected component (if applicable):
> Actual results:
> Imported schema has changed integer data type to biginteger data type.
> Expected results:
> Imported schema will be identical to original schema.
> Additional info:
> Imported schema is so long as the JPA entity reflects the biginteger type. This is problematic because now two separate JPA entities are needed, one for the original schema and another for the imported schema.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[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: 9.2
(was: 9.1)
> 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: 8.6.2, 9.2, 9.0.3
>
> 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, 5 months
[JBoss JIRA] (TEIIDDES-2398) Inconsistent column datatypes when importing
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2398?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2398:
-----------------------------------
Fix Version/s: 9.2
(was: 9.1)
> Inconsistent column datatypes when importing
> --------------------------------------------
>
> Key: TEIIDDES-2398
> URL: https://issues.jboss.org/browse/TEIIDDES-2398
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Modeling
> Reporter: Andrej Šmigala
> Assignee: Mark Drilling
> Fix For: 8.6.2, 9.2, 9.0.3
>
> Attachments: datatypes.png, MySQL_BQT_DDL.ddl
>
>
> There are multiple discrepancies in the column datatypes when importing using JDBC importer vs when using Teiid Connection importer.
> Also some of the imported datatypes seem completely wrong (e.g. bigdecimal for almost all numeric datatypes in oracle)
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months