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

[JBoss JIRA] (TEIIDDES-2138) Restrict "New VDB" wizard's "Add model" to the current project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2138?page=com.atlassian.jira.plu... ] Barry LaFond reassigned TEIIDDES-2138: -------------------------------------- Assignee: Barry LaFond > Restrict "New VDB" wizard's "Add model" to the current project > -------------------------------------------------------------- > > Key: TEIIDDES-2138 > URL: https://issues.jboss.org/browse/TEIIDDES-2138 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 8.3.1 > Reporter: Marc Shirley > Assignee: Barry LaFond > Fix For: 8.5, 8.3.3 > > > New VDB wizard behavior should be the same as the edit VDB behavior and restrict model selection to only the current project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2138) Restrict "New VDB" wizard's "Add model" to the current project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2138?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2138: ----------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/commit/48602eaec24df6b14... * Filtering model selector dialog to existing project if selected at launch * Preventing selecting models from different projects if project not yet set. > Restrict "New VDB" wizard's "Add model" to the current project > -------------------------------------------------------------- > > Key: TEIIDDES-2138 > URL: https://issues.jboss.org/browse/TEIIDDES-2138 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 8.3.1 > Reporter: Marc Shirley > Fix For: 8.3.3 > > > New VDB wizard behavior should be the same as the edit VDB behavior and restrict model selection to only the current project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2138) Restrict "New VDB" wizard's "Add model" to the current project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2138?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2138: ----------------------------------- Fix Version/s: 8.5 > Restrict "New VDB" wizard's "Add model" to the current project > -------------------------------------------------------------- > > Key: TEIIDDES-2138 > URL: https://issues.jboss.org/browse/TEIIDDES-2138 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 8.3.1 > Reporter: Marc Shirley > Fix For: 8.5, 8.3.3 > > > New VDB wizard behavior should be the same as the edit VDB behavior and restrict model selection to only the current project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2138) Restrict "New VDB" wizard's "Add model" to the current project

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2138?page=com.atlassian.jira.plu... ] Barry LaFond commented on TEIIDDES-2138: ---------------------------------------- There are some complexities with this issue.... * New VDB wizard can be launched either with or without a workspace resource selected. * If NO selection ** then the location of the VDB is undefined and therefore the *Add* models action can't be scoped to a single project. ** user can select to add models from different projects (dynamically preventing this in the tree will be difficult) *** Easier to validate during selection and error out (models selected from different projects > Restrict "New VDB" wizard's "Add model" to the current project > -------------------------------------------------------------- > > Key: TEIIDDES-2138 > URL: https://issues.jboss.org/browse/TEIIDDES-2138 > Project: Teiid Designer > Issue Type: Feature Request > Components: VDB & Execution > Affects Versions: 8.3.1 > Reporter: Marc Shirley > Fix For: 8.3.3 > > > New VDB wizard behavior should be the same as the edit VDB behavior and restrict model selection to only the current project. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2127) Problem with SF import using Teiid Connection importer - keys not resolved

by Mark Drilling (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2127?page=com.atlassian.jira.plu... ] Mark Drilling commented on TEIIDDES-2127: ----------------------------------------- I logged the linked JIRA. This would fix the key resolution without any changes on Designer side, but we would still need special handling to support 8.7. What will you revert - the schema qualified names? > Problem with SF import using Teiid Connection importer - keys not resolved > -------------------------------------------------------------------------- > > Key: TEIIDDES-2127 > URL: https://issues.jboss.org/browse/TEIIDDES-2127 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: exportedDDL-DV6.ddl, exportedDDL-Teiid87.ddl > > > There is a problem with Salesforce import using the Teiid Connection importer in Designer 8.5 when connecting to a teiid 8.7 instance - the keys are not getting resolved, resulting in numerous model errors after import. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2112) Need to correct the generated MySQL DDL for Primary Keys

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2112?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-2112. ------------------------------------ Resolution: Done added check in MYSQL xslt for PK's named "PRIMARY" and use the alternate ADD PRIMARY KEY and skip ADD CONSTRAINT Done > Need to correct the generated MySQL DDL for Primary Keys > -------------------------------------------------------- > > Key: TEIIDDES-2112 > URL: https://issues.jboss.org/browse/TEIIDDES-2112 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.5 > > > The generated DDL for MySQL primary keys needs to be adjusted to account for the case where the user names their PK to PRIMARY. > We currently generate DDL of the following form for MySQL > ALTER TABLE <tableName> > ADD CONSTRAINT <pkName> > PRIMARY KEY (<colName>); > For a key named PRIMARY this results in DDL that fails on MySQL. We should change the form for MySQL to be > ALTER TABLE <tableName> ADD PRIMARY KEY (<colName>); > On MySQL the PK is forced to be named PRIMARY, so its not possible to set the name anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2112) Need to correct the generated MySQL DDL for Primary Keys

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2112?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2112: ----------------------------------- Git Pull Request: https://github.com/Teiid-Designer/teiid-designer/commit/4ec6aadab8c43f033... > Need to correct the generated MySQL DDL for Primary Keys > -------------------------------------------------------- > > Key: TEIIDDES-2112 > URL: https://issues.jboss.org/browse/TEIIDDES-2112 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.4 > Reporter: Mark Drilling > Assignee: Barry LaFond > Fix For: 8.5 > > > The generated DDL for MySQL primary keys needs to be adjusted to account for the case where the user names their PK to PRIMARY. > We currently generate DDL of the following form for MySQL > ALTER TABLE <tableName> > ADD CONSTRAINT <pkName> > PRIMARY KEY (<colName>); > For a key named PRIMARY this results in DDL that fails on MySQL. We should change the form for MySQL to be > ALTER TABLE <tableName> ADD PRIMARY KEY (<colName>); > On MySQL the PK is forced to be named PRIMARY, so its not possible to set the name anyway. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2127) Problem with SF import using Teiid Connection importer - keys not resolved

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2127?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-2127: ---------------------------------------- This will be a Teiid bug, I switched it around in 8.7, which not really needed. I will revert it back. BTW, none of these properties are in use by the transalator. The translator defines them but never uses it for anything, so they as good as not being there. Also, I thought Designer has separate importer for SF? > Problem with SF import using Teiid Connection importer - keys not resolved > -------------------------------------------------------------------------- > > Key: TEIIDDES-2127 > URL: https://issues.jboss.org/browse/TEIIDDES-2127 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export > Affects Versions: 8.5 > Reporter: Mark Drilling > Assignee: Mark Drilling > Fix For: 8.5 > > Attachments: exportedDDL-DV6.ddl, exportedDDL-Teiid87.ddl > > > There is a problem with Salesforce import using the Teiid Connection importer in Designer 8.5 when connecting to a teiid 8.7 instance - the keys are not getting resolved, resulting in numerous model errors after import. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-2050) Full Temp Table support in Designer

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-2050?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-2050: ----------------------------------- Fix Version/s: Future (was: 8.5) > Full Temp Table support in Designer > ----------------------------------- > > Key: TEIIDDES-2050 > URL: https://issues.jboss.org/browse/TEIIDDES-2050 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: Future > > > Per TEIIDDES-1794 there are more areas Designer needs to add support for temporary tables: > ... the full array of temp table stuff we currently support is: > * Teiid global temporary table (a virtual entry - which from an engine perspective can be on any model type) > * Teiid temporary table (not a schema entry in the design time metadata, scoped to a session/block) > * Teiid temporary table backed by a physical table (not a schema entry in the design time metadata, scoped to a session/block - the physical table could be a temporary one) > Eventually we would also like to have an ease of use path to simply create a teiid temporary table and have the backing table created on a source automatically - similar to the data shipment join temporary table creation. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

[JBoss JIRA] (TEIIDDES-1732) Stream line steps to implement all the steps around materialization

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1732?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1732: ----------------------------------- Fix Version/s: 8.6 (was: 8.5) > Stream line steps to implement all the steps around materialization > -------------------------------------------------------------------- > > Key: TEIIDDES-1732 > URL: https://issues.jboss.org/browse/TEIIDDES-1732 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 8.2 > Reporter: Van Halbert > Assignee: Barry LaFond > Fix For: 8.6 > > > Would like to stream line the steps to putting materialization to work. Example: > - Right mouse click on view, select materialization > - present wizard to walk thru the following options: > - create physical table based on selected view/table (export/import of ddl is supported, but would like the table automatically created) > - put name of mat table into the selected table/view to be materialized > - [optional] export DDL (file system or clipboard) > - [optional] create procedure that has the "select into" for refreshing > Having the procedure provides the immediate ability to call to refresh, without having to remember what tables. Also, with the feature of native queries, could add the truncate call to clear the table. > Once thru this wizard, (I think) everything is in place to do materialization for the specified table. -- This message was sent by Atlassian JIRA (v6.2.3#6260)

10 years, 8 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues May 2014