[JBoss JIRA] (TEIIDDES-1211) Exporting DDL for Postgres produces invalid CREATE INDEX statement because duplicate object names in database
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1211?page=com.atlassian.jira.plu... ]
Barry LaFond resolved TEIIDDES-1211.
------------------------------------
Resolution: Done
Added validation rule to check sibling name uniqueness across model object types (TABLE, VIEW, PROCEDURE, INDEX)
> Exporting DDL for Postgres produces invalid CREATE INDEX statement because duplicate object names in database
> -------------------------------------------------------------------------------------------------------------
>
> Key: TEIIDDES-1211
> URL: https://issues.jboss.org/browse/TEIIDDES-1211
> Project: Teiid Designer
> Issue Type: Bug
> Components: Import/Export
> Affects Versions: 7.4.2
> Reporter: Van Halbert
> Assignee: Barry LaFond
> Fix For: 8.2
>
> Attachments: tpc_postgres.ddl
>
>
> Trying to execute DDL on postgres database produces this error:
> Error: ERROR: relation "orders" already exists
> SQLState: 42P07
> ErrorCode: 0
> Error occured in:
> CREATE INDEX ORDERS ON ORDERS (O_CUSTKEY)
> ----
> The problem was resolved if I changed ORDERS index name:
>
> CREATE INDEX ORDERS_IDX ON ORDERS (O_CUSTKEY);
> ----
> Here's a statement I found on the Postgres Naming rules:
> The names of all objects must be unique within some scope. Every database must have a unique name; the name of a schema must be unique within the scope of a single database, the name of a table must be unique within the scope of a single schema, and column names must be unique within a table. The name of an index must be unique within a database.
> I would like to suggest that all index names that are created are appended with "idx" or something similar. Right now, the first looks to be the name of the table, and subsequent names have 1,2, etc. appended.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1480) Add handling for language support in vdbs
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1480?page=com.atlassian.jira.plu... ]
Barry LaFond commented on TEIIDDES-1480:
----------------------------------------
The doc describes a set of properties that can be added to a VDB like:
{code}
<property name="allowed-languages" value="javascript"/>
<property name="allowed-languages" value="perl"/>
<property name="allowed-languages" value="php"/>
{code}
The permissions are defined with these *values* as the <resource-name>
* So what is the scope of the permission?
* Can each *role" have only one permission defined for each *allowed-language* ?
* Does that mean that there is no connection between "allowed-language* and a model resource?
* Can these *allowed-languages* be defined separately in a list, and then displayed and added/removed as permissions for each Role?
> Add handling for language support in vdbs
> -----------------------------------------
>
> Key: TEIIDDES-1480
> URL: https://issues.jboss.org/browse/TEIIDDES-1480
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 8.2
>
>
> Teiid 8.2 added support for an OBJECTTABLE table function TEIID-2141. To use the OBJECTTABLE construct, a vdb property allowed-languages and if applicable the data role language permission needs granted. See the reference https://docs.jboss.org/author/display/TEIID/XML+Definition for an example.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1480) Add handling for language support in vdbs
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1480?page=com.atlassian.jira.plu... ]
Barry LaFond edited comment on TEIIDDES-1480 at 5/22/13 11:31 AM:
------------------------------------------------------------------
The doc describes a set of properties that can be added to a VDB like:
{code}
<property name="allowed-languages" value="javascript"/>
<property name="allowed-languages" value="perl"/>
<property name="allowed-languages" value="php"/>
{code}
The permissions are defined with these *values* as the <resource-name>
* So what is the scope of the permission?
* Can each *role* have only one permission defined for each *allowed-language* ?
* Does that mean that there is no connection between "allowed-language* and a model resource?
* Can these *allowed-languages* be defined separately in a list, and then displayed and added/removed as permissions for each Role?
was (Author: blafond):
The doc describes a set of properties that can be added to a VDB like:
{code}
<property name="allowed-languages" value="javascript"/>
<property name="allowed-languages" value="perl"/>
<property name="allowed-languages" value="php"/>
{code}
The permissions are defined with these *values* as the <resource-name>
* So what is the scope of the permission?
* Can each *role" have only one permission defined for each *allowed-language* ?
* Does that mean that there is no connection between "allowed-language* and a model resource?
* Can these *allowed-languages* be defined separately in a list, and then displayed and added/removed as permissions for each Role?
> Add handling for language support in vdbs
> -----------------------------------------
>
> Key: TEIIDDES-1480
> URL: https://issues.jboss.org/browse/TEIIDDES-1480
> Project: Teiid Designer
> Issue Type: Feature Request
> Components: Teiid Integration
> Reporter: Steven Hawkins
> Assignee: Dan Florian
> Fix For: 8.2
>
>
> Teiid 8.2 added support for an OBJECTTABLE table function TEIID-2141. To use the OBJECTTABLE construct, a vdb property allowed-languages and if applicable the data role language permission needs granted. See the reference https://docs.jboss.org/author/display/TEIID/XML+Definition for an example.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1663) Create Relational Child Dialogs have sizing issues
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1663?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1663:
-----------------------------------
Assignee: Paul Richardson (was: Dan Florian)
> Create Relational Child Dialogs have sizing issues
> --------------------------------------------------
>
> Key: TEIIDDES-1663
> URL: https://issues.jboss.org/browse/TEIIDDES-1663
> Project: Teiid Designer
> Issue Type: Enhancement
> Components: Dialogs
> Affects Versions: 8.1
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.2
>
> Attachments: SizingIssueExample.png
>
>
> Default sizing for some of the 'Create Relational child...' dialogs hides some parameters. Looks like resizing of the dialog also needs some tweaking.
> I am attaching an example for New Child > Procedure... in virtual relational models. On my system, the Name in Source is fully covered. IMO, the bottom tabbed panel should be in a scrollable panel and items above it should never be hidden. Resizing smaller would then result in scrollable area at the bottom with everything accessible.
--
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
11 years
[JBoss JIRA] (TEIIDDES-1687) Deploy VDB action gives no feedback when server is unavailable
by Barry LaFond (JIRA)
[ https://issues.jboss.org/browse/TEIIDDES-1687?page=com.atlassian.jira.plu... ]
Barry LaFond updated TEIIDDES-1687:
-----------------------------------
Assignee: Paul Richardson (was: Dan Florian)
> Deploy VDB action gives no feedback when server is unavailable
> --------------------------------------------------------------
>
> Key: TEIIDDES-1687
> URL: https://issues.jboss.org/browse/TEIIDDES-1687
> Project: Teiid Designer
> Issue Type: Bug
> Components: VDB & Execution
> Affects Versions: 8.1
> Reporter: Mark Drilling
> Assignee: Paul Richardson
> Fix For: 8.2
>
>
> The "Deploy VDB" action is enabled in Model Explorer context menu, but there is no feedback if you select it when server is not running.
> 1) The user should be shown a dialog, saying that no server is available.
> 2) When selecting the "Execute VDB" action, a dialog *is* shown - the Deploy action should do the same. The text on the Execute dialog needs some tweaking, though. Currently it says "Unable to establish connection to server 'admin'" - it should use the name of the server instead of 'admin'
--
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
11 years