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 "Rick Hillegas (JIRA)" <ji...@apache.org> on 2012/07/18 15:36:35 UTC

[jira] [Commented] (DERBY-5861) Provide a diagnostic table function which lets DBOs view the Derby properties understood by their database.

    [ https://issues.apache.org/jira/browse/DERBY-5861?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13417081#comment-13417081 ] 

Rick Hillegas commented on DERBY-5861:
--------------------------------------

This issue came up as a result of the discussion on this email thread: http://old.nabble.com/schema-questions-td34174077.html#a34174077
                
> Provide a diagnostic table function which lets DBOs view the Derby properties understood by their database.
> -----------------------------------------------------------------------------------------------------------
>
>                 Key: DERBY-5861
>                 URL: https://issues.apache.org/jira/browse/DERBY-5861
>             Project: Derby
>          Issue Type: Improvement
>          Components: SQL
>    Affects Versions: 10.10.0.0
>            Reporter: Rick Hillegas
>         Attachments: DerbyPropertyViewer.java
>
>
> Currently there is no way for the DBO to verify what the database thinks the derby properties are. We could provide a diagnostic table function to show this information. By default only the DBO should be able to run this table function. I will attach a crude workaround.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira