Actually, in addition to Dan's suggestion of CREATE SCHMEA, you have to next do SET SCHEMA, and then you don't need to create a dummy table in the schema. To be specific, following eg worked in ij
ij> connect 'jdbc:derby:c:/dellater/db1;create=true;user=mamta;password=mamta';
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 db2sql select * from sys.systables;
0 rows inserted/updated/deleted
ij> exit;
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 db2sql select * from sys.systables;
0 rows inserted/updated/deleted
ij> exit;
On 6/11/05, Peter Nabbefeld <[EMAIL PROTECTED]> wrote:
Daniel John Debrunner schrieb:
> [EMAIL PROTECTED] wrote:
>
>
>>"Jean T. Anderson" <[EMAIL PROTECTED]> 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.
Peter
