[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.3
(was: 9.2)
(was: 9.0.3)
> 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.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, 8 months
[JBoss JIRA] (TEIIDDES-2524) Enable DDL importer to import Teiid CREATE VIRTUAL PROCEDURE DDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2524?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2524:
-----------------------------------
Fix Version/s: 9.3
(was: 9.2)
(was: 9.0.3)
> Enable DDL importer to import Teiid CREATE VIRTUAL PROCEDURE DDL
> ----------------------------------------------------------------
>
> Key: TEIIDDES-2524
> URL: https://issues.jboss.org/browse/TEIIDDES-2524
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Import/Export
> Reporter: Barry LaFond
> Fix For: 9.3
>
> Attachments: TEIIDDES-2524_work_in_progress.zip
>
>
> in 9.1, we've added ability to set SQL for imported *CREATE VIEW ....* ddl via ddl importer.
> for 9.2 we'll add ability to import *CREATE VIRTUAL PROCEDURE...* ddl.
> This case is a little more complex since the SQL defined in a procedure transformation will include just the BEGIN .... END part of the SQL, so there's an additional step required to extract the relevant SQL string and apply it to the transformation
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2579) Salesforce custom URL not getting pushed to DV runtime upon PREVIEW
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2579?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2579:
--------------------------------------
Assignee: Mark Drilling (was: Barry LaFond)
> Salesforce custom URL not getting pushed to DV runtime upon PREVIEW
> -------------------------------------------------------------------
>
> Key: TEIIDDES-2579
> URL: https://issues.jboss.org/browse/TEIIDDES-2579
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0.1
> Reporter: Debbie Steigner
> Assignee: Mark Drilling
> Fix For: 9.2, 9.0.3
>
>
> The Teiid Designer in JBDS 8.x lets you create a connection to Salesforce and provides an option to define a custom URL if its different from the default one.
> After the metadata for one or more tables have been imported, if one chooses to do a 'Preview Data' on one of the tables imported. There are issues as the Preview version of the resource adapter is missing the following URL config property and attempts to connect to the default/implicit SF URL.
> <config-property type="java.lang.String" name="URL"></config-property>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2579) Salesforce custom URL not getting pushed to DV runtime upon PREVIEW
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2579?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2579:
-----------------------------------
Fix Version/s: 9.2
9.0.3
> Salesforce custom URL not getting pushed to DV runtime upon PREVIEW
> -------------------------------------------------------------------
>
> Key: TEIIDDES-2579
> URL: https://issues.jboss.org/browse/TEIIDDES-2579
> Project: Teiid Designer
> Issue Type: Bug
> Components: Data Preview
> Affects Versions: 9.0.1
> Reporter: Debbie Steigner
> Assignee: Barry LaFond
> Fix For: 9.2, 9.0.3
>
>
> The Teiid Designer in JBDS 8.x lets you create a connection to Salesforce and provides an option to define a custom URL if its different from the default one.
> After the metadata for one or more tables have been imported, if one chooses to do a 'Preview Data' on one of the tables imported. There are issues as the Preview version of the resource adapter is missing the following URL config property and attempts to connect to the default/implicit SF URL.
> <config-property type="java.lang.String" name="URL"></config-property>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2422) XSD model created in wrong folder when creating Web service model from WSDL
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2422?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-2422.
------------------------------------
Fix Version/s: 9.2
Resolution: Done
> XSD model created in wrong folder when creating Web service model from WSDL
> ---------------------------------------------------------------------------
>
> Key: TEIIDDES-2422
> URL: https://issues.jboss.org/browse/TEIIDDES-2422
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Reporter: Andrej Šmigala
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 8.6.2 Beta1, 8.6.2, 9.2, 9.0.3
>
>
> When creating a Web Service model from an existing WSDL, there is an option to change the target location of the imported xml schema. Changing this location however results in the schema model being created in the wrong folder.
> Expected result:
> The XML and Web Service models are created in the 'web_services' subfolder, the XSD model is created in the 'schemas' subfolder.
> Actual result:
> The XML and Web Service models are created in the 'web_services' subfolder, but the XSD model is created in 'web_services/schemas' subfolder.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2248:
----------------------------------------
[~elvisisking] Dan, can you check into this? I know you fixed some MS parsing issues with quotes, so maybe it'll be fixed in upcoming MS release version?
> Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2248
> URL: https://issues.jboss.org/browse/TEIIDDES-2248
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.3.3
> Environment: Teiid Designer 8.3.3
> Teiid 8.4.1-redhat-7
> Reporter: Andrej Šmigala
> Assignee: Dan Florian
> Fix For: 9.2
>
> Attachments: screen-1.png
>
>
> Create a table with
> {code:sql}
> CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' )
> {code}
> When trying to import it through Teiid Connection Importer, the importer DDL is shown as
> {code:sql}
> CREATE FOREIGN TABLE "dballo00.dbo.t1" (
> c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar')
> ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0);
> {code}
> but on the next page, the following error is shown (see screenshot):
> The DDL failed to parse with message: "Unparsable table body".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months
[JBoss JIRA] (TEIIDDES-2248) Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2248?page=com.atlassian.jira.plu... ]
Barry LaFond reassigned TEIIDDES-2248:
--------------------------------------
Assignee: Dan Florian (was: Barry LaFond)
> Teiid Connection import fails to parse DDL when table contains VARCHAR column with DEFAULT value
> ------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-2248
> URL: https://issues.jboss.org/browse/TEIIDDES-2248
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export, Teiid Integration
> Affects Versions: 8.3.3
> Environment: Teiid Designer 8.3.3
> Teiid 8.4.1-redhat-7
> Reporter: Andrej Šmigala
> Assignee: Dan Florian
> Fix For: 9.2
>
> Attachments: screen-1.png
>
>
> Create a table with
> {code:sql}
> CREATE TABLE t1 ( c1 VARCHAR(10) DEFAULT 'c1' )
> {code}
> When trying to import it through Teiid Connection Importer, the importer DDL is shown as
> {code:sql}
> CREATE FOREIGN TABLE "dballo00.dbo.t1" (
> c1 string(10) DEFAULT '(''c1'')' OPTIONS (NAMEINSOURCE '"c1"', NATIVE_TYPE 'varchar')
> ) OPTIONS (NAMEINSOURCE '"dballo00"."dbo"."t1"', UPDATABLE TRUE, CARDINALITY 0);
> {code}
> but on the next page, the following error is shown (see screenshot):
> The DDL failed to parse with message: "Unparsable table body".
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 8 months