February 2011 - teiid-designer-issues

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

by Van Halbert (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-746?page=com.atlassian.jira.plug... ] Van Halbert commented on TEIIDDES-746: -------------------------------------- I put my vote in for needing this option. Trying to create a vdb that uses a jdbc translator. I have no clue, do I put, jdbc, mssql, sqlserver, or what at the translator. This shouldn't be done by trial and error. And without help of some kind, you have to go dig thru the doc's each time you build a vdb, until you become familiar with all the options. For which, I see this as a painful (and frustrating) step for any new user. > 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: 8.0 > > 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-217) JDBC Import Error from MySQL with BIT datatypes

by Mark Drilling (JIRA)

JDBC Import Error from MySQL with BIT datatypes ----------------------------------------------- Key: TEIIDDES-217 URL: https://jira.jboss.org/jira/browse/TEIIDDES-217 Project: Teiid Designer Issue Type: Bug Components: Import/Export Affects Versions: 6.0.0, 6.1.0, 6.2.0, Future Reporter: Mark Drilling Assignee: Barry LaFond Priority: Minor JDBC import from a MySQL database having columns of BIT datatype fails. The import succeeds, but attempts to re-open the generated relational model fail. Further inspection of the .xmi shows that an incorrect 'defaultValue' for the column has been written to the xmi model file. -- 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, 2 months

3
4
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-881) Teiid Designer admin connections should be based on a configurable runtime.

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-881?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-881: -------------------------------- Parent: TEIIDDES-175 Issue Type: Sub-task (was: Feature Request) > Teiid Designer admin connections should be based on a configurable runtime. > --------------------------------------------------------------------------- > > Key: TEIIDDES-881 > URL: https://issues.jboss.org/browse/TEIIDDES-881 > Project: Teiid Designer > Issue Type: Sub-task > Components: VDB & Execution > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: John Doyle > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > The admin and preview connections for Teiid Designer rely on paths that specify plugin + version. Updates to the tooling therefore break existing connections when the version changes. We should instead rely on a user configurable runtime configuration like other JBoss runtimes. -- 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] Updated: (TEIIDDES-879) Automtically create DTP Driver Definition based upon Teiid Runtime Configuration

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-879?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-879: -------------------------------- Summary: Automtically create DTP Driver Definition based upon Teiid Runtime Configuration (was: [Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition) > Automtically create DTP Driver Definition based upon Teiid Runtime Configuration > -------------------------------------------------------------------------------- > > Key: TEIIDDES-879 > URL: https://issues.jboss.org/browse/TEIIDDES-879 > Project: Teiid Designer > Issue Type: Sub-task > Components: Eclipse Integration > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Brian Fitzpatrick > > For the Teiid driver... Is it possible to wrap the driver jar in a plug-in and automatically set it up? Or set up multiple versions (7.0, 7.1, etc.)? Though it's server-dependent, we should be able to control that enough to simplify life for the user and auto-configure a driver instance. -- 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] Updated: (TEIIDDES-879) [Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition

by John Doyle (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-879?page=com.atlassian.jira.plug... ] John Doyle updated TEIIDDES-879: -------------------------------- Parent: TEIIDDES-175 Issue Type: Sub-task (was: Feature Request) > [Designer] Provide Teiid driver in a plug-in wrapper to save the user the step of creating a DTP Driver Definition > ------------------------------------------------------------------------------------------------------------------ > > Key: TEIIDDES-879 > URL: https://issues.jboss.org/browse/TEIIDDES-879 > Project: Teiid Designer > Issue Type: Sub-task > Components: Eclipse Integration > Affects Versions: 7.1.1, 7.2, 7.3 > Reporter: Brian Fitzpatrick > > For the Teiid driver... Is it possible to wrap the driver jar in a plug-in and automatically set it up? Or set up multiple versions (7.0, 7.1, etc.)? Though it's server-dependent, we should be able to control that enough to simplify life for the user and auto-configure a driver instance. -- 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] Commented: (TEIIDDES-792) add support for in/out out return params

by Steven Hawkins (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-792?page=com.atlassian.jira.plug... ] Steven Hawkins commented on TEIIDDES-792: ----------------------------------------- I've got a start at these changes, but need to wait until the first drop of Teiid 7.4 is added. There is still a lingering issue (that was rejected some time ago) about not being able to delete procedure resultsets once they've been added. There's some complexity with deleteaction handling that isn't immediately obvious to me. I'll re-log since I can't find the original. > add support for in/out out return params > ---------------------------------------- > > Key: TEIIDDES-792 > URL: https://issues.jboss.org/browse/TEIIDDES-792 > Project: Teiid Designer > Issue Type: Feature Request > Components: Modeling > Affects Versions: 7.4 > Reporter: Steven Hawkins > Assignee: Steven Hawkins > Fix For: 7.4 > > > In/out, out, return parameters are supported by Teiid virtual procedures - not just result sets - as of 7.4. Designer should remove validation restrictions preventing the usage of these parameters and update the external metadata logic to add out/return parameters as valid symbols. -- 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-826) Provide the ability to view the connection properties that are stored on the model as a result of setting the connection profile, this info will be useful to view when a model is passed on to someone else.

by Van Halbert (JIRA)

Provide the ability to view the connection properties that are stored on the model as a result of setting the connection profile, this info will be useful to view when a model is passed on to someone else. ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: TEIIDDES-826 URL: https://issues.jboss.org/browse/TEIIDDES-826 Project: Teiid Designer Issue Type: Enhancement Components: Dialogs, Editors Affects Versions: 7.3 Reporter: Van Halbert Provide the ability to view the connection properties that are stored on the model (in tags) as a result of setting the connection profile, this info will be useful to view when a model is passed on to someone else. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
9
0 / 0

[JBoss JIRA] Resolved: (TEIIDDES-386) Add validation rule for missing names in source for physical tables

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-386?page=com.atlassian.jira.plug... ] Barry LaFond resolved TEIIDDES-386. ----------------------------------- Resolution: Done Added relational table validation rule: MissingNameInSourceRule > Add validation rule for missing names in source for physical tables > ------------------------------------------------------------------- > > Key: TEIIDDES-386 > URL: https://issues.jboss.org/browse/TEIIDDES-386 > Project: Teiid Designer > Issue Type: Task > Components: Modeling > Environment: All > Reporter: Paul Nittel > Assignee: Barry LaFond > Fix For: 7.4 > > Attachments: PartsByHand-ds.xml, PartsNIS_MPS.zip, wtf_parts_porsche.png > > > I created a physical model and added names in source for the columns, forgetting the table. It validates OK. I wired it to a connector binding and tried to preview the data. This failed with a rather verbose, ugly Oracle error. See attached screenshot. > Should/Can we add a new rule to validate the presence of all names in source for source models. > (Once I defined the tables NIS, it worked fine.) -- 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-883) Add support for Ingres database

by Ramesh Reddy (JIRA)

Add support for Ingres database ------------------------------- Key: TEIIDDES-883 URL: https://issues.jboss.org/browse/TEIIDDES-883 Project: Teiid Designer Issue Type: Feature Request Components: Import/Export Affects Versions: 7.3 Reporter: Ramesh Reddy For Ingres add support for 1) Import of the metadata 2) Creation of data source / Connection profile 3) Export to DDL -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 2 months

3
2
0 / 0

[JBoss JIRA] Updated: (TEIIDDES-226) Problem importing Synonyms into VDB

by Barry LaFond (JIRA)

[ https://issues.jboss.org/browse/TEIIDDES-226?page=com.atlassian.jira.plug... ] Barry LaFond updated TEIIDDES-226: ---------------------------------- Fix Version/s: 8.0 (was: 7.4) Priority: Minor (was: Major) > Problem importing Synonyms into VDB > ----------------------------------- > > Key: TEIIDDES-226 > URL: https://issues.jboss.org/browse/TEIIDDES-226 > Project: Teiid Designer > Issue Type: Bug > Components: Import/Export, Teiid Integration, VDB & Execution > Affects Versions: 6.0.0, 6.1.0, 6.2.0 > Reporter: Ram Yelamanchilli > Priority: Minor > Labels: Designer, SYNONYM, VDB > Fix For: 8.0 > > > I'm trying to import synonyms When I create a source model importing SYNONYM, source model is created with the following error. > "The Base Table must reference one more more columns; there are none." > Designer version is 6.2. -- 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