[ https://issues.jboss.org/browse/TEIID-2327?page=com.atlassian.jira.plugin... ] Steven Hawkins commented on TEIID-2327: --------------------------------------- After reviewing oracle and db2 implementations and doing some initial mocking, I'm moving forward with functionality similar to oracle - that is the effect of the mask is applied effectively when the table is accessed and only for select/exec. db2 effectively applies the masking when a value is used in a projected function or after the projection - which means that the grouping, joins, etc. take place on the unmasked values. Not only is this more difficult to implement, but it also easily allows for the definition of masks that fail at runtime (using another column value to mask without that column being available such as in a grouping), and without additional restrictions allow for simplistic determination of masked values. Several additional row/column enhancements may be needed, such as the ability for views/procedures to turn off the effect of transitive masking/filtering and the ability to turn off the check constraint effect of a source table filter. -- 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