[JBoss JIRA] Created: (TEIIDDES-569) SQLXML type is imported as object
by Paul Nittel (JIRA)
SQLXML type is imported as object
---------------------------------
Key: TEIIDDES-569
URL: https://jira.jboss.org/browse/TEIIDDES-569
Project: Teiid Designer
Issue Type: Bug
Components: Import/Export
Affects Versions: 7.1
Environment: All
Reporter: Paul Nittel
Attachments: Validating_Wx.zip
I imported the metadata for the INVOKE function from the weather example VDB. When I used the function in a transformation (see below), there was a validation error. Steve Hawkins noted the type of the result procedure parameter was "object" and should be "SQLXML". (Turns out that "SQLXML" is "XMLLiteral" in current Designer parlance. Perhaps that should be changed... Ask Steve H.)
After several attempts to validate the SQL, it finally validated. (And another Jira is on the way.)
SELECT
t.*
FROM
(EXEC Wx_Teiid.invoke(binding = null, action = 'GET', request = null, endpoint = QUERYSTRING('', '38.99,-77.02 39.70,-104.80 47.6,-122.30' AS listLatLon, 'time-series' AS product, '2004-01-01T00:00:00' AS "begin", '2013-04-20T00:00:00' AS "end", 'maxt' AS maxt, 'mint' AS mint))) AS w, XMLTABLE('/dwml/data/location' PASSING result COLUMNS location_key string, lattitude string PATH 'point/@latitude', longitude string PATH 'point/@longitude') AS t
--
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, 3 months
[JBoss JIRA] Created: (TEIIDDES-639) Allow defining the data-role for the "SYSADMIN" module.
by Ramesh Reddy (JIRA)
Allow defining the data-role for the "SYSADMIN" module.
-------------------------------------------------------
Key: TEIIDDES-639
URL: https://jira.jboss.org/browse/TEIIDDES-639
Project: Teiid Designer
Issue Type: Task
Components: VDB & Execution
Affects Versions: 7.1
Reporter: Ramesh Reddy
Fix For: 7.1.1
After TEIID-1246, there is no need for granting explicit data role permissions for the "SYS" and "pg_catalog" models. These models are now accessible to any logged in user with out any authorization checks. However this JIRA introduced a new system models called "SYSADMIN", which requires data role permissions to be accessed by the user.
What I am proposing here is, modify the current functionality in the Designer Data Roles editor such that
1) Modify the check box that says "Allow read-only access to the System tables for this data role" to say "Allow this role to access SYSADMIN model"
2) Remove the automatic generation of the permission code for "SYS" and "pg_catalog" and add the following to the XML file
<permission>
<resource-name>sysadmin</resource-name>
<allow-read>true</allow-read>
</permission>
--
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, 3 months
[JBoss JIRA] Created: (TEIIDDES-635) NPE Deleting Model Project with Diagrams for models within that project open
by Barry LaFond (JIRA)
NPE Deleting Model Project with Diagrams for models within that project open
----------------------------------------------------------------------------
Key: TEIIDDES-635
URL: https://jira.jboss.org/browse/TEIIDDES-635
Project: Teiid Designer
Issue Type: Bug
Components: Diagrams
Affects Versions: 7.1.1
Reporter: Barry LaFond
Assignee: Barry LaFond
Priority: Critical
Fix For: 7.1.1
Attachments: org.teiid.designer.diagram.ui.patch
Actually got this with "jbosstools-3.2.0.Beta1.aggregate-Update-2010-09-27_05-18-00-H173.zip" kit today.
Couldn't get the NPE in Designer IDE, but there is a bug nonetheless.
DiagramEditor needs in notifyChanged() needs to check if the current diagram eIsProxy() which indicates the EObject is out of scope/unloaded and in this case, being deleted.
java.lang.NullPointerException
at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramUtil.createPackageDiagram(PackageDiagramUtil.java:43)
at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramProvider.createPackageDiagram(PackageDiagramProvider.java:57)
at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramProvider.getPackageDiagram(PackageDiagramProvider.java:136)
at com.metamatrix.modeler.diagram.ui.pakkage.PackageDiagramType.getDiagramForContext(PackageDiagramType.java:179)
at com.metamatrix.modeler.diagram.ui.DiagramTypeManager.getDiagramForContext(DiagramTypeManager.java:221)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.openContext(DiagramEditor.java:1155)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.openContext(DiagramEditor.java:1126)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.setDiagram(DiagramEditor.java:1511)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.openContext(DiagramEditor.java:1142)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.openContext(DiagramEditor.java:1126)
at com.metamatrix.modeler.diagram.ui.editor.DiagramEditor.notifyChanged(DiagramEditor.java:1097)
at com.metamatrix.modeler.internal.ui.editors.ModelEditor$5.run(ModelEditor.java:1117)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
--
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, 3 months
[JBoss JIRA] Created: (TEIIDDES-537) SQLResultsView needs tweaking.
by John Doyle (JIRA)
SQLResultsView needs tweaking.
------------------------------
Key: TEIIDDES-537
URL: https://jira.jboss.org/browse/TEIIDDES-537
Project: Teiid Designer
Issue Type: Bug
Affects Versions: 7.1
Reporter: John Doyle
Assignee: John Doyle
Fix For: 7.1.1
The SQL Results view needs some tweaking.
The actual results flash in the result tab and then are replaced by the 'status' tab
The results from preview are not displayed until the user select "Display results of unresolvable connection profiles" in the filter options.
Clobs are not handled correctly the the default viewer. XML is probably also not handled correctly, but I haven't tested that yet.
--
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, 3 months