[ https://issues.jboss.org/browse/TEIID-5798?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-5798: --------------------------------------- Ill defined perhaps. It is simply that conditions and masks are scoped to the entire "permission" internally. Just keep in mind that is actually a large change and breaks the apis and how multiple grants / revokes are currently handled (not that it's currently a great way of doing things). Given the amount of work involved it may be better to think about adopting/following the pg model for condition/mask. As is we'd have to come up with our own definitions for the following: {code} GRANT SELECT,INSERT ... CONDITION 'cond 1'; GRANT DELETE ... CONDITION 'cond 2'; {code} {code} REVOKE DELETE ... -- but nothing specified about the "delete condition". Does it linger, or go away? {code} {code} GRANT SELECT ... CONDITION 'cond 3'; -- would this be an exception (similar to today), or like pg would we support combinations of conditions within the same role. Currently we only combine across roles. {code} {code} REVOKE SELECT ... CONDITION -- presumably the insert condition remains {code} -- This message was sent by Atlassian Jira (v7.13.8#713008)