Return-Path: X-Original-To: apmail-db-derby-dev-archive@www.apache.org Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A852B7FD7 for ; Mon, 18 Jul 2011 16:01:20 +0000 (UTC) Received: (qmail 46240 invoked by uid 500); 18 Jul 2011 16:01:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 46198 invoked by uid 500); 18 Jul 2011 16:01:19 -0000 Mailing-List: contact derby-dev-help@db.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 46190 invoked by uid 99); 18 Jul 2011 16:01:19 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2011 16:01:19 +0000 X-ASF-Spam-Status: No, hits=-2001.1 required=5.0 tests=ALL_TRUSTED,RP_MATCHES_RCVD X-Spam-Check-By: apache.org Received: from [140.211.11.116] (HELO hel.zones.apache.org) (140.211.11.116) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 18 Jul 2011 16:01:18 +0000 Received: from hel.zones.apache.org (hel.zones.apache.org [140.211.11.116]) by hel.zones.apache.org (Postfix) with ESMTP id 1AF1341D41 for ; Mon, 18 Jul 2011 16:00:58 +0000 (UTC) Date: Mon, 18 Jul 2011 16:00:58 +0000 (UTC) From: "Dag H. Wanvik (JIRA)" To: derby-dev@db.apache.org Message-ID: <1379712890.533.1311004858106.JavaMail.tomcat@hel.zones.apache.org> In-Reply-To: <1252752499.10380.1310575019823.JavaMail.tomcat@hel.zones.apache.org> Subject: [jira] [Commented] (DERBY-5329) Document who is allowed to run which system procedures/functions. MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DERBY-5329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13067100#comment-13067100 ] Dag H. Wanvik commented on DERBY-5329: -------------------------------------- The answer to the first question is "yes". On number two, technically, SQL authorization can be enabled without authentication in Derby, but it is rather pointless since all users can pretend to be anyone, including the DBO. I.e. authentication can be meaningfully used without SQL authorization, but the opposite is not true. I guess our present wording is a bit verbose (and technically wrong: for execution privileges one does need to at least *pretend* to be the dbo - by connecing as dbo), it makes more sense. So I suggest we continue to use what we currently have: "If authentication and SQL authorization are both enabled, ...". > Document who is allowed to run which system procedures/functions. > ----------------------------------------------------------------- > > Key: DERBY-5329 > URL: https://issues.apache.org/jira/browse/DERBY-5329 > Project: Derby > Issue Type: Improvement > Components: Documentation > Affects Versions: 10.9.0.0 > Reporter: Rick Hillegas > Assignee: Kim Haase > Fix For: 10.8.1.6, 10.9.0.0 > > Attachments: DERBY-5329.diff, DERBY-5329.stat, DERBY-5329.zip, rrefaltertablecompress.html, rrefstorejarinstall.html > > > The 5th functional spec attached to DERBY-464 contains a table describing which system procedures/functions can only be run by the DBO and which can be run by everyone. I can't find this information in our user guides. It would be good to copy this information into the Reference Guide topics for each of these procedures/functions. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira