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

[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 updated TEIIDDES-1437: ----------------------------------- Fix Version/s: 8.2 Priority: Minor (was: Major) Assignee: Barry LaFond > 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

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

by Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1617?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1617: ---------------------------------------- So, what is stopping the user from using that right now? If you are just looking pre-populated for metadata, user can easily cut/copy the view definition from source model and copy that into a view model and hack it away! Doing something like that by default seems wrong. What you are asking is way to create Base Layer based on source model where you can select choice of foreign tables. Designer already creates a way to create the base layer, I do not know if Designer lets the user select choice of tables rather than converting the whole model. If we do not have that feature that may be something Designer could do. > 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: --------------------------------------- This is also beneficial for someone that is migrating from dbms to another. > 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: --------------------------------------- I think the goal is to move the view's out of the database and into Teiid. The database view now becomes a virtual table with the transformation containing the database view. This would enable a user to get rid of their database views and push that logic into Teiid (where possible). > 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 Ramesh Reddy (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1617?page=com.atlassian.jira.plu... ] Ramesh Reddy commented on TEIIDDES-1617: ---------------------------------------- Please provide more information for the request. Teiid Designer is already capable of importing the source database's views into source model and treat that as foreign table. Then user is free to use that metadata in any other view transformation a their usecase dictates. So, I am not sure I understand the above request. > 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-1658) NPE Viewing Transformation

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1658?page=com.atlassian.jira.plu... ] Barry LaFond updated TEIIDDES-1658: ----------------------------------- Issue Type: Bug (was: Feature Request) Fix Version/s: 8.2 Assignee: Barry LaFond > NPE Viewing Transformation > -------------------------- > > Key: TEIIDDES-1658 > URL: https://issues.jboss.org/browse/TEIIDDES-1658 > Project: Teiid Designer > Issue Type: Bug > Components: Transformations > Affects Versions: 8.1 > Reporter: Ted Jones > Assignee: Barry LaFond > Fix For: 8.2 > > > Viewing/Editing a transformation for a web service model generated from WSDL without automatically generating the XML Document model results in the following NPE: > java.lang.NullPointerException > at java.util.AbstractCollection.addAll(AbstractCollection.java:303) > at org.teiid.designer.query.sql.lang.util.CommandHelper.getProjectedSymbols(CommandHelper.java:33) > at org.teiid.designer.transformation.util.TransformationSqlHelper.getProjectedSymbolNames(TransformationSqlHelper.java:1253) > at org.teiid.designer.transformation.util.TransformationMappingHelper.compareQueryTargetAndSQLOutput(TransformationMappingHelper.java:201) > at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.setMessageDisplayForValidSQL(TransformationObjectEditorPage.java:2956) > at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.setEditorMessage(TransformationObjectEditorPage.java:1436) > at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.setEditorContent(TransformationObjectEditorPage.java:1022) > at org.teiid.designer.transformation.ui.editors.TransformationObjectEditorPage.edit(TransformationObjectEditorPage.java:839) > at org.teiid.designer.webservice.ui.editor.OperationObjectEditorPage.edit(OperationObjectEditorPage.java:410) > at org.teiid.designer.ui.editors.ModelObjectEditorPanel.activateModelObjectEditor(ModelObjectEditorPanel.java:152) > at org.teiid.designer.ui.editors.MultiPageModelEditor.editModelObject(MultiPageModelEditor.java:391) > at org.teiid.designer.webservice.ui.editor.OperationEditorPage.openObjectEditor(OperationEditorPage.java:360) > at org.teiid.designer.webservice.ui.editor.OperationEditorPage.updateUi(OperationEditorPage.java:465) > at org.teiid.designer.webservice.ui.editor.OperationEditorPage$1.widgetSelected(OperationEditorPage.java:137) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4136) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1458) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1481) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1466) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1271) > at org.teiid.designer.ui.editors.MultiPageModelEditor.selectPage(MultiPageModelEditor.java:876) > at org.teiid.designer.ui.editors.ModelEditorManager$3.run(ModelEditorManager.java:181) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > ... 23 more -- 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-1679) Move Status View to lower left corner in modeler perspective

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-1679?page=com.atlassian.jira.plu... ] Barry LaFond resolved TEIIDDES-1679. ------------------------------------ Resolution: Done Done > Move Status View to lower left corner in modeler perspective > ------------------------------------------------------------ > > Key: TEIIDDES-1679 > URL: https://issues.jboss.org/browse/TEIIDDES-1679 > Project: Teiid Designer > Issue Type: Feature Request > Components: Views > Affects Versions: 8.2 > Reporter: Barry LaFond > Assignee: Barry LaFond > Fix For: 8.2 > > > Teiid Designer's Status View get's lost behind the Guides view. > It also contains very little content and may be much better suited as a monitor over in the Model Explorer. > Investigate user experience if it was in the ME and would probably require an extension contribution because Status View is defined in the advisor UI plugin. -- 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-931) Change the default to qualify name in source

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-931?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-931. ----------------------------------- Assignee: Barry LaFond (was: Mark Drilling) Resolution: Out of Date This was resolved a few releases ago. The default is to fully qualify NIS with no option to change it. > Change the default to qualify name in source > -------------------------------------------- > > Key: TEIIDDES-931 > URL: https://issues.jboss.org/browse/TEIIDDES-931 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Barry LaFond > Fix For: 8.2 > > > Fully qualified name in source entries are a safe default. Just using table names can lead to conflicts. Also using just table names prevents the costing logic from working. > It would almost be best if we didn't even offer the ability to use unqualified names. -- 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-931) Change the default to qualify name in source

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-931?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDDES-931: ----------------------------------------- There may be some confusion here. This is specifically about the name in source (are you referencing the Design/Runtime name). The default should be to qualify. Perhaps it is now given how long ago this was logged. There are very few situations where the user would want unqualified - but I would walk back the description and say that it should still be offered as an option. > Change the default to qualify name in source > -------------------------------------------- > > Key: TEIIDDES-931 > URL: https://issues.jboss.org/browse/TEIIDDES-931 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Mark Drilling > Fix For: 8.2 > > > Fully qualified name in source entries are a safe default. Just using table names can lead to conflicts. Also using just table names prevents the costing logic from working. > It would almost be best if we didn't even offer the ability to use unqualified names. -- 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-931) Change the default to qualify name in source

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-931?page=com.atlassian.jira.plug... ] Barry LaFond commented on TEIIDDES-931: --------------------------------------- Not sure I agree yet. Fully qualified Parts example: * SUPPLIER_ID : *PartsOracle11.PARTSSUPPLIER.SUPPLIER_PARTS.SUPPLIER_ID* The VDB, when used as a source, treats each Model Name as a schema, so if I had named my XMI model, PARTSSUPPLIER, then the fully qualified name would have been: * SUPPLIER_ID : *PARTSSUPPLIER.PARTSSUPPLIER.SUPPLIER_PARTS.SUPPLIER_ID* ... which reflects 2 schema containers We added this "fully qualified name" feature so Designer could handle importing from DB's with multiple schema defined, but we don't really have a good/available test case > Change the default to qualify name in source > -------------------------------------------- > > Key: TEIIDDES-931 > URL: https://issues.jboss.org/browse/TEIIDDES-931 > Project: Teiid Designer > Issue Type: Quality Risk > Components: Import/Export > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Mark Drilling > Fix For: 8.2 > > > Fully qualified name in source entries are a safe default. Just using table names can lead to conflicts. Also using just table names prevents the costing logic from working. > It would almost be best if we didn't even offer the ability to use unqualified names. -- 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