[
https://issues.jboss.org/browse/TEIID-4770?page=com.atlassian.jira.plugin...
]
Bram Gadeyne commented on TEIID-4770:
-------------------------------------
Hi Steven,
Please let me know if you need the full data-role xml. e.g. for the resource glims it is
defined (by teiiddesigner) as:
{code:xml}
<data-role name="mica" any-authenticated="false"
allow-create-temporary-tables="true" grant-all="false">
<description></description>
<!-- ... -->
<permission>
<resource-name>glims</resource-name>
<allow-create>false</allow-create>
<allow-read>false</allow-read>
<allow-update>false</allow-update>
<allow-delete>false</allow-delete>
<allow-execute>false</allow-execute>
<allow-alter>false</allow-alter>
</permission>
<!-- ... -->
<mapped-role-name>mica</mapped-role-name>
</data-role>
{code}
The convert script generates empty GRANT statements for roles that
don't have permission to access a certain schema.
--------------------------------------------------------------------------------------------------------------------
Key: TEIID-4770
URL:
https://issues.jboss.org/browse/TEIID-4770
Project: Teiid
Issue Type: Enhancement
Components: Build/Kits
Affects Versions: 9.2
Reporter: Bram Gadeyne
Assignee: Steven Hawkins
Fix For: 9.3, 9.2.1
The convert script generates empty GRANT statements for roles that don't have
permission to access a certain schema.
E.g. GRANT ON SCHEMA glims TO mica;
When you try to deploy the script, the server complains that it expects a permission type
(like select or alter) here.
These lines should probably be removed.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)