February 2010 - teiid-designer-issues

[JBoss JIRA] Moved: (TEIIDDES-352) XML document preview returns relational results--if any

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-352?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-579 to TEIIDDES-352: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-352 (was: JBEDSP-579) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > XML document preview returns relational results--if any > ------------------------------------------------------- > > Key: TEIIDDES-352 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-352 > Project: Teiid Designer > Issue Type: Task > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > > (Yeah, I know we're disabling this feature, but later on this could be an issue!) > I added an XML document model to the Parts project. that's what I used to test this feature. > if there are no existing previews in the preview tab and I preview the document, I am asked if I want to save the results to a file. Selecting yes, I get nothing and the preview window contains: > XML query results too large. > Save was cancelled. > No results displayed. > If I have already previewed a relation table and try to preview the XML doc, it gives me the same "save as a file" dialog and then a file chooser so I can name my file and choose its location. When finished, it saved the RELATIONAL preview in the specified file. No XML doc saved! > [Added Stuff] I just noticed that, despite the errors, if I click the "save query results to file" button, it does, in fact, save the results, even though they were not displayed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-349) Provide way to export or save data from Designer's "Compare with..." operation

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-349?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-550 to TEIIDDES-349: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-349 (was: JBEDSP-550) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.2) (was: 5.5.1) (was: 5.5) > Provide way to export or save data from Designer's "Compare with..." operation > ------------------------------------------------------------------------------ > > Key: TEIIDDES-349 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-349 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > Assignee: Barry LaFond > > Per client request in I-T #198888: > ---------------------------- > When generating a model difference list (using the "Compare with..." menu option), it would be very useful to be able to save or output (i.e., print out) the information shown, to help preserve change information as part of CM. Especially when the user has no control on the source schema. > ---------------------------- > The use case provided is to compare an updated source schema and modify model details as appropriate. The users have no control and very little notification when schemas change on their data sources. Currently, they do a separate import on the new source, and modify their models appropriately as needed. However, they are required to flip back to the results page of the "Compare with..." operation to reference the changes. They are requesting a way to save/export this information, as currently the only option is to do screen prints. The preferrable method would probably be an XML doc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-350) Designer: Add capability to export / import a workspace for migrations.

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-350?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-562 to TEIIDDES-350: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-350 (was: JBEDSP-562) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Designer: Add capability to export / import a workspace for migrations. > ----------------------------------------------------------------------- > > Key: TEIIDDES-350 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-350 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Mark Drilling > Assignee: Barry LaFond > > This capability would allow a user to easily upgrade their Designer version without losing anything. The workspace export/import would bring along projects, preferences, connector bindings, extension jars, etc. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-351) Actions in Designer should be 'view sensitive' - needs review

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-351?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-575 to TEIIDDES-351: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-351 (was: JBEDSP-575) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Actions in Designer should be 'view sensitive' - needs review > ------------------------------------------------------------- > > Key: TEIIDDES-351 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-351 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Mark Drilling > Assignee: Barry LaFond > > This was brought up following the Designer usability demo. The 'Preview' action is used in multiple views in Designer. However it's selection is driven by workspace selection, not just the selection of the view(s) in which it appears. This should be reviewed / discussed. There are other actions that act similarly. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-348) Bidirectional Dependency Diagram

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-348?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-526 to TEIIDDES-348: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-348 (was: JBEDSP-526) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.2) > Bidirectional Dependency Diagram > -------------------------------- > > Key: TEIIDDES-348 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-348 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Debbie Steigner > Assignee: Barry LaFond > > Enhancement Request Issue Tracker # 195371 > I know that the MetaMatric Designer can show all the models a specific view is dependent on. > What would be nice is to be able to generate a dependency diagram showing all the views that depend on a specific model. > This feature would be very helpful when managing changes in a view and tracking how it affects the rest of the models. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-347) NPE (unhandled event loop exception) when trying to build a sub-datatype (Simple Datatypes Editor)

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-347?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-254 to TEIIDDES-347: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-347 (was: JBEDSP-254) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: Westport) > NPE (unhandled event loop exception) when trying to build a sub-datatype (Simple Datatypes Editor) > -------------------------------------------------------------------------------------------------- > > Key: TEIIDDES-347 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-347 > Project: Teiid Designer > Issue Type: Task > Environment: Linux > Reporter: Paul Nittel > Assignee: Barry LaFond > Attachments: SubTypeNpe.txt > > > I'm following the E2E XSD Simple Datatypes Editor Test Script... > To build a sub-type, I choose the Boolean built-in type then click the Create subtype of this Datatype hyperlink. The stack trace is attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-345) More accurate importing of JDBC numeric types

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-345?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-1174 to TEIIDDES-345: ---------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-345 (was: JBEDSP-1174) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.2) > More accurate importing of JDBC numeric types > --------------------------------------------- > > Key: TEIIDDES-345 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-345 > Project: Teiid Designer > Issue Type: Bug > Reporter: Marc Shirley > > sometimes we import fixed precision source types as floats and vice versa -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-346) Restore Designer "Problems" view functionality

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-346?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-224 to TEIIDDES-346: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-346 (was: JBEDSP-224) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5.3) > Restore Designer "Problems" view functionality > ---------------------------------------------- > > Key: TEIIDDES-346 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-346 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Barry LaFond > > Restore Designer "Problems" view characteristics > We had to remove the Modeler Problems view and rely on generic Eclipse Problems view. This includes implementing interfaces like IShowInSource, IShowInTarget, IShowInTargetList. This framework utilizes getAdapter()'s. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-343) Inclusion of Data Flows

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-343?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-163 to TEIIDDES-343: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-343 (was: JBEDSP-163) Component/s: (was: Designer) (was: Query) Fix Version/s: (was: Future Versions) > Inclusion of Data Flows > ----------------------- > > Key: TEIIDDES-343 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-343 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > > case 4879 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

[JBoss JIRA] Moved: (TEIIDDES-344) Transformation editor in Designer should support comments and preserve user formatting

by Van Halbert (JIRA)

[ https://jira.jboss.org/jira/browse/TEIIDDES-344?page=com.atlassian.jira.p... ] Van Halbert moved JBEDSP-124 to TEIIDDES-344: --------------------------------------------- Project: Teiid Designer (was: JBoss Enterprise Data Services Platform) Key: TEIIDDES-344 (was: JBEDSP-124) Component/s: (was: Designer) Fix Version/s: (was: Future Versions) Affects Version/s: (was: 5.5) > Transformation editor in Designer should support comments and preserve user formatting > -------------------------------------------------------------------------------------- > > Key: TEIIDDES-344 > URL: https://jira.jboss.org/jira/browse/TEIIDDES-344 > Project: Teiid Designer > Issue Type: Feature Request > Reporter: Marc Shirley > > We should support the ability to put comments into transformation code. This is especially useful for virtual procedures, which can get complicated, and could benefit from comments. It also comes up when bringing in SQL code from another environment (e.g. a view from Oracle) -- it would be nice to be able to preserve the comments from the original environment. > It would be nice to support comments prefixed by "--", such as in Oracle. I believe this is standard SQL-92, so we should support it as well. > ------------------- > Fix the designer transformation window, so that it actually saves what the user types (keep formatting, allow comments, etc.). This should really be one of the standard Eclipse text editing windows - MM specific stuff (other than syntax highlighting) should be decoupled from the edit window - there are a couple of requests from ING on this. > ------------------- > As Designer is treated like any other development environment and may have multiple developers working on the same project set, it is very important that comments be supported within the transformations. Although it might be helpful, it is not necessary that these comments get pushed out to source. These comments would be primarily used for developer references. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

teiid-designer-issues February 2010