From derby-user-return-14500-apmail-db-derby-user-archive=db.apache.org@db.apache.org Mon Jul 23 14:33:50 2012 Return-Path: X-Original-To: apmail-db-derby-user-archive@www.apache.org Delivered-To: apmail-db-derby-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AE1449FCB for ; Mon, 23 Jul 2012 14:33:50 +0000 (UTC) Received: (qmail 43964 invoked by uid 500); 23 Jul 2012 14:33:50 -0000 Delivered-To: apmail-db-derby-user-archive@db.apache.org Received: (qmail 43769 invoked by uid 500); 23 Jul 2012 14:33:50 -0000 Mailing-List: contact derby-user-help@db.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Reply-To: "Derby Discussion" Delivered-To: mailing list derby-user@db.apache.org Received: (qmail 43755 invoked by uid 99); 23 Jul 2012 14:33:50 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2012 14:33:50 +0000 X-ASF-Spam-Status: No, hits=-2.8 required=5.0 tests=FSL_RCVD_USER,HTML_MESSAGE,RCVD_IN_DNSWL_HI,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kristian.waagan@oracle.com designates 148.87.113.117 as permitted sender) Received: from [148.87.113.117] (HELO rcsinet15.oracle.com) (148.87.113.117) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 23 Jul 2012 14:33:40 +0000 Received: from acsinet22.oracle.com (acsinet22.oracle.com [141.146.126.238]) by rcsinet15.oracle.com (Sentrion-MTA-4.2.2/Sentrion-MTA-4.2.2) with ESMTP id q6NEXJWW031220 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=OK) for ; Mon, 23 Jul 2012 14:33:19 GMT Received: from acsmt357.oracle.com (acsmt357.oracle.com [141.146.40.157]) by acsinet22.oracle.com (8.14.4+Sun/8.14.4) with ESMTP id q6NEXIfY011758 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Mon, 23 Jul 2012 14:33:19 GMT Received: from abhmt102.oracle.com (abhmt102.oracle.com [141.146.116.54]) by acsmt357.oracle.com (8.12.11.20060308/8.12.11) with ESMTP id q6NEXIEH021362 for ; Mon, 23 Jul 2012 09:33:18 -0500 Received: from [192.168.0.198] (/84.215.180.161) by default (Oracle Beehive Gateway v4.0) with ESMTP ; Mon, 23 Jul 2012 07:33:18 -0700 Message-ID: <500D6075.6040704@oracle.com> Date: Mon, 23 Jul 2012 16:32:21 +0200 From: Kristian Waagan Organization: Oracle Corporation User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:10.0.1) Gecko/20120208 Thunderbird/10.0.1 MIME-Version: 1.0 To: derby-user@db.apache.org Subject: Re: AW: schema-questions References: <944A1108FF717B43A3F9AA883583DDB202330E8A@EVS01.intern.interpay.nl> <1342541288.30268.4346.camel@dellberry> <944A1108FF717B43A3F9AA883583DDB202330E92@EVS01.intern.interpay.nl> <1342557348.30268.4451.camel@dellberry> <944A1108FF717B43A3F9AA883583DDB202330EC7@EVS01.intern.interpay.nl> <1342626465.30268.4587.camel@dellberry> <944A1108FF717B43A3F9AA883583DDB202330F41@EVS01.intern.interpay.nl> <1342716252.30268.4680.camel@dellberry> <944A1108FF717B43A3F9AA883583DDB202330F7E@EVS01.intern.interpay.nl> <944A1108FF717B43A3F9AA883583DDB202330FD6@EVS01.intern.interpay.nl> In-Reply-To: <944A1108FF717B43A3F9AA883583DDB202330FD6@EVS01.intern.interpay.nl> Content-Type: multipart/alternative; boundary="------------030807080601060808020606" X-Source-IP: acsinet22.oracle.com [141.146.126.238] This is a multi-part message in MIME format. --------------030807080601060808020606 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 23.07.2012 15:34, Malte.Kempff@de.equens.com wrote: > Actually I found 2 hints > > 1. > use SET CURRENT SCHEMA > 2. > Make your own custom authentication > For completeness, one can also specify the schema explicitly in the queries of course. I don't know if there are scenarios where this approach won't work. -- Kristian --------------030807080601060808020606 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit On 23.07.2012 15:34, Malte.Kempff@de.equens.com wrote:
Actually I found 2 hints
  1. use SET CURRENT SCHEMA
  2. Make your own custom authentication

For completeness, one can also specify the schema explicitly in the queries of course. I don't know if there are scenarios where this approach won't work.


--
Kristian
--------------030807080601060808020606--