Return-Path: Delivered-To: apmail-db-derby-dev-archive@www.apache.org Received: (qmail 32187 invoked from network); 12 Jun 2005 05:15:12 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 Jun 2005 05:15:12 -0000 Received: (qmail 26214 invoked by uid 500); 12 Jun 2005 05:15:12 -0000 Delivered-To: apmail-db-derby-dev-archive@db.apache.org Received: (qmail 26185 invoked by uid 500); 12 Jun 2005 05:15:11 -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: "Derby Development" Delivered-To: mailing list derby-dev@db.apache.org Received: (qmail 26166 invoked by uid 99); 12 Jun 2005 05:15:11 -0000 X-ASF-Spam-Status: No, hits=0.1 required=10.0 tests=HTML_30_40,HTML_MESSAGE,RCVD_BY_IP,SPF_HELO_PASS,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: domain of msatoor@gmail.com designates 64.233.184.196 as permitted sender) Received: from wproxy.gmail.com (HELO wproxy.gmail.com) (64.233.184.196) by apache.org (qpsmtpd/0.28) with ESMTP; Sat, 11 Jun 2005 22:15:06 -0700 Received: by wproxy.gmail.com with SMTP id 58so977744wri for ; Sat, 11 Jun 2005 22:15:03 -0700 (PDT) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:references; b=GAHN3PIIXo2w+ybaHk9lD6RR7poFNAJFK2AoEESmhdF+WszZzPLBfejW2tEaAMIWKkFAiD7p82s7NkboggMqpQlU6XewDDqy9FM43KgI6ZMUVQ/Pj60Eu8dcfX1YwnD83yQOQv6Et4rNZdWwG2PyprlE8AFhL65u5Mclhn7Bmpw= Received: by 10.54.46.47 with SMTP id t47mr2008284wrt; Sat, 11 Jun 2005 22:15:03 -0700 (PDT) Received: by 10.54.49.54 with HTTP; Sat, 11 Jun 2005 22:15:03 -0700 (PDT) Message-ID: Date: Sat, 11 Jun 2005 22:15:03 -0700 From: Mamta Satoor Reply-To: Mamta Satoor To: Derby Development Subject: Re: 10.1 branch created / please review open 10.1 JIRA issues [DERBY-85] In-Reply-To: Mime-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_5223_21076679.1118553303197" References: <155E5416-F701-4485-BB21-290405E0A261@gmail.com> <22B2C628-2138-42D2-81E9-3881E0CABAE0@gmail.com> <42A9B0EE.2080005@bristowhill.com> <42AB428F.1000002@debrunners.com> X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N ------=_Part_5223_21076679.1118553303197 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline Actually, in addition to Dan's suggestion of CREATE SCHMEA, you have to nex= t=20 do SET SCHEMA, and then you don't need to create a dummy table in the=20 schema. To be specific, following eg worked in ij ij> connect=20 'jdbc:derby:c:/dellater/db1;create=3Dtrue;user=3Dmamta;password=3Dmamta'; ij> create table itko.t1 (i int); 0 rows inserted/updated/deleted ij> create schema mamta; 0 rows inserted/updated/deleted ij> set schema mamta; 0 rows inserted/updated/deleted ij> create trigger itko.trig1 after update on itko.t1 for each row mode=20 db2sql select * from sys.systables; 0 rows inserted/updated/deleted ij> exit; On 6/11/05, Peter Nabbefeld wrote:=20 >=20 > Daniel John Debrunner schrieb: >=20 > > Dyre.Tjeldvoll@Sun.COM wrote: > > > > > >>"Jean T. Anderson" writes: > >> > >> > >> > >>>If there are no takers to fix DERBY-85 yet, is there a viable > >>>workaround we can document in the Jira issue and on the derby web site= ? > >> > >> > >>Yes, create a non-empty dummy table in the default schema. I think > >>I've mentioned this in a comment to DERBY-85... > > > > > > Or simpler, just create the schema using CREATE SCHEMA. > > > > Dan. > > > I've tried that, but it did not seem to work (probably no autocommit?) - > only after creating a dummy table in the default schema I could create > the trigger in a non-default schema. >=20 > Peter >=20 >=20 > ------=_Part_5223_21076679.1118553303197 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable Content-Disposition: inline
Actually, in addition to Dan's suggestion of CREATE SCHMEA, you have t= o next do SET SCHEMA, and then you don't need to create a dummy table in th= e schema. To be specific, following eg worked in ij
ij> connect 'jdbc:derby:c:/dellater/db1;create=3Dtrue;user=3Dmamta;= password=3Dmamta';
ij> create table itko.t1 (i int);
0 rows insert= ed/updated/deleted
ij> create schema mamta;
0 rows inserted/update= d/deleted
ij> set schema mamta;
0 rows inserted/updated/deleted
ij> c= reate trigger itko.trig1 after update on itko.t1 for each row mode db2sql s= elect * from sys.systables;
0 rows inserted/updated/deleted
ij> ex= it;

 
On 6/11/05, = Peter Nabbefeld <Peter.Nab= befeld@gmx.de> wrote:
Daniel John Debrunner schrieb:
> Dyre.Tjeldvoll@Sun.COM= wrote:
>
>
>>"Jean T. Anderson" <jta@bristowhill.com> writes:
>= >
>>
>>
>>>If there are no takers to fix D= ERBY-85 yet, is there a viable
>>>workaround we can document in the Jira issue and on the der= by web site?
>>
>>
>>Yes, create a non-empty dum= my table in the default schema. I think
>>I've mentioned this in a= comment to DERBY-85...
>
>
> Or simpler, just create the schema using CREATE SC= HEMA.
>
> Dan.
>
I've tried that, but it did not seem = to work (probably no autocommit?) -
only after creating a dummy table in= the default schema I could create
the trigger in a non-default schema.

Peter



------=_Part_5223_21076679.1118553303197--