[JBoss JIRA] Created: (TEIIDDES-717) Designer whoudl provide option to create datasources during the VDB deploy
by Ramesh Reddy (JIRA)
Designer whoudl provide option to create datasources during the VDB deploy
--------------------------------------------------------------------------
Key: TEIIDDES-717
URL: https://jira.jboss.org/browse/TEIIDDES-717
Project: Teiid Designer
Issue Type: Feature Request
Components: Teiid Integration
Affects Versions: 7.1
Reporter: Ramesh Reddy
Currently when a VDB is deployed, vdb is deployed but process does not check if the required data sources in the server exist or not. Designer should provide an option to the user to select to decide to create data sources or not in the same deploy action. This could be wizard driven if needed to. That way when a VDB is deployed all the required artifacts are also available in the server.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 10 months
[JBoss JIRA] Created: (TEIIDDES-768) Criteria Builder may insert crieria inside object names if user not careful
by Paul Nittel (JIRA)
Criteria Builder may insert crieria inside object names if user not careful
---------------------------------------------------------------------------
Key: TEIIDDES-768
URL: https://issues.jboss.org/browse/TEIIDDES-768
Project: Teiid Designer
Issue Type: Bug
Components: Transformations
Affects Versions: 7.1.1
Environment: JBDS 4.0 Beta2
Reporter: Paul Nittel
I start with:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PartsSource.PARTS;
END
At this point the Criteria Builder (and Expression Builder) button is disabled. So I click in the SELECT clause to enable the button. Let's say I click between the P and the A of .PARTS. The button enables, I craft my WHERE clause, click OK and wind up with:
CREATE VIRTUAL PROCEDURE
BEGIN
SELECT * FROM PartsSource.PA WHERE PartsSource.PARTS.PART_COLOR = PartsView.getPartsByColor.colorInRTS;
END
Regardless of where in the SELECT I click, the WHERE clause should be inserted in a syntactically correct location.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-710) Add Ability to Create Translator Overrides in Designer
by Ted Jones (JIRA)
Add Ability to Create Translator Overrides in Designer
-------------------------------------------------------
Key: TEIIDDES-710
URL: https://jira.jboss.org/browse/TEIIDDES-710
Project: Teiid Designer
Issue Type: Feature Request
Components: VDB & Execution
Affects Versions: 7.1
Reporter: Ted Jones
Assignee: Ted Jones
Need the ability to ad translator overrides for a VDB. Currently overrides have to be manually added to the vdb.xml.
After talking with Barry, the best place for such and editor would be from the Translator field of the models table from within the VDB editor. There is a context menu that allows you to change the translator from that field.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 11 months
[JBoss JIRA] Created: (TEIIDDES-518) DTP context menu options on Teiid tables should consider whether virtual model supports update.
by Ken Johnson (JIRA)
DTP context menu options on Teiid tables should consider whether virtual model supports update.
-----------------------------------------------------------------------------------------------
Key: TEIIDDES-518
URL: https://jira.jboss.org/browse/TEIIDDES-518
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.0
Environment: Teiid Designer 7.0 + JBoss Dev Studio 3.0.1GA
Teiid 7.1 Alpha on EAP 5.1
RHEL 6, OpenJDK 1.6
Reporter: Ken Johnson
In DTP, Context menu for Table contains several options under Data->(Edit, Load, Extract, Sample Contents). For virtual tables, Extract and Sample Contents are fine. Edit and Load will attempt to write data. Thus a few issues:
a) These options should be disabled if the table in question does not have Supports Update checked.
b) These options should be tested when the table *does* have Update and Insert procedures defined.
c) Tables in SYS schema should never be writable.
When working with physical tables, all options should be available and work correctly. Cursory testing indicates this is the case - at least with a MySQL data source underlying the model.
--
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
14 years