db-derby-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Knut Anders Hatlen (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DERBY-6420) Clarify how DROP statements work on trigger dependencies
Date Wed, 04 Dec 2013 16:57:37 GMT

    [ https://issues.apache.org/jira/browse/DERBY-6420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13839070#comment-13839070
] 

Knut Anders Hatlen commented on DERBY-6420:
-------------------------------------------

I missed one little thing. DROP SYNONYM says "An error will occur if there are any views or
triggers dependent on the table or view defined by the synonym." It should just say "... if
there are any views or triggers dependent on the synonym."

> Clarify how DROP statements work on trigger dependencies
> --------------------------------------------------------
>
>                 Key: DERBY-6420
>                 URL: https://issues.apache.org/jira/browse/DERBY-6420
>             Project: Derby
>          Issue Type: Improvement
>          Components: Documentation
>    Affects Versions: 10.11.0.0
>            Reporter: Knut Anders Hatlen
>            Assignee: Kim Haase
>            Priority: Minor
>             Fix For: 10.11.0.0
>
>         Attachments: DERBY-6420-2.diff, DERBY-6420-2.zip, DERBY-6420.diff, DERBY-6420.stat,
DERBY-6420.zip
>
>
> Some of the DROP statement topics don't mention what happens if an object depended on
by a trigger gets dropped. We should add this information. The behaviour should be more consistent
after DERBY-2041.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

Mime
View raw message