You are viewing a plain text version of this content. The canonical link for it is here.

Posted to derby-dev@db.apache.org by "Mamta A. Satoor (JIRA)" <ji...@apache.org> on 2012/09/28 06:17:08 UTC

[jira] [Updated] (DERBY-5399) Reimplement the sensitive diagnostic VTIs as table functions so that the DBO can grant SELECT access to them in a straightforward way.

     [ https://issues.apache.org/jira/browse/DERBY-5399?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mamta A. Satoor updated DERBY-5399:
-----------------------------------

    Labels: derby_triage10_10  (was: )
    
> Reimplement the sensitive diagnostic VTIs as table functions so that the DBO can grant SELECT access to them in a straightforward way.
> --------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5399
>                 URL: https://issues.apache.org/jira/browse/DERBY-5399
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.9.1.0
>            Reporter: Rick Hillegas
>              Labels: derby_triage10_10
>
> This is the more complicated solution (2) discussed on DERBY-5395. Re-implementing the diagnostic VTIs as table functions (with metadata tuples in the system catalogs) would make it more straightforward for the DBO to grant tech support roles access to this data.

--
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