Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm
Precedence: bulk
Reply-To: <derby-dev@db.apache.org>
Date: Tue, 17 Jul 2012 19:41:34 +0000 (UTC)
From: "Rick Hillegas (JIRA)" <jira@apache.org>
To: derby-dev@db.apache.org
Message-ID: <1426932585.65460.1342554094918.JavaMail.jiratomcat@issues-vm>
Subject: [jira] [Created] (DERBY-5861) Provide a diagnostic table function
 which lets DBOs view the Derby properties understood by their database.
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Rick Hillegas created DERBY-5861:
------------------------------------

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


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