[JBoss JIRA] (TEIIDDES-2502) Incorrect transformation reconciliation
by Tom Johnston (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2502?page=com.atlassian.jira.plu... ]
Tom Johnston commented on TEIIDDES-2502:
----------------------------------------
Van, you are correct.
The copy/paste issue was simply when logging the issue.
What I was loging was the invalid sql that resulted from a valid sql being entered as a transformation sql.
> Incorrect transformation reconciliation
> ---------------------------------------
>
> Key: TEIIDDES-2502
> URL: https://issues.jboss.org/browse/TEIIDDES-2502
> Project: Teiid Designer
> Issue Type: Bug
> Components: Modeling, Transformations
> Affects Versions: 9.0.1
> Environment: 9.0.1.Final-v20150211-1407-B643
> JBDS / Designer on Windows
> Reporter: Tom Johnston
> Assignee: Barry LaFond
>
> SELECT
> proj.\*, act.\*, cm.Field_Num, cm.Identity_Token, f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN Table2 AS proj ON proj.Field_ID = act.Field_ID) LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> "resolves"
> to:
> SELECT
> Table2 AS proj.\*,
> Table1 AS act.\*, cm.Field_Num, cm.Identity_Token,
> f.Plant_Num
> FROM
> ((Table1 AS act LEFT OUTER JOIN
> Table2 AS proj ON proj.Field_ID = act.Field_ID)
> LEFT OUTER JOIN Table3 AS f ON f.Field_ID = act.Field_ID) INNER JOIN
> Table4 AS cm ON cm.Contract_ID = f.Contract_ID
> ORDER BY act.Crop_Year
> with error:
> ERROR: Error in parsing of sql - Encountered " <ALL_IN_GROUP> "proj.\* "" at
> line 2, column 54.
> Was expecting one of:
> "instead" ...
> "enabled" ...
> "disabled" ...
> "view" ...
> "key" ...
> "serial" ...
> "textagg" ...
> "count" ...
> "row_number" ...
> "rank" ...
> "dense_rank" ...
> "sum" ...
> "avg" ...
> "min" ...
> "max" ...
> "every" ...
> "stddev_pop" ...
> "stddev_samp" ...
> "var_samp" ...
> "var_pop" ...
> "document" ...
> "content" ...
> "trim" ...
> "empty" ...
> "ordinality" ...
> "path" ...
> "first" ...
> "last" ...
> "next" ...
> "substring" ...
> "extract" ...
> "to_chars" ...
> "to_bytes" ...
> "timestampadd" ...
> "timestampdiff" ...
> "querystring" ...
> "namespace" ...
> "result" ...
> "index" ...
> "accesspattern" ...
> "auto_increment" ...
> "wellformed" ...
> "sql_tsi_frac_second" ...
> "sql_tsi_second" ...
> "sql_tsi_minute" ...
> "sql_tsi_hour" ...
> "sql_tsi_day" ...
> "sql_tsi_week" ...
> "sql_tsi_month" ...
> "sql_tsi_quarter" ...
> "sql_tsi_year" ...
> "texttable" ...
> "arraytable" ...
> "selector" ...
> "skip" ...
> "width" ...
> "passing" ...
> "name" ...
> "encoding" ...
> "columns" ...
> "delimiter" ...
> "quote" ...
> "header" ...
> "nulls" ...
> "objecttable" ...
> "version" ...
> "including" ...
> "excluding" ...
> "xmldeclaration" ...
> "variadic" ...
> "exception" ...
> "raise" ...
> "chain" ...
> "jsonarray_agg" ...
> "jsonobject" ...
> <ID> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2522) VDB Role Editor does not show when added
by Ehsanullah Jan (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2522?page=com.atlassian.jira.plu... ]
Ehsanullah Jan commented on TEIIDDES-2522:
------------------------------------------
The roles grid (or pretty much any grid for that matter) that has more than one items and that is sized such that no scroll bars are visible (or needed) will not show the first item.
This gets very confusing because you'd wonder where did the role go that I just added a few minutes ago. But if you select any of the visible entries in the grid and then use your cursor keys, you'll be able to show the 'invisible' first item in the grid.
It might be a Mac-specific issue.
> VDB Role Editor does not show when added
> ----------------------------------------
>
> Key: TEIIDDES-2522
> URL: https://issues.jboss.org/browse/TEIIDDES-2522
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 9.0
> Environment: Mac
> JBDS Version: 8.0.0.GA
> Build id: GA-v20141020-1042-B317
> Teiid Designer version: 9.0.1.Final-v20150211-1407-B643
> Reporter: Marc Shirley
>
> Newly added roles do not show up, but instead require the editor to be switched off of the Role view and then back to the Role view in order to view changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2522) VDB Role Editor does not show when added
by Marc Shirley (JIRA)
Marc Shirley created TEIIDDES-2522:
--------------------------------------
Summary: VDB Role Editor does not show when added
Key: TEIIDDES-2522
URL: https://issues.jboss.org/browse/TEIIDDES-2522
Project: Teiid Designer
Issue Type: Bug
Components: VDB & Execution
Affects Versions: 9.0
Environment: Mac
JBDS Version: 8.0.0.GA
Build id: GA-v20141020-1042-B317
Teiid Designer version: 9.0.1.Final-v20150211-1407-B643
Reporter: Marc Shirley
Newly added roles do not show up, but instead require the editor to be switched off of the Role view and then back to the Role view in order to view changes.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2520) Teiid Connection Import fails when model name is set before model location
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2520?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-2520:
----------------------------------------
* Added logic to re-set model name when project changed. This forces re-setting of the model's full path file name, which includes project folder
* Added check to ignore cancelled project selection dialog
* Added panel scrolling to importer pages : Fixed in conjunction with scrolled panel improvements for TEIIDDES-2501 for the Teiid Connection Importer wizard pages
master:
9.0.x: https://github.com/Teiid-Designer/teiid-designer/commit/244792ffd37b2b7f6...
> Teiid Connection Import fails when model name is set before model location
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2520
> URL: https://issues.jboss.org/browse/TEIIDDES-2520
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.2 Beta1
> Reporter: Andrej Šmigala
> Fix For: 9.1, 9.0.2 Beta2, 9.0.2
>
>
> When going through the Teiid Connection Import wizard, setting model name before selecting the model project on the _Select the target model for the import_ page causes the import to fail. This happens when no model project was previously selected.
> When a model project is already selected, changing the model project on that page, after setting the model name, causes the new model to be created in the wrong project.
> Selecting the model project first and then setting the model name does not cause any of these issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2520) Teiid Connection Import fails when model name is set before model location
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-2520?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-2520:
-----------------------------------
Fix Version/s: 9.1
9.0.2 Beta2
9.0.2
> Teiid Connection Import fails when model name is set before model location
> --------------------------------------------------------------------------
>
> Key: TEIIDDES-2520
> URL: https://issues.jboss.org/browse/TEIIDDES-2520
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 9.0.2 Beta1
> Reporter: Andrej Šmigala
> Fix For: 9.1, 9.0.2 Beta2, 9.0.2
>
>
> When going through the Teiid Connection Import wizard, setting model name before selecting the model project on the _Select the target model for the import_ page causes the import to fail. This happens when no model project was previously selected.
> When a model project is already selected, changing the model project on that page, after setting the model name, causes the new model to be created in the wrong project.
> Selecting the model project first and then setting the model name does not cause any of these issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2521) Model unresolved reference errors upon import of previously working project
by Marc Shirley (JIRA)
Marc Shirley created TEIIDDES-2521:
--------------------------------------
Summary: Model unresolved reference errors upon import of previously working project
Key: TEIIDDES-2521
URL: https://issues.jboss.org/browse/TEIIDDES-2521
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 9.0
Environment: JBDS Version: 8.0.0.GA
Build id: GA-v20141020-1042-B317
Teiid Designer version: 9.0.1.Final-v20150211-1407-B643
Reporter: Marc Shirley
Importing a model set from a previous version results in large number of errors like example [1] due to broken references. In one example set there were 900+ of these errors related to 3 model files. To correct, the model files need to have Edit -> Modeling -> Validate Transformations action run on each model individually.
[1] Sql transformation in the model mymodel1 contains the unresolved reference file:/C:/jbdevstudio/8.1.0.GA/workspaces/mymodel2.xmi
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months
[JBoss JIRA] (TEIIDDES-2520) Teiid Connection Import fails when model name is set before model location
by Andrej Šmigala (JIRA)
Andrej Šmigala created TEIIDDES-2520:
----------------------------------------
Summary: Teiid Connection Import fails when model name is set before model location
Key: TEIIDDES-2520
URL: https://issues.jboss.org/browse/TEIIDDES-2520
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 9.0.2 Beta1
Reporter: Andrej Šmigala
When going through the Teiid Connection Import wizard, setting model name before selecting the model project on the _Select the target model for the import_ page causes the import to fail. This happens when no model project was previously selected.
When a model project is already selected, changing the model project on that page, after setting the model name, causes the new model to be created in the wrong project.
Selecting the model project first and then setting the model name does not cause any of these issues.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 5 months