db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Yip Ng (JIRA)" <derby-...@db.apache.org>
Subject [jira] Commented: (DERBY-1839) Doc Review Updates - Ref Manual
Date Tue, 19 Sep 2006 22:41:26 GMT
    [ http://issues.apache.org/jira/browse/DERBY-1839?page=comments#action_12436039 ] 
Yip Ng commented on DERBY-1839:

Hi Laura:

For CREATE TRIGGER, I think you misinterpreted my doc comment.

You cannot create trigger for schemas that start with SYS in either modes(Derby SQL authorization
mode or the old mode).

I was referring to "You can create a trigger in any schema." part.  In SQL authorization mode,
one cannot create a trigger in a schema that the user does not own.  For example, if user2
attempts to create an after insert trigger on table  user1.t1, first user2 must have TRIGGER
privilege granted by user1.  The following create trigger statement should succeed if user2
has TRIGGER privilege on table user1.t1.

CREATE TRIGGER user2.tr1 after insert on user1.t1 for each statement mode db2sql insert into
user2.t2 values 1;

This would fail since user2 is trying to create the trigger tr1 in schema user1 for which
user2 does not own.

CREATE TRIGGER user1.tr1 after insert on user1.t1 for each statement mode db2sql insert into
user2.t2 values 1;

Hope that clear things up.

> Doc Review Updates - Ref Manual
> -------------------------------
>                 Key: DERBY-1839
>                 URL: http://issues.apache.org/jira/browse/DERBY-1839
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions:
>            Reporter: Laura Stewart
>         Assigned To: Laura Stewart
>         Attachments: 1839_SQLstatements.diff, derby1839_SQLstatements2.diff, derby1839_SQLstatements2_html.zip,
> This JIRA issue will be used to track all of the issues found in the 10.2 doc review
of the Reference Manual.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message