February 2011 - teiid-designer-issues

[JBoss JIRA] Created: (TEIIDDES-887) Changing validation preference (i.e. Relational) forces a re-build but validation does not pick up changed preference

by Barry LaFond (JIRA)

Changing validation preference (i.e. Relational) forces a re-build but validation does not pick up changed preference --------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-887 URL: https://issues.jboss.org/browse/TEIIDDES-887 Project: Teiid Designer Issue Type: Bug Components: Modeling, Validation Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.4 While adding/testing new validation rules and validation preferences it became apparent that there is a timing/event issue with changing preferences and the auto-build that's kicked off when user APPLY's or hits OK 1) Create simple relational model with table and one column with datatype decimal with "0" precision 2) Saving/validation should result in "Missing or invalid precision" WARNING 3) Edit Preferences > TEiid Designer > Validation and open "Relational" tab. 4) Change the "Missing precision property on columns with numeric types:" value to "ERROR" 5) Hit OK 6) Choose YES to FULL REBUILD 7) ERROR is not created in problems view I Stepped through this in DEBUG and the ERROR DID get created. Seems the validation preference is NOT getting set/changed prior the the validation logic requesting current value. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-292) WSDL to Relational Importer should be smarter about column names.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-292?page=com.atlassian.jira.plug... ] John Doyle resolved TEIIDDES-292. --------------------------------- Labels: (was: wsdltorelational) Fix Version/s: 7.3 7.1.1 Resolution: Done > WSDL to Relational Importer should be smarter about column names. > ----------------------------------------------------------------- > > Key: TEIIDDES-292 > URL: https://issues.jboss.org/browse/TEIIDDES-292 > Project: Teiid Designer > Issue Type: Bug > Affects Versions: 7.1 > Reporter: John Doyle > Assignee: John Doyle > Priority: Minor > Fix For: 7.3, 7.1.1 > > Attachments: ndfdXML.wsdl > > > With some WSDL the WSDL to Relational Importer will default a column name to text, when it should provide a name for the column. This can be especially problematic when this happens more than once per table, in that case we create a model that does not validate. See the attached schema. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-889) Binary string values may corrupt .xmi files

by Steven Hawkins (JIRA)

Binary string values may corrupt .xmi files ------------------------------------------- Key: TEIIDDES-889 URL: https://issues.jboss.org/browse/TEIIDDES-889 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 6.0.0 Reporter: Steven Hawkins Priority: Minor see TEIIDDES-217 a String value such as "new String(new char[1])" written as a column default value will corrupt the .xmi file. This would presumably happen on any entry, not just default value. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-886) Synchonize VDB with source model with changed Translator does not update translator field.

by Barry LaFond (JIRA)

Synchonize VDB with source model with changed Translator does not update translator field. ------------------------------------------------------------------------------------------ Key: TEIIDDES-886 URL: https://issues.jboss.org/browse/TEIIDDES-886 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.3 Reporter: Barry LaFond Assignee: Dan Florian Priority: Critical Fix For: 7.4 Started with parts example... 1) Select Virtual Model and create NEW VDB 2) Resulting VDB's Source models have no Translator name defined 3) In Workspace, Set Connection Profile on both source models 4) In VDB Editor, Synchronize ALL 5) Translator names are NOT updated from the source model connection info. Should be a tweak to the VdbModelEntry.synchronizeModelEntry( final IProgressMonitor monitor ) method for Regular VDBs -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
1
0 / 0

[JBoss JIRA] Created: (TEIIDDES-832) VDB Synchronize Column Does Not Refresh State After Synchronize All

by Dan Florian (JIRA)

VDB Synchronize Column Does Not Refresh State After Synchronize All ------------------------------------------------------------------- Key: TEIIDDES-832 URL: https://issues.jboss.org/browse/TEIIDDES-832 Project: Teiid Designer Issue Type: Bug Components: VDB & Execution Affects Versions: 7.2 Environment: JBDS 4.0.0.CR2, Mac OS X Reporter: Dan Florian After hitting the "Synchronize All" button on the VDB editor, the 2 models that needed to be synchronized still had unchecked checkboxes in the "Synchronized" column. Just clicking in the "Models" table caused the checkboxes to repaint and show the correct state. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-746) Translator/JNDI Name cells should be a comboboxes, but not textboxes.

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-746?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-746: ---------------------------------- Fix Version/s: 7.4 (was: 8.0) > Translator/JNDI Name cells should be a comboboxes, but not textboxes. > --------------------------------------------------------------------- > > Key: TEIIDDES-746 > URL: https://issues.jboss.org/browse/TEIIDDES-746 > Project: Teiid Designer > Issue Type: Feature Request > Components: Editors > Affects Versions: 7.1, 7.1.1 > Reporter: Dmitry Geraskov > Assignee: Barry LaFond > Priority: Minor > Fix For: 7.4 > > Attachments: cells.PNG > > > Open VDB files editor and look at Model visual part. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

1
0
0 / 0

[JBoss JIRA] Created: (TEIIDDES-574) Datatypes editor: Changing name of datatype is not reflected in list "Datatypes in <your>.xsd"

by Paul Nittel (JIRA)

Datatypes editor: Changing name of datatype is not reflected in list "Datatypes in <your>.xsd" ---------------------------------------------------------------------------------------------- Key: TEIIDDES-574 URL: https://jira.jboss.org/browse/TEIIDDES-574 Project: Teiid Designer Issue Type: Bug Components: Modeling Affects Versions: 7.1 Environment: Fedora 12, JBDS 3.0.1, Teiid Designer 7.1M2 Reporter: Paul Nittel Priority: Minor While testing the simple datatypes editor we change the name of a datatype from PublicationYear to Temporary. When the change is made, the old name remains on the list of "Datatypes in BookDatatypes.xsd". Only after restarting the editor is the change noted in that list. Not a major issue, but it leaves the not-quite-finished impression. Reproduction steps are below. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
6
0 / 0

[JBoss JIRA] Created: (TEIIDDES-834) VDB Editor's Synchronize All Warning Dialog Should Have A "Remember My Decision" Checkbox

by Dan Florian (JIRA)

VDB Editor's Synchronize All Warning Dialog Should Have A "Remember My Decision" Checkbox ----------------------------------------------------------------------------------------- Key: TEIIDDES-834 URL: https://issues.jboss.org/browse/TEIIDDES-834 Project: Teiid Designer Issue Type: Feature Request Components: VDB & Execution Affects Versions: 7.2 Environment: JBDS 4.0.0.CR2, Mac OS X Reporter: Dan Florian When a VDB editor's "Synchronize All" is done, a warning dialog is always displayed warning the user about the possibility of data roles being lost (or something like that). It would be nice if this dialog had a "Remember my decision" checkbox so that the user didn't have to see that warning dialog every time. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (TEIIDDES-831) VDB Models Table Should Resize Columns When A Model Is Added

by Dan Florian (JIRA)

VDB Models Table Should Resize Columns When A Model Is Added ------------------------------------------------------------ Key: TEIIDDES-831 URL: https://issues.jboss.org/browse/TEIIDDES-831 Project: Teiid Designer Issue Type: Task Components: VDB & Execution Affects Versions: 7.2 Environment: JBDS 4.0.0.CR2, Mac OS X Reporter: Dan Florian After adding a view model to a VDB, other dependent models may also automatically be added. In my specific case, adding one model added 8 other models. But in order to figure out which models were automatically added I had to resize both the "Model" and "Path" columns. The "Models" table should resize/pack at least those first two columns when a model is added. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-286) Query Plan Viewer does not show dependent access node's source queries in query plan

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-286?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-286. ----------------------------------- Resolution: Out of Date The old MMX SQL results view and query plan are no longer used. DTP's "Get Execution Plan" and view replace it. > Query Plan Viewer does not show dependent access node's source queries in query plan > ------------------------------------------------------------------------------------ > > Key: TEIIDDES-286 > URL: https://issues.jboss.org/browse/TEIIDDES-286 > Project: Teiid Designer > Issue Type: Bug > Components: Diagrams > Reporter: Michael Walker > Assignee: Barry LaFond > Fix For: 7.4 > > Attachments: depdenentaccess.JPG > > > In a dependent join situation, the query plan shows the source query for the dependent feeder node, but does not show the source query for the dependent "access" or "wait" node. This is not consistent behavior. see screenshot. > By accessing the "wait" node's properties, the source query can be found. However, if the source query is long, it will be truncated, and there is no way to view the entire query if it is displayed in this properties window only (due to another bug). -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 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 February 2011