Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 65301 invoked from network); 18 Sep 2007 01:57:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 18 Sep 2007 01:57:29 -0000 Received: (qmail 68027 invoked by uid 500); 18 Sep 2007 01:57:20 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 68002 invoked by uid 500); 18 Sep 2007 01:57:20 -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 67993 invoked by uid 99); 18 Sep 2007 01:57:20 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 17 Sep 2007 18:57:20 -0700 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [192.18.6.21] (HELO gmp-eb-mail-1.sun.com) (192.18.6.21) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Sep 2007 01:57:18 +0000 Received: from fe-emea-09.sun.com (gmp-eb-lb-2-fe1.eu.sun.com [192.18.6.10]) by gmp-eb-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id l8I1upYM026264 for ; Tue, 18 Sep 2007 01:56:56 GMT Received: from conversion-daemon.fe-emea-09.sun.com by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JOJ00301K1X3000@fe-emea-09.sun.com> (original mail from Dag.Wanvik@Sun.COM) for derby-dev@db.apache.org; Tue, 18 Sep 2007 02:56:50 +0100 (BST) Received: from khepri05.norway.sun.com ([129.159.112.194]) by fe-emea-09.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JOJ00K2KK2P0800@fe-emea-09.sun.com> for derby-dev@db.apache.org; Tue, 18 Sep 2007 02:56:50 +0100 (BST) Date: Tue, 18 Sep 2007 03:56:49 +0200 From: Dag.Wanvik@Sun.COM (Dag H. Wanvik) Subject: Re: Roles for Derby - draft spec uploaded In-reply-to: <46EECEE6.1080702@apache.org> Sender: Dag.Wanvik@Sun.COM To: derby-dev@db.apache.org Message-id: MIME-version: 1.0 Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7BIT References: <56a83cd00709151627o63e483ces81626f10a414a4e0@mail.gmail.com> <56a83cd00709171133y57d65362r31fb2c5b7cfd7f75@mail.gmail.com> <46EECEE6.1080702@apache.org> User-Agent: Gnus/5.1008 (Gnus v5.10.8) Emacs/22.1 (usg-unix-v) X-Virus-Checked: Checked by ClamAV on apache.org Daniel John Debrunner writes: > On 9/17/07, Dag H. Wanvik wrote: >>> As for having a default role on connect, that could be added later. >>> This is implementation defined behavior, according to SQL std. > > Where does the standard say that? I see in section 4.37.2 the sentence: > > "An SQL-session initially has no SQL-session role name." Ah, yes I knew I had seen that somewhere. I was referring to Annex B "Implementation-defined elements", clause 69 b: 69) Subclause 17.1, : : b) The initial value of the current role name is the null value. >> I can just hear myself cursing every time I have to type in "SET ROLE >> admin" before I can get any work done through my admin UI. > > There's nothing to stop a tool determining if a user has a single > role and then executing a SET ROLE before it opens its admin UI. +1 Dag