May 2013 - teiid-designer-issues - Jboss List Archives

[JBoss JIRA] (TEIIDDES-1697) Performance bottlenecks when accessing all resources in workspace

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1697?page=com.atlassian.jira.plu... ] Paul Richardson resolved TEIIDDES-1697. --------------------------------------- Resolution: Done > Performance bottlenecks when accessing all resources in workspace > ----------------------------------------------------------------- > > Key: TEIIDDES-1697 > URL: https://issues.jboss.org/browse/TEIIDDES-1697 > Project: Teiid Designer > Issue Type: Bug > Components: Usability > Affects Versions: 8.1 > Reporter: Paul Richardson > Assignee: Paul Richardson > Fix For: 8.2 > > > A number of functions in Designer use the workspace to find all resources then analyse each one to determine whether they are designer models. This is inefficient and does not scale when the workspace contains a substantial number of projects. > Refactor the functions to require that all searched resources must be contained in the SAME project as the resource that initiated the search. > Projects that do not have the designer modelling nature should always be ignored. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1617) Capture view definition from database and apply as transformation query for viewModel table

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1617?page=com.atlassian.jira.plu... ] Steven Hawkins commented on TEIIDDES-1617: ------------------------------------------ > That's the key piece missing. But the real key to this issue is why/how often would you need it. There are two basic purposes for the view sql. One is additional metadata reporting. The other, which is the trust of this issue, is to create a Teiid view based upon the database view. The latter is by no means a common use case. You also have to contend with taking the source sql and rewriting it as valid sql for Teiid. I would think that we would want to stay away from this as a Designer feature unless there is some trust for being a general database migration tool. > Capture view definition from database and apply as transformation query for viewModel table > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1617 > URL: https://issues.jboss.org/browse/TEIIDDES-1617 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > Labels: importers > -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1617) Capture view definition from database and apply as transformation query for viewModel table

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1617?page=com.atlassian.jira.plu... ] Van Halbert commented on TEIIDDES-1617: --------------------------------------- Unfortunately, the view that Teiid builds is just built upon what columns are exposed. It doesn't include the actual dependent tables and join logic. That's the key piece missing. > Capture view definition from database and apply as transformation query for viewModel table > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1617 > URL: https://issues.jboss.org/browse/TEIIDDES-1617 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > Labels: importers > -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1617) Capture view definition from database and apply as transformation query for viewModel table

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1617?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-1617: ---------------------------------------- So a MYSQL DB has the following raw DDL {code} *CREATE TABLE product (qty INT, price INT);* *CREATE VIEW product_info (the_quantity INT, the_price INT) AS SELECT qty, price, qty*price AS value FROM product;* {code} User can access this view with : *SELECT * FROM product_info;* Through Teiid IMPORT, the TABLE DDL will look like: {code} *CREATE FOREIGN TABLE product (qty INT, price INT);* {code} What will the "product_info" view be returned as? {code} *CREATE FOREIGN TABLE product_info (the_quantity INT, the_price INT);* {code} > Capture view definition from database and apply as transformation query for viewModel table > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1617 > URL: https://issues.jboss.org/browse/TEIIDDES-1617 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > Labels: importers > -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1617) Capture view definition from database and apply as transformation query for viewModel table

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1617?page=com.atlassian.jira.plu... ] Barry LaFond edited comment on TEIIDDES-1617 at 5/1/13 5:39 PM: ---------------------------------------------------------------- So a MYSQL DB has the following raw DDL {code} CREATE TABLE product (qty INT, price INT); CREATE VIEW product_info (the_quantity INT, the_price INT) AS SELECT qty, price, qty*price AS value FROM product; {code} User can access this view with : *SELECT * FROM product_info;* Through Teiid IMPORT, the TABLE DDL will look like: {code} CREATE FOREIGN TABLE product (qty INT, price INT); {code} What will the "product_info" view be returned as? {code} CREATE FOREIGN TABLE product_info (the_quantity INT, the_price INT); {code} was (Author: blafond): So a MYSQL DB has the following raw DDL {code} *CREATE TABLE product (qty INT, price INT);* *CREATE VIEW product_info (the_quantity INT, the_price INT) AS SELECT qty, price, qty*price AS value FROM product;* {code} User can access this view with : *SELECT * FROM product_info;* Through Teiid IMPORT, the TABLE DDL will look like: {code} *CREATE FOREIGN TABLE product (qty INT, price INT);* {code} What will the "product_info" view be returned as? {code} *CREATE FOREIGN TABLE product_info (the_quantity INT, the_price INT);* {code} > Capture view definition from database and apply as transformation query for viewModel table > ------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1617 > URL: https://issues.jboss.org/browse/TEIIDDES-1617 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Tom Johnston > Labels: importers > -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1285) Deprecate and remove the ability to create a "View" table, because the "base table" does the job and it supports foreign keys

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1285?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1285: ----------------------------------- Assignee: Barry LaFond > Deprecate and remove the ability to create a "View" table, because the "base table" does the job and it supports foreign keys > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1285 > URL: https://issues.jboss.org/browse/TEIIDDES-1285 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.2 > > > The creation of a "View" table is not really useful. This is because the "Base Table" represents the same thing and it also supports foreign keys. Something the "View" table doesn't support. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1285) Deprecate and remove the ability to create a "View" table, because the "base table" does the job and it supports foreign keys

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1285?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1285: ----------------------------------- Fix Version/s: 8.2 > Deprecate and remove the ability to create a "View" table, because the "base table" does the job and it supports foreign keys > ----------------------------------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-1285 > URL: https://issues.jboss.org/browse/TEIIDDES-1285 > Project: Teiid Designer > Issue Type: Enhancement > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Van Halbert > Fix For: 8.2 > > > The creation of a "View" table is not really useful. This is because the "Base Table" represents the same thing and it also supports foreign keys. Something the "View" table doesn't support. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1417: ----------------------------------- Fix Version/s: 8.2 (was: Future) > Problems After Renaming Model Which Is A Dependency For Other Models > -------------------------------------------------------------------- > > Key: TEIIDDES-1417 > URL: https://issues.jboss.org/browse/TEIIDDES-1417 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Dan Florian > Assignee: Mark Drilling > Fix For: 8.2 > > > After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs: > Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>" > Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur. > The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found. > See forum post for more details. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1417) Problems After Renaming Model Which Is A Dependency For Other Models

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1417?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1417: ----------------------------------- Assignee: Paul Richardson (was: Mark Drilling) > Problems After Renaming Model Which Is A Dependency For Other Models > -------------------------------------------------------------------- > > Key: TEIIDDES-1417 > URL: https://issues.jboss.org/browse/TEIIDDES-1417 > Project: Teiid Designer > Issue Type: Bug > Components: Modeling > Affects Versions: 7.7.1 > Reporter: Dan Florian > Assignee: Paul Richardson > Fix For: 8.2 > > > After renaming a virtual model that is a dependency of many other models, the following error sometimes occurs: > Unresolved reference "file:/<file_path_to_base_model>/<name_of_old_base_model>" > Seems may have something to do with model object proxies and loading of models. If all the models are open in an editor, the error will not occur. However, if no editors are open, the error may occur. > The error is generated from the ResourceInScopeValidationRule class when an EMF resource cannot be found. > See forum post for more details. -- 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

12 years, 12 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1437) Status View Entries Enable Then Disable When Selecting To Enable Change Project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1437?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1437. ------------------------------------ Resolution: Done Done > Status View Entries Enable Then Disable When Selecting To Enable Change Project > ------------------------------------------------------------------------------- > > Key: TEIIDDES-1437 > URL: https://issues.jboss.org/browse/TEIIDDES-1437 > Project: Teiid Designer > Issue Type: Bug > Components: Views > Affects Versions: 7.8 > Environment: OS X 10.7.4, Teiid Designer 7.8, Eclipse Java EE Indigo Release 2 > Reporter: Dan Florian > Assignee: Barry LaFond > Priority: Minor > Fix For: 8.2 > > > Using an empty workspace (no Designer projects), opened Teiid Designer perspective. In Status View, when going from unchecked to checked state in the "Enable Change Project" checkbox, the category/subject entry labels (like Sources, XML Schemas), enable then a second later disable. Since they are already disabled before checking the box, there is no need for them to be temporarily enabled. -- 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

12 years, 12 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2013