[JBoss JIRA] (TEIIDDES-1794) Designer support for global temporary tables
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1794?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1794:
-----------------------------------
Fix Version/s: 8.3
> Designer support for global temporary tables
> --------------------------------------------
>
> Key: TEIIDDES-1794
> URL: https://issues.jboss.org/browse/TEIIDDES-1794
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Modeling
> Reporter: Mark Addleman
> Fix For: 8.3
>
>
> Teiid has added support for a global temporary tables - they share a common definition, but each session has their own instance. Internally this is modeled as a virtual table (without a transformation) with a table type of "TemporaryTable" (int code 6). If you provided matching index metadata we would recognize the entry as a global temporary table.
> Alternatively extension metadata could be used.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1814) Need to remove Teiid specific server creation dialog for Designer 8.x
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1814?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1814.
------------------------------------
Assignee: Paul Richardson
Fix Version/s: 8.2.x-prod-eds6.0
Resolution: Done
Dialog was removed. Teiid Instance info is now editable via a Teiid Instance editor tab on the Server editor
> Need to remove Teiid specific server creation dialog for Designer 8.x
> ---------------------------------------------------------------------
>
> Key: TEIIDDES-1814
> URL: https://issues.jboss.org/browse/TEIIDDES-1814
> Project: Teiid Designer
> Issue Type: Quality Risk
> Reporter: Ramesh Reddy
> Assignee: Paul Richardson
> Fix For: 8.2.x-prod-eds6.0
>
>
> Currently Teiid Designer has its own server instance creation dialog box and let's user create new server instance with it. This causes confusion as to how to configure server. There should be only one way to create a server instance.
> In AS 7.x with Teiid 8.x, this dialog or option should NOT exist, as Teiid is just subsystem in JBoss AS, and it does own the Admin section as it did in Teiid 7.x series. It should operate solely by the server instance created by "Servers" view provided by the JBoss Tools.
> The Teiid's JDBC port can also be automatically read from the configuration, and JDBC user name/password can be moved to "preferences" section and default to "user/user". Do not hard code these names in code.
> Since JBoss Tools gives an option to create multiple running servers, the default selection of the server view can still exist; or contribute the default selection of server to the JBoss Tools and remove that option from Teiid Designer.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1863) Add native type to procedure parameters
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1863?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1863:
-----------------------------------
Fix Version/s: 8.3
> Add native type to procedure parameters
> ---------------------------------------
>
> Key: TEIIDDES-1863
> URL: https://issues.jboss.org/browse/TEIIDDES-1863
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Modeling, Teiid Integration
> Reporter: Steven Hawkins
> Fix For: 8.3
>
>
> TEIID-2644 adds out parameter cursor handling for oracle, and adds a native type property to procedure parameters (just like regular columns). That is not currently in the index metadata. This value would need to be captured on import and either a new index version used, or an extension property (with additional Teiid handling), or the vdb.xml can use alter statements to add an option.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1861) Designer deletes data role "condition" information
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1861?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1861:
----------------------------------------
Pablo,
Any chance you could attach the Model Project Set (zip) containing the model(s) and VDB at the point just prior to synchronizing?
> Designer deletes data role "condition" information
> --------------------------------------------------
>
> Key: TEIIDDES-1861
> URL: https://issues.jboss.org/browse/TEIIDDES-1861
> Project: Teiid Designer
> Issue Type: Bug
> Components: Teiid Integration, VDB & Execution
> Affects Versions: 8.2
> Environment: Windows 7, Eclipse kepler.
> Reporter: Pablo Navascues
> Assignee: Barry LaFond
> Fix For: 8.2.x-prod-eds6.0
>
>
> Create a VDB
> Create a source model by importing from JDBC
> Add model to VDB
> Define data role with a table wide condition like "USERNAME=substring(user(), 1, locate('@', user()) - 1)"
> Synchronize, save VBD.
> Condition is applied to queries, can be seen in the designer, can be seen in the VBD internal xml.
> Keep working and after another save (not necessarily de second one) condition field value is empty in designer and gone from teh XML as well.
> This has happened more than once and to more than one developer in the team.
--
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, 7 months
[JBoss JIRA] (TEIIDDES-1811) Can't import Procedure parameters to source model in Teiid Designer
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1811?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1811:
----------------------------------------
Again, I am able to import procedures from into an existing source model and my parameters do get imported. It works with both SQL Server and Oracle. So I cannot reproduce step (1) above.
Are you importing via JDBC and which database type?
> Can't import Procedure parameters to source model in Teiid Designer
> -------------------------------------------------------------------
>
> Key: TEIIDDES-1811
> URL: https://issues.jboss.org/browse/TEIIDDES-1811
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 8.1
> Environment: Windows, eclipse JUNO, Teiid Designer 8.2 alpha1
> Reporter: Jing Li
> Priority: Minor
> Fix For: 8.3
>
>
> Usually if we have some changes in source VDB, after we update the source model in designer, we will see the changes.
>
> But for procedure, if we add a new procedure in source VDB, after update SM, we only can see the procedure, but can't see the paramenters of that procedure. We have to manually add them.
> In this way, in the future, every time when we update our SM, our procedures parameters will be gone, we have to add them manually.
> According to Ramesh -- "That sounds like Designer bug to me. You should log a JIRA with Teiid Designer."
> Thanks.
> See: https://community.jboss.org/message/830569
--
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, 7 months